Security

Security starts with less data.

AnonRouter is built to protect your requests by minimizing what exists to protect. Prompt and response content is never retained on our servers.

Server-side content retention
None
Third-party analytics
None
API key storage
One-way hashed

Platform controls

Defense in depth, without the surveillance layer.

The controls below are designed around the data AnonRouter actually handles, from account authentication to provider routing.

Content stays transient

Prompts, model responses, generated media, and provider payloads are processed for the request and never written to application logs, databases, or caches.

Credentials are protected

Passwords and recovery proofs use Argon2id. API keys and session tokens are random secrets stored only as keyed, one-way hashes—not recoverable plaintext.

Browser requests are constrained

First-party sessions, origin checks, a nonce-based content security policy, no-referrer responses, and no-store documents reduce common browser attack paths.

Abuse controls preserve privacy

Layered request, account, API-key, provider, and model limits protect expensive paths without retaining raw network addresses or inspecting prompt content.

Routing respects privacy floors

Provider fallbacks are bounded and never silently weaken the privacy level a request requires. E2EE is used only through an explicitly verified, supported route.

No tracking layer

AnonRouter uses first-party session cookies only. There are no advertising pixels, behavioral analytics, or third-party tracking cookies on the site.

Request lifecycle

A smaller data trail by design.

Request content has one job: reach the model you selected and return the result. It does not become a server-side conversation history.

  1. 01

    Authenticate

    Your API key is checked against its one-way hash. The key itself is never sent to a model provider.

  2. 02

    Process in memory

    The request is routed within your privacy boundary and passed to the selected provider without your account identity.

  3. 03

    Return, then forget

    The result is returned to you. Only payload-free usage metadata needed for billing and reliability is retained.

Found a security issue?

Please report it privately so we can investigate. Include the affected surface, expected and observed behavior, reproducible steps, impact, and any relevant request IDs or timestamps.

contact@anonrouter.ai

Keep sensitive data out of reports

Never send live API keys, passwords, recovery phrases, payment details, prompts, or model responses. Use redacted examples and stop testing if you encounter another person's data.

Need product support instead?
Security — AnonRouter