Averium Route

Draft — requires legal review

This text is a working draft, not yet reviewed by counsel. Values in [brackets] are placeholders.

Legal · privacy

Privacy Policy

Last updated [Effective date]

This policy explains what personal data [Company legal name] collects when you use Averium Route, why, and the choices you have.

1.The short version

  • We do not store the content of your prompts or of model responses. We keep metadata about each request so we can bill it and show it to you.
  • Chat conversations are saved only in your browser, on your device.
  • The provider that serves a request receives its content and may retain it under its own policy.
  • We don't sell personal data, don't use it for advertising and don't train models on your content.

2.What we collect

  • Account data: your name, email address, whether it is verified, organization name, role, and a hash of your password (never the password itself).
  • Request metadata: for each API or Chat request, the time, organization, key, model, provider, token counts, cost, latency, status and error code, request id and the client IP address.
  • Billing data: top-ups, ledger entries and payment status. Card details are collected by our payment processor (Stripe); we never see the full card number.
  • Security data: sign-in and sign-up attempts, IP address and browser user agent, used to stop abuse and protect accounts.
  • Cookies and storage: one session cookie to keep you signed in, and browser storage for preferences (theme, table density) and Chat conversations. We use no advertising or analytics cookies.

Sign-up is protected by Cloudflare Turnstile, which processes signals from your browser to tell people from bots under Cloudflare's privacy policy (opens in a new tab).

3.Prompts, responses and Chat

The content of your requests (prompts, system messages, files) and of the responses passes through our servers in memory on its way to and from the provider. We do not write it to our databases or logs, and our staff cannot read it afterwards.

Chat in the dashboard keeps conversations only in your browser's storage, on your device. Clearing your browser data deletes them; we have no copy to restore.

4.Model providers

To answer a request, we send its content to the provider that serves the chosen model (or the model automatic routing picks). Each provider processes it under its own terms and privacy policy and may retain it for a period, for example to monitor abuse. The providers we route to and their policies are listed at [provider policy page URL].

Don't send special categories of personal data (health, biometrics and similar) or data you are not allowed to share unless the provider's terms permit it.

5.How we use data

  • To run the service: authenticate you, route and meter requests, enforce budgets and show usage (performance of our contract with you).
  • To bill and keep accounting records (legal obligation).
  • To secure the service, prevent fraud and abuse, and enforce rate limits (legitimate interest).
  • To send service email: verification links, password resets, receipts and budget alerts (contract and legitimate interest). We send no marketing email without your consent.

6.Who we share data with

  • Model providers: request content and the minimum metadata needed to serve it.
  • Our processors: hosting, the payment processor, the email delivery service and Cloudflare (bot protection), under contracts that limit their use of the data.
  • Authorities, when the law requires it.
  • A buyer or successor, if our business is sold or merged, under this policy.

Data may be processed outside your country. Where the law requires it we rely on appropriate safeguards, such as standard contractual clauses.

7.How long we keep it

  • Account data: while your account exists, then [account retention period].
  • Ledger and billing records: [accounting retention period, e.g. 7 years], as tax and accounting law requires.
  • Request metadata: [request metadata retention period].
  • Security logs: [security log retention period].

8.Security

Traffic is encrypted in transit. Passwords are stored as salted hashes and API keys as hashes; a key is shown in full only once, when it is created. Access to production systems is limited to the people who need it.

9.Your rights

Depending on where you live, you can ask to access, correct, export or delete your personal data, and object to or restrict some processing. Write to [Contact email]; we answer within 30 days. You can also complain to your data protection authority. Some records, such as the ledger, must be kept for the legal period even after you close your account.

10.Children

The service is not meant for anyone under 18, and we don't knowingly collect their data.

11.Changes to this policy

We tell you about material changes by email or in the app before they take effect. The date at the top shows the latest version. See also the Terms of Service.

12.Contact

The controller of your personal data is [Company legal name], [Registered address], [Jurisdiction]. Privacy questions and requests: [Contact email].