⚡ LLM Pricing
Calculator Compare Trends Chat MCP API What's New Sign in
Draft, not yet in force. This is a template awaiting legal review; paid plans cannot be bought until it is in force.

Last updated 2026-11-01

Privacy Policy

This policy explains what personal data [ENTITY NAME] ("we", "us") holds when you use the LLM Pricing API service, why, for how long, and what rights you have. It is written for customers in the United States (including California residents under the CCPA) and, where it applies, the EU and UK (GDPR and UK GDPR). This document is a template awaiting legal review and is not in force until the notice at the top of the page is gone.

1. What we hold and why

DataPurposeRetention
Account email, organisation id, plan, billing status and Stripe customer and subscription referencesCreate and run your account, bill you, contact you about your accountUntil you delete the account
Service key (stored only as a SHA-256 hash and an 8-character prefix; the owner sees only the prefix)Authenticate your requestsUntil the key is rotated or the account is deleted
Provider keys you store for dispatch (encrypted at rest)Run your dispatch requests on your own provider accountUntil you remove them or the account is deleted
Usage events (endpoint, model, token counts, cost, time)Rate limits, budgets, usage and savings reportsUntil the account is deleted
Dispatch receipt metadata (model, provider, token counts, cost and status, never the prompt or the response)Audit and cost reporting for dispatch90 days
Support conversations and escalations (the messages you send the support assistant, with keys and secrets redacted before the assistant reads them)Answer questions and, on request, escalate to the ownerConversations you hold while signed in with your service key are kept against your organisation for 90 days after the last message, then purged; escalations and their action records for 365 days; redacted summaries of inputs and outputs for 90 days
Network address (transient)Per-address rate limiting and choosing a display currency; kept in memory and not written to the databases. To estimate your country for currency and usage analytics, the address is sent to a third-party IP geolocation service (ip-api.com)Cleared on restart; the geolocation service applies its own retention

We do not sell personal data and we do not use it for advertising.

2. Who receives it

We use the service providers listed on the Subprocessors page: a hosting provider, a payment processor, an IP geolocation service and the language-model provider that runs the support and pricing assistants. Support messages reach that language-model provider after redaction of keys and secrets. We disclose data where the law requires it.

3. Your rights

You can ask us to: tell you what we hold about you, give you a copy of it, correct it, delete it, or stop processing it. California residents have the right to know, delete and correct, and to not be discriminated against for exercising these rights. Residents of the EU and UK also have the rights of access, rectification, erasure, restriction, portability and objection, and may complain to their data protection authority.

You can exercise the rights of access, portability and deletion yourself, without asking anyone, with your service key:

  • Export. GET /billing/account/export returns one JSON file with everything we hold about your organisation: your account record, metadata of the provider keys you stored (never the keys), usage events, dispatch receipts, budget alerts, routing history and the support conversations held under your key. It never contains your service key or another organisation's data.
  • Delete. POST /billing/account/delete with {"confirm": "DELETE", "org_id": "<your org id>"} permanently erases all of that and stops your key working at once. It is irreversible. If you have a paid subscription it is ended immediately, so no further charge occurs; if you delete within the refund window the owner is asked to review a refund and you receive a reference (see Refunds).
  • What remains. After deletion we keep a dated marker: a keyed hash of your email address and the time of deletion. The hash lets us recognise an address we have already erased and does not reveal addresses on its own. When the operator has configured one, the key includes a secret held outside the database, so a copy of the database alone cannot be used to test whether an address was deleted; otherwise someone holding our database could test whether a given address was deleted. The marker does not stop you signing up again. Deleting your account also anonymises the support escalation records tied to your organisation: what you wrote in an escalation, including any email address you typed there, is replaced with a removal notice, while the record's date, status and the owner's decision (but not the text of any reply to you) are kept for up to 365 days. Other records about the service itself (owner action records and the orchestrator log) do not name you, and Stripe keeps its own records under its own policy.

To correct your data, or for any request the endpoints do not cover, ask the support assistant on the chat page to escalate your request, or write to [CONTACT EMAIL]. We verify your identity before acting, normally by asking you to prove control of the account, and respond within 30 days.

4. Legal bases (EU and UK)

We process account and billing data to perform our contract with you, security and usage data for our legitimate interest in running a secure service, and any other data with your consent, which you can withdraw.

5. International transfers

The Service is hosted in the United States. If you are in the EU or UK, your data is transferred to the United States under the safeguards described in the Data Processing Addendum.

6. Security

Stored provider keys are encrypted, service keys are stored only as a hash, the Service is reachable only over TLS, and operator functions are restricted. See the Security statement for plain facts, including what we do not have.

7. Children

The Service is not directed to anyone under 16 and we do not knowingly collect their data.

8. Changes and contact

We will update the "Last updated" date when this policy changes. Controller: [ENTITY NAME], [POSTAL ADDRESS]. Contact: [CONTACT EMAIL].

Policies: Terms of Service Privacy Policy Refund Policy Data Processing Addendum Subprocessors Security FAQ Billing