Arc USDC arcexit.com

Privacy

2026-08-31 no accounts, no KYC, no analytics

No accounts, no KYC, no analytics, no cookies, no server-side database. We do not ask for your name, ID, or email, and we have no way to associate a wallet with a person.

1. What we collect

Nothing on our side. The pages are static files with no backend. There is no sign-up, no form and no tracking pixel, and nothing we wrote reports on you. We cannot see who you are, and we do not try.

One correction worth making, because you can see it in a browser console: our host, Cloudflare, injects its own analytics beacon into the page on the way out. The site's security headers block it from loading, so it never runs and never reports anything, and it is absent from what a plain download of the page contains. We did not put it there and we do not read it, but saying flatly that no analytics script exists would not survive anyone checking.

2. The watcher

The OTC service includes an automated watcher that we run, because someone has to observe payments and execute deliveries. It reads public blockchain data only: offers, payments, and deliveries, the same things a block explorer shows anyone. Nothing reaches it from your browser, it sets no cookie, and it stores no personal data. It can tell no more about who you are than any other observer of a public chain.

3. What stays in your browser

The pages keep a small amount of state in your browser's local storage so you do not lose work. In full, that is: your language and theme choice; whether you connected a wallet last time and which wallet software it was, so the page can reconnect without asking; the source and destination chains you last picked on the bridge; the transaction hashes of your recent burns; the progress of an in-flight batch collection; whether you have already seen the first-run guide; and, on the market, the vault deposits made from the address you connected plus two counters recording how far your browser has scanned the chain for trade statistics and sale alerts.

These never leave your device, and clearing browser data deletes them. Note that the burn hashes are your recovery keys, so record them elsewhere if you clear data mid-transfer.

4. What is public anyway

Everything you sign is public on the blockchains involved: addresses, amounts, timestamps. That is a property of public blockchains, not of this site. Assume on-chain activity is permanently visible to everyone, including the fact that a given address bought or sold on this market.

5. Third parties the page talks to

Your browser talks directly to blockchain RPC endpoints and to Circle's public attestation API in order to compose and track transfers. Those services see your IP address and the addresses you query, under their own policies. The page's security headers list every host it may contact, and it can reach nothing else.

6. Contact

[email protected], or [email protected] for anything that should not be public.

No accounts, no KYC, no analytics. Static pages.