Privacy Policy
Last updated November 2, 2026.
1. What we collect
| Category | Examples | Why |
|---|---|---|
| Account data | Email address, display name, sign-in provider identifier | To create and secure your account |
| Billing data | Purchase amounts, fees, any VAT or tax ID you enter at checkout, payment status, payment processor references; if you turn on auto top-up, your top-up settings and the card's brand and last four digits | To sell credits, run auto top-up and keep an accurate ledger. Full card details are entered with and held by our payment processor, never by us. |
| Request metadata | Model, token counts, cost, latency, status, error codes, timestamps, the API key used | To bill usage, show your activity log, detect abuse and operate routing |
| Request content | Prompts, files and completions you send through the API | To forward to the upstream provider serving the model and return the response |
| Technical data | IP address, user agent, cookies needed for sign-in and theme preference | Security, rate limiting and keeping you signed in |
| Sign-up credit record | When a sign-up credit is granted: the account, the amount, how the email was verified (email link, Google or GitHub) and a keyed one-way hash of the network address it was claimed from (for IPv6, the /64 prefix). We never store the address itself. | To give the credit once per person and network every 30 days, and prevent abuse |
2. Sign in with Google
If you choose "Continue with Google", Google shares the following with us, and only with your permission: your email address, whether Google has verified it, your name, a link to your profile picture and your Google account ID. We request only the basic email and profile permissions. We cannot access your Gmail, contacts, files or any other Google data.
- How we use it: to create your account and sign you in. Your email address identifies your account and receives service and billing emails. We do not currently display your name or picture.
- Where it is stored: with our authentication and database provider (see sub-processors below), for as long as your account is open.
- Sharing: we do not sell Google user data, share it with third parties other than the sub-processors that run the Service, use it for advertising, or use it to train AI models.
- Your control: you can remove our access at any time at myaccount.google.com/permissions, and ask us to delete your account and its data by emailing support@aimodelsrouter.ai.
AI Models Router's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
3. How request content is handled
- Our request log stores metadata only (see above). It has no fields for prompt or completion text, and the dashboard cannot show it.
- To serve a request, its content is sent to the third-party inference provider hosting the model. Our current inference provider states that it does not store model inputs or outputs on its infrastructure; its terms allow it to scan and retain relevant content when investigating abuse. Beyond what our providers commit to, we make no zero-retention or no-training commitments.
- Content may transit our infrastructure in memory and in transport logs needed to operate and debug the Service.
4. Sub-processors
We use carefully selected service providers (sub-processors) in these categories. Each processes data only to provide its part of the Service, under contract. We update this section before adding a new category.
| Category | Purpose | Data |
|---|---|---|
| AI inference providers (USA) | Running the AI models you call | Request content (prompts, files, completions) |
| Authentication and database provider (USA) | Sign-in and data storage | Account data, API key hashes, request metadata, ledger |
| Payment processor (USA) | Card payments, saved cards for auto top-up, fraud prevention | Billing data; card details are entered directly with the processor |
| Cloud hosting provider (USA) | Running our website and API | Request content in transit, technical data |
| Email provider | Sign-in links, low-balance and billing emails | Your email address and the content of those emails |
Business customers who need the names of our current sub-processors (for example for a data processing agreement) can request them from support@aimodelsrouter.ai.
5. API keys
We store only a SHA-256 hash of each API key, plus its first and last characters for display. We cannot show you a key again after creation.
6. Retention
Account data is kept while your account is open. Request metadata (model, token counts, cost, timing and status, never prompts or completions) is kept for billing, accounting and abuse prevention while your account exists, and longer where the law requires. Billing and ledger records are kept as long as tax and accounting law requires. A sign-up credit record is kept while the account exists, like the ledger entry it belongs to. Request content is not stored by us. You can ask us to delete your account by emailing support@aimodelsrouter.ai.
7. Your rights
Depending on where you live, you may have rights to access, correct, export or delete your personal data. Email support@aimodelsrouter.ai to exercise them.
8. Cookies
We use cookies strictly necessary to keep you signed in. Your theme and code-language preferences are stored in your browser's local storage. We do not use advertising cookies.