Privacy Policy

Arctools has no account system, no sign-up form and no database of users. We do not collect, request or store:

• Names, email addresses, phone numbers or postal addresses. Nothing on this site asks for them.
• Account credentials, because there are no accounts.
• Your wallet's private key or seed phrase. Arctools cannot access these and will never ask for them.
• Payment details, because there is no fiat payment path. The service fee is paid onchain in USDC.
• Behavioural analytics, session recordings, heatmaps, advertising identifiers or cross-site profiles.

Your wallet address is read in your browser, so the interface can show your balance, read your token's state and build transactions for you to sign. Arctools runs no backend that stores wallet addresses: the only server-side endpoint the site exposes is a liveness probe that reports network facts and no request data. Your browser does talk to the third parties listed in section 4.

Two things are kept in your browser. Neither is a tracking cookie, and neither is used to profile you:

• Your theme preference (the localStorage key arctools-theme), so the site does not flash the wrong colours on your next visit.
• Your wallet connection, in a first-party cookie written by the wallet library when you connect (named wagmi.store), so you do not have to reconnect on every page load. It holds the address you connected with, the chain id and basic connector details — no private key, and nothing that can sign for you. It is scoped to this domain.

Disconnecting removes the connection from that record, and clearing your browser's site data removes both. Nothing else is lost. Our server code does not read the wallet cookie: pages render identically for everyone and your connection is reattached in the browser after the page loads.

Every Arctools service is a real transaction on Arc Mainnet, built in your browser and signed by you. That makes it permanently public — a property of the blockchain rather than of this site, and true of every wallet and application on the network.

• Your wallet address, the amounts, the token addresses and the destinations you send to are permanently visible on the Arc Explorer.
• That includes any address you enter as a bundle launch recipient, an airdrop recipient, a tax recipient or a fee recipient.
• The service fee is an onchain transfer to a treasury address fixed in the contract and public; for Token Manager, Revoke Ownership and Burn it is also recorded as a public, permanent receipt.
• We cannot delete, obscure or anonymise onchain data, and neither can anyone else.
• If you need privacy, do not put information on a public ledger that you would not want associated with your address.

Arctools is a front end, so using it means your browser talks to organisations we do not control. These are all of them:

• The Arc RPC endpoint. Reads and transaction submissions go from your browser to an Arc Mainnet node — by default the public endpoint at https://rpc.mainnet.arc.io, or a dedicated one if this deployment is configured with it. The endpoint sees your IP address and every query you make, including the addresses you inspect. Point your own build at your own node to avoid it.
• Your wallet. The extension or app you connect holds your keys and decides what it reports to sites; its own policy applies.
• WalletConnect, only for a mobile wallet session and only where this deployment is configured with a project id. Establishing the session shares your address and IP with the WalletConnect relay, which is operated by Reown. Connect a browser extension instead and the relay is never involved.
• Our hosting. The site is served from a private server behind a TLS-terminating reverse proxy, which sees the requests described in section 7.
• Search engines. Where they are configured, the site's HTML carries a Google Search Console verification tag and a Bing Webmaster Tools verification tag. Those tags collect nothing in your browser; they tell the two engines that this domain is ours, which is how we read the aggregate search data they already hold.

Web fonts are served from this domain rather than a font CDN, and no page loads a third-party script tag, tag manager, ad frame or embedded widget. Beyond the parties above, we do not sell, rent or share personal data, and we pass nothing to advertising networks or data brokers.

We measure how many people read which pages, in aggregate. That measurement comes from the access log of our own server — the log described in section 7 — and it is deliberately the least intrusive thing that answers whether anything is being read. It is not a tracking system:

• No third-party analytics script, tag manager or pixel is loaded on any page, and nothing is added to the HTML you receive in order to measure you.
• No cookie is used for measurement, and no advertising cookie is used anywhere.
• No cross-site or cross-device tracking. We cannot follow you to another site and do not try.
• No profiles of identifiable individuals: counts are per page and per day, not per person, and we do not record what you read or in what order.
• Your wallet address is never joined to traffic data — the two live in different places and are never combined.
• Measurement is used only to understand aggregate page traffic. It is not used for advertising, not sold, and not shared for anyone else's advertising.

Because this happens on the server rather than in a script in your browser, a browser ad blocker or tracking-protection list will not change it — those tools block third-party scripts and requests, and there are none here to block. We do not read Do Not Track or Global Privacy Control signals, because there is no client-side tracker for them to switch off, and we would rather say that than imply a switch that does not exist.

The route that does work is a direct one: email support@arctools.tech and we will tell you exactly what is counted, and exclude the address you ask about from the aggregate counts we produce.

Arctools sets no first-party advertising or tracking cookies, and we do not ask anyone to set cookies on our behalf. The only cookie this site writes is the wallet-connection record described in section 2. It is functional, it exists only because you chose to connect a wallet, and its only purpose is to keep that connection across page loads.

There is no consent banner because there is nothing to consent to: the one cookie is strictly necessary for a feature you asked for, and the measurement in section 5 uses no cookies at all. If we ever wanted an advertising or cross-site cookie, this page would have to say so before it appeared.

Third-party libraries triggered by your own choices — a wallet extension or a WalletConnect session — may write their own storage under their own policies.

The reverse proxy in front of this site writes JSON access logs to a file on the same private server. What matters is what is in the records, how long they are kept and what is done with them.

• Each record holds request metadata: IP address, timestamp, method, path, user agent, response status and the request headers your browser sent. Cookie and authorization header values are redacted by the proxy before a record is written, and this deployment leaves that redaction on.
• The log rotates at 20 MB and only the five most recent rotated files are kept — at most about 120 MB of history in total. Records beyond that are deleted as new ones are written, and are not archived anywhere else.
• Logs are used to keep the site available, to detect abuse and to produce the aggregate counts described in section 5. They are not used to analyse individuals.
• They are not correlated with wallet activity or with anything you do onchain, and are not shared with anyone except where the law compels it.

Privacy laws such as the GDPR and CCPA give you rights of access, correction, deletion, portability and objection over personal data held about you. Arctools holds very little: there is no account and no profile, so there is no history of your use of the tools to retrieve. What can exist is a log record of a request, and the aggregate counts derived from many such records.

You can ask what we hold that relates to you, and ask us to delete it. Write to support@arctools.tech and we can search the logs for the address you ask about and remove what matches. You can also exercise the practical equivalent yourself at any time by clearing your browser's site data for this domain.

Note that a request to delete onchain data cannot be honoured by anyone, including us, because the blockchain is immutable by design.

Arctools is not intended for anyone under 18, and we do not knowingly serve or collect information from children. There is no age verification because there is no account to register and no profile to create; the only personal data that can exist is the small amount described in section 7.

If this policy changes, the effective date at the top of the page changes with it, and material changes will be noted on the site. Anything that would put more data in someone else's hands — a new third party, a new thing measured, a new cookie — will be described here before it ships.

Privacy questions, including anything in section 5 or section 8, go to support@arctools.tech. The site this policy covers is https://arctools.tech. See also our Terms of Service.