Effective: 2026-09-14 (v1, testnet)
This page describes what data the arcns websites, API and contracts handle. arcns is operated by Fortiblox. It is an independent project, not affiliated with Circle Internet Group or the Arc network.
This documentation site
docs.arcns.io is a static site export: it sets no third-party cookies, runs no analytics and has no accounts. It does load first-party client JavaScript for the docs interface itself (navigation, search, theme). The only thing it can log is the web server's request line (path, status, timestamp) and the connecting IP address, kept in rotating server logs for at most 30 days.
Cloudflare
Requests to docs.arcns.io and api.arcns.io pass through Cloudflare's network before they reach our server. Cloudflare sees your IP address, request headers and TLS metadata and processes them under its own policy: Cloudflare privacy policy. We use Cloudflare for TLS, DDoS protection and rate limiting only.
The resolver API
api.arcns.io logs, per request: the client IP address (as passed by Cloudflare), the user agent, the path, the status code and the timestamp. When a call is paid for over the x402 protocol — the mechanism automated/agent callers use to pay per request in USDC, currently $0.001 — the log additionally includes the paying wallet address, the transaction hash and the amount; that is the same information the payment itself already made public on the chain. Browsers and holders of a free API key are not charged and do not generate that entry. These logs are used for rate limiting and abuse prevention only, are not shared, and are deleted after at most 30 days. The API keeps no accounts and no cookies; a free API key is a static credential we issue directly, out of band, and is not tied to any personal information.
On-chain data is public by design
Names, address records, text records, primary names, transfers, listings and every other action executed through the arcns contracts are written to the Arc chain. That data is public, permanent and replicated by every node; it is readable by anyone and cannot be deleted or edited by us. Before you set a record, assume everyone can see it forever.
The app and wallet
The user-facing app (app.arcns.io) is live. Connecting an existing wallet, or creating an embedded one, is handled by Privy, a third-party wallet infrastructure provider: Privy processes whatever that involves (a wallet address, and for an embedded wallet, the login method you choose) under its own policy: Privy privacy policy. arcns's servers do not see your Privy login credentials.
Gifting a name to an email address is the one place arcns's own servers handle an email address you type in: it is sent to Privy to create or find a wallet for the recipient, and used only to prepare that gift's claim link. If a claim-notification email is sent, it goes out through a third-party delivery provider (Resend) rather than arcns's own infrastructure. That email address is not added to a mailing list and is not used for anything else.
What we do not do
- We do not sell personal data, or share it with third parties for their own marketing or advertising purposes. The service providers named above (Privy, Resend) process data only to provide the specific feature they're named for.
- We do not build profiles or track users across sites.
- We do not run a mailing list or send marketing email; the only email arcns's servers ever touch is a recipient address you provide yourself when gifting a name (see "The app and wallet" above).
Your rights and contact
If you are in a jurisdiction that gives you rights over personal data (for example the GDPR), you can exercise them for the server logs described above; we cannot alter on-chain data. Contact: [email protected]. Do not post secrets or private keys there.
Changes
We may update this page. The effective date at the top is the version you are reading; the history is in the repository.