01
Authorize access.
Your client asks account services to check access and reserve credits. This request contains the model and usage limits, without your prompt.
Privacy, built in.
Think freely.
Ask privately.
Use the models you love from your terminal, an SDK, or your browser. AnonRouter routes your prompts through protected hardware, without logging them or using them for training.
No prompt logs Hardware-protected routing Open-source content plane
01 / Protected processing
A protected space
for your conversations.
AnonRouter handles your requests inside an Intel TDX enclave. It runs on the server, with memory protected from the host operating system and hypervisor.
HOST OPERATING SYSTEM
Same machine. Protected memory.
The host operating system manages the server. AnonRouter runs in an enclave on that same machine, with memory that Intel TDX isolates from the host operating system.
INSIDE THE ENCLAVE
Inside, it stays private.
Your encrypted connection opens inside the enclave. AnonRouter handles your prompts and responses there, without writing them to logs.
02 / Your identity stays separate
A ticket for your request.
Your identity stays behind.
Create an anonymous account and connect from your terminal, SDK, or browser. Account services authorize access and handle billing without receiving your prompts.
02
Issue a one-use ticket.
Your client receives a short-lived ticket authorizing the request. It can be redeemed once, replacing account credentials on the content request.
03
Send directly to the enclave.
Your client sends the ticket and prompt to the protected endpoint without account credentials. Account services receive usage metadata for billing, not your conversation.
Using a terminal, coding agent, or SDK? With a standard OpenAI-compatible client, you send your API key and prompt over HTTPS to the enclave. Authentication happens there; account services receive only authorization and billing metadata. You don’t need to request a ticket yourself.
Create a private account03 / Choose your protection
One API.
Four privacy levels.
Our no-logs promise applies across AnonRouter. Route labels show the additional protection from the provider, hardware, and encryption.
Anonymous
The provider can see your prompt while serving it, but your identity stays hidden.
Private
Prompt and response content is not retained after the request completes.
TEE
The model runs inside an attestable enclave, isolated from the infrastructure around it.
E2EE
Your client encrypts the prompt; only a verified enclave can decrypt it.
Applies to routesAnonymousPrivate
Protected by policy.
Anonymous routes hide your AnonRouter identity from the provider; the provider’s own content retention policy applies. Private routes add a commitment not to retain prompts or responses after the request.
Provider commitmentsPrivacy under the provider’s terms
Browse private modelsApplies to routesTEEE2EE
Protected by hardware.
The model runs inside an attestable enclave, with memory isolated from the host software. E2EE adds encryption from your client to the verified enclave, so only that enclave can open your prompt.
Attested hardwareA boundary you can independently verify
Browse TEE models04 / Verify it yourself
See the evidence.
Read the code.
Explore the public source, inspect your route’s attestation, and check the evidence behind its protection.
01
Inspect the code.
The confidential content plane is public. Read the code that handles your prompts inside the enclave, explore its tests, and inspect how the workload is built.
Explore the source02
Verify before you send.
Run verification from your terminal or application with the Confidential SDK. Check AnonRouter’s routing enclave and your chosen provider route separately, then make your request only when the results meet the protection you require.
Explore the Confidential SDK
03
Check the evidence.
Inspect the verification results and compare the measured workload with the expected release. Use the provider’s tools to check its hardware evidence independently. In web Chat, the attestation panel also lets you download the raw evidence.
Read the verification details05 / What remains afterward
The answer stays with you.
Your prompts stay out of our records.
Conversation content, usage records, and local history are different things. Here’s what happens to each.
CONTENT
No conversation archive.
AnonRouter doesn’t store your prompts or responses or use them for training. The model provider’s retention depends on your chosen route; Anonymous routes follow the provider’s own policy.
USAGE
Billing without the conversation.
We retain limited metadata such as the model, token counts, cost, and request status to bill for usage and operate the service. Your prompt and response are excluded.
ON YOUR DEVICE
Your client controls local history.
Terminal tools, coding agents, and SDK applications have their own history and logging settings. Our web Chat and Studio can save history in your browser; clear it, disable it, or use Ghost Mode to keep conversations out of local history storage.
For account data, website analytics, and retention details.Read the Privacy Policy
Your ideas.
Nobody else’s business.
Use the models you love. Keep your conversations yours.