Privacy Policy

Last updated: 28 September 2026. This notice describes what SyncNet V3 processes and why. SyncNet has no user accounts, does not request or store private keys or seed phrases, and does not post to social networks on your behalf. Wallet connection and transaction approval are handled by the wallet provider you choose in your browser.

Who is responsible

SyncNet is run by the SyncNet operators. For privacy questions and requests, use the channels on the Contact page.

What SyncNet processes

Wallet addresses and signatures. SyncNet sees the address of the wallet you connect. Signed actions use a free message, never a transaction. For Project Passport, Marketplace, Economy and Project Home actions, the server stores the signed message and the signature so anyone can verify it.

Project Passport and Marketplace records. Operator claims, listings, offers, operator transfers, deal settlement checklists and their signatures, including the wallet addresses involved. Listings and Passport operator history are public; history is append-only.

Project Home activation and payment records. Payment quotes (the project, the requesting operator, price, reference rate and exact SYNC amount), and for each activation the paying wallet address, transaction hash, amount, block and time. Activation records can be read through SyncNet’s public API, and the payment itself is public on Robinhood Chain. Free-beta activations record only the project, the time and the operator who published; no payment exists for them.

Project Home content and history. Every published configuration and revision (text, links, image references), the signing wallet, its signature and the time, plus unpublish and adoption events. Revisions are kept as an audit and recovery history; published content is public. If SyncNet suspends a Project Home, it records the category, an internal note, the time and which SyncNet operator acted.

Image uploads. To upload an image you sign a free wallet message and receive a short-lived upload session (30 minutes, kept in your browser’s session storage). The server decodes and re-encodes every image (PNG or GIF) before pinning it, which removes embedded metadata such as EXIF/GPS, comments and XMP. SyncNet stores the image’s hash, type, dimensions, size and time. The pinning provider receives the sanitised image and a label containing the uploading wallet address. Images pinned to IPFS are public.

Labs · EARLY (pilot). If you use EARLY, SyncNet stores: signed “Count me in” signals (your wallet address and the YouTube channel id, private, shown to nobody but you; the creator later sees only a count); your signed support intents and, when a transfer matches one, a private receipt (your wallet address, the creator’s channel id and wallet, the token, the exact amount, the transaction hash, block and time). Receipts and signals are never public and are never listed to anyone without a fresh signature from your wallet. If you choose to make an EARLY card, the public page shows the creator, the date and the creator’s approximate audience on that day, and hides your wallet, the amount and the transaction unless you later reveal them. For creators, SyncNet stores the YouTube channel id, title, handle and avatar URL, the public subscriber count read daily (or “hidden”), the receiving wallet and the signed manifests; the channel id, wallet and daily audience snapshots are published as signed attestations and anchored on Robinhood Chain and via OpenTimestamps. Google sign-in uses read-only YouTube access; the access token is used once and not stored, and no refresh token is requested. Payments go directly from your wallet to the creator’s wallet on Robinhood Chain and are public there; SyncNet never receives or holds them.

Launch proofs and Economy records. If you publish a launch proof to the SyncNet Registry, the proof (deployer address, token, transaction hash, intent record and signature) becomes public. Signed Economy curation events are stored and public.

IP addresses and abuse-prevention identifiers. SyncNet uses your IP address to apply rate limits and lockouts. The counters are keyed by a salted hash of the IP address, not the address itself, and expire automatically.

Server logs. SyncNet’s functions log events and errors. IP addresses and wallet addresses appear in logs only as salted hashes; logs can contain token addresses, transaction hashes and error details.

Blockchain, RPC and indexer requests. Your browser and SyncNet’s server read Robinhood Chain through RPC providers and read PAR’s indexer and token list. Launch simulation sends the project’s name, ticker, description, image URI, wallet address and prepared call to a public Robinhood Chain RPC (eth_call) before any transaction is sent, so do not treat simulated metadata as secret.

Browser storage. Your browser stores local features: launch records (prepared and sent launches, transaction hashes, intent records and signatures), Duel records, Project Home drafts and upload sessions. They stay on your device until you clear browser storage.

Why

SyncNet processes this information to run the features you use; to verify signatures, Project Passport authority and Project Home payments; to show public records and verifiable history; to prevent abuse, fraud and overload; to keep SyncNet secure and moderate content under the Terms; and to meet legal obligations.

Who receives it

Service providers that run parts of SyncNet: Netlify (hosting, functions and their logs); Upstash (the key-value store for rate limits, Registry, Marketplace, Passport, Economy and Project Home records); Pinata and, where configured, a second pinning service (image pinning); IPFS gateways used to check and display images (gateway.pinata.cloud, ipfs.io, dweb.link); Robinhood Chain RPC providers; PAR (api.par.family, par.family); and your wallet provider. Public records — blockchain transactions, IPFS content, Registry proofs, Marketplace listings, Passport history and published Project Homes — can be read by anyone. SyncNet may also disclose information where the law requires it or where needed to protect SyncNet, its users or others from fraud or abuse.

Retention

• Rate-limit counters and lockouts: until their window ends (at most one day).
• Upload sessions: 30 minutes; signature nonces: 90 days; unpaid Project Home payment quotes: 90 days.
• EARLY: unsigned intent drafts 20 minutes; unmatched intents 90 days; Count me in signals 180 days (withdrawn ones 30 days); OAuth link records 15 minutes; sessions at most 2 hours; receipts for as long as the service runs (they are your proof).
• Project Home activations, revisions and audit history, Project Passport and Marketplace history, Registry proofs and Economy events: for as long as SyncNet operates the service they belong to, because they are the verifiable record of who controlled what.
• Server logs: for the hosting provider’s log retention period.
• Browser storage: until you clear it.

Public blockchains and IPFS

Transactions, token metadata and anything published to a public blockchain or IPFS are public and effectively permanent. SyncNet cannot change or erase them, and cannot remove copies held by other IPFS nodes, gateways, explorers or indexers, even if SyncNet stops serving or pinning them.

Your rights and requests

Depending on where you live, you may have rights to access, correct or delete personal data, to restrict or object to its processing, and to complain to a data protection authority. To make a request, contact SyncNet through the channels on the Contact page and say that it is a privacy request. SyncNet may ask you to prove control of a wallet with a free signature before acting. Records on public blockchains or IPFS, and signed append-only records that others rely on to verify history, may not be deletable; if SyncNet cannot delete something, it will say why.

Security

SyncNet protects what it stores with signature checks, hashed identifiers and server-side credentials that are never sent to browsers, but no online system is completely secure, and SyncNet is experimental software. Never share your seed phrase or private key; SyncNet will never ask for them.

International processing

SyncNet’s service providers and the public blockchain and IPFS networks operate infrastructure in several countries, so information may be processed outside the country where you live, where data protection laws may differ.

Changes

SyncNet may update this notice. The date at the top shows the current version.