Privacy Policy
Effective October 30, 2026
Policy overview
Our underlying policy is that we want you to remain anonymous when using our service. We never store your prompts or model responses, and we keep as little data as possible. In some situations we process limited personal data, for example when you pay by card or send an email to support. This policy describes those cases.
What we never store
- Prompts, messages, model responses, and generated media
- Request and response bodies exchanged with model providers
- Activity logs of what you ask or which conversations you have
- Raw IP addresses in our application or access logs
- Full API keys, passwords, or recovery phrases
Request content is processed in memory only for the request that needs it and is gone when the request completes.
We use network information such as your IP address transiently to route requests, apply rate limits, and prevent abuse. On the public pages listed below, our self-hosted analytics service also uses the IP address and browser user agent transiently to derive a pseudonymous identifier that changes every day. We do not write raw IP addresses or full user agents to our application, access, or analytics logs.
Categories of personal data
Accounts
An anonymous account consists of a server-assigned username and hashed credentials. No email address or personal details are required or collected. A registered account additionally stores your email address and hashed password or OAuth identity. Either kind of account can also be linked to the visit that brought you here, as described under Campaign measurement below.
Payments
- Card (handled by our payment provider): charge ID, last four digits of the card, card type, amount, and status
- Bitcoin and Lightning: the invoice and transaction data needed to confirm the payment. Note that the Bitcoin blockchain is public.
Usage metadata
To settle your prepaid balance we record the model, token counts, cost, status, and timestamp of each request, linked to an opaque account identifier. This contains no request content.
Public website analytics
We collect limited first-party analytics on our public pages: the page path, timestamp, external referring domain, browser, operating system, broad device type, country, and clicks on sign-up, API-key, Chat, and documentation calls to action. Those clicks carry no link or form properties. Model, creator, and provider detail pages are recorded under their own catalog path, because which models people read about is what this measurement is for. Those paths are public catalog names, and a path that is not one is not recorded at all.
The Chat page records only that it was opened. No prompt, message, model response, attachment, conversation, or conversation identifier is ever sent to analytics, and your chats are not analytics data. Page analytics does not collect URL queries other than campaign labels, search text, account identifiers, Studio activity, payment activity, session recordings, heatmaps, or persistent visitor identifiers. No page analytics event is sent from authentication, account, Studio, recovery, payment, or receipt pages.
Campaign measurement
To learn which links bring people to AnonRouter, we read the campaign labels in the link you arrived from and note which of our main pages you visit. Advertising click identifiers are removed and not recorded.
This uses two first-party cookies that only control.anonrouter.ai can read, lasting 30 days: one connects your visits with a random identifier, the other remembers the campaign you came from. If you create an account in that time, we link it to your visit so we can count sign-ups and first milestones: your first API key, first successful request, and first payment and its amount.
For this we keep only the country of your first visit, looked up on our own servers, never your IP address, city, or precise location. Country data: IP Geolocation by DB-IP (db-ip.com).
Only a few authorized staff can see individual visits. We use no fingerprinting or third-party trackers and share nothing with advertising platforms. If your browser sends Do Not Track or Global Privacy Control, we stop recording your visits.
Support
Support by email: your email address and other information you have written in the email. Please do not include prompts, API keys, or recovery phrases when contacting support.
Contact form
When you send the Enterprise contact form on our pricing page, we store your name, work email, company if you give one, and message, encrypted, together with the monthly volume range you picked and the time it arrived. We use it only to reply to you about your request. The Connected apps developer form stores your name, reply email, app name, website or repository if provided, and integration request, all encrypted, with the same handling and retention. We do not store your IP address or browser details with it, and it is not linked to an account even if you are signed in. To keep spam out, your browser solves a small computational puzzle before sending, and a one-way code derived from your network address is kept for up to two days to limit how often the form can be sent. We are told that a new request arrived; the notice does not contain what you wrote. We never sell or share what you send with anyone.
How long is the personal data saved?
Account and usage records are kept while your account is active. When you delete your account, it closes right away, and the information that identifies you, such as your email address, username, and sign-in details, is erased after 7 days. Payment and usage records are then kept, linked only to an account number that can no longer be used to sign in, for 7 years after the end of the calendar year in which they were made. Security records, such as account restrictions, stay linked to that same number. If your account had an email address, we keep a one-way hash of that address for 12 months, only to stop repeated free sign-up credit; it cannot be turned back into your address. Payment data is kept as long as needed to handle refunds, disputes, and the statutory accounting retention periods that apply to us, after which it is deleted. Support emails are deleted once they are no longer needed to resolve the request. Contact form requests are deleted 180 days after they arrive, unless we are still working with you on the request, in which case we keep it only as long as that takes. Public website analytics events are deleted after 90 days. Individual campaign and visit records are deleted after 30 days, or sooner when an account is deleted. Campaign totals, which identify no one, are kept for up to 400 days. Copies can remain in database backups until those backups expire. Backups are not changed in place; if one is ever restored, account deletions are applied again before it is used.
Cookies and your device
We use first-party session cookies for account sessions and the campaign measurement cookies described above. Our self-hosted page analytics sets no cookie, writes nothing to local storage, and uses no advertising identifiers, cross-site tracking, or third-party analytics service. Browser Do Not Track and Global Privacy Control signals disable page analytics and campaign measurement. Chat and Studio can keep history in your own browser for convenience; Ghost Mode disables this, and clearing site data removes it. Deleting your account does not remove it, because it is not stored with your account.
Security
We apply reasonable technical and organizational measures designed to protect the limited personal data we hold, including encryption in transit, hashed credentials, and access controls. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
Third-party recipients
Personal data is shared only with suppliers performing services on our behalf: payment providers and, for request content, the provider of the model you select. Requests we forward are not tied to your account identity, and each model in the catalog shows a privacy label describing what its route guarantees.
Each provider processes the request content we forward under its own terms and privacy commitments, which we review before routing to it. On an Anonymous route the provider can see the prompt while serving it and its retention is not guaranteed; Private, TEE, and E2EE routes carry the stronger provider or cryptographic guarantee described on the route.
We do not sell your personal data, we do not share it for cross-context behavioral advertising, and we do not use it to build advertising profiles.
The rights of individuals
You can delete your account from Preferences. Anonymous accounts never need an email address to do this.
You may request access to, correction of, or deletion of personal data regarding you by contacting us at the address below. In most cases we will not be able to provide you with any data, since we do not store data that identifies you; an anonymous account was never connected to a person, and we cannot produce records that do not exist. We may need to verify that you control the account before acting on a request.
Children
The service is intended for adults. It is not directed to children, and we do not knowingly collect personal data from anyone under 18. If we learn that we have collected such data, we delete it. If you believe a minor has provided us personal data, contact us at the address below.
Contact information
AnonRouter is operated by Sunday Labs LLC, 30 N Gould St #56887, Sheridan, Wyoming 82801, United States.
To exercise your rights or ask a question about this policy, contact contact@anonrouter.ai.
Updates
This Privacy Policy may be updated and, in such case, a new version will be published on this website. See also the Terms of Service.