Privacy Policy

What we store

Your account

Your name, your email address, and a hash of your password. Sessions are kept as a cookie in your browser and a session row on our side so we know you are signed in.

Your API keys

Keys are shown to you once, at creation, and never again. We store a one-way hash of the secret plus a short display hint (the mc-v1-… prefix and last few characters) so you can tell your keys apart in the dashboard. We cannot recover a key you have lost; you have to issue a new one.

Your provider keys (BYOK)

Provider API keys you connect are stored encrypted (AES-256-GCM), decrypted only in memory to authenticate your own requests, and never logged or displayed again — the dashboard shows only a short hint (the first and last few characters). Removing a key, or deleting your account, deletes the stored ciphertext.

Usage metadata, per request

Every call through the gateway writes one row so that your usage log, spend guardrails and routing work. That row holds:

• which model and which upstream provider served it;
• which of your API keys was used;
• whether it ran on your own provider key, and — for modelcards/auto — the routing tier and complexity score;
• prompt and completion token counts;
• the estimated upstream cost (what your provider bills you);
• latency, whether the response was streamed, and a timestamp;
• whether it succeeded, and — if it failed — the error message the provider returned.

What we do not store

• Prompt and completion content. Your messages are held in memory only for as long as it takes to forward the request and stream the response back. Once the response completes, the content is not written to our database — only the metadata listed above.
• Playground history stays in your browser. The chat transcript on /chat is saved to your own browser's localStorage so a reload does not lose it. It never leaves your machine except as the request being sent. Clearing the conversation, or your browser storage, erases it.
• Payment details. There is nothing to pay us during beta, so we hold no card or billing information at all — your inference is billed by your own providers.

What we never do

• We do not train on your data. Not your prompts, not the completions, not your usage patterns.
• We do not sell your data or share it with data brokers, advertisers or model vendors for their own use.
• We do not read your traffic for any purpose other than serving and billing it.

Who else sees your request

The upstream provider that serves a request necessarily receives its content, and handles it under their own privacy and retention policy — which, since the request runs on your own account with them, is the policy you already accepted as their customer. The model card for each model names the providers that can serve it, and modelcards/auto only routes within providers you have connected. We pass along your prompt and the model parameters; we do not pass along your name or email.

Beyond that, we share data only with infrastructure suppliers needed to run the service (hosting), and where the law requires it.

How long we keep it

Account details and keys live as long as your account does. Usage rows are kept so your usage history and routing statistics stay accurate. Since request content is never persisted, there is nothing to expire.

Deleting your account

Deletion is self-serve, from the settings page of your dashboard. It is a full cascade: your user record, API keys, stored provider keys and usage history are removed together. Deletion is irreversible and there is no recovery window.

You can also export or ask about the data we hold on you at any time by emailing support@model.cards.

Cookies

We set a session cookie when you sign in, and store your theme preference locally. There are no advertising cookies and no third-party analytics trackers on the site.

Changes

If we start storing something new — request content for a debugging feature you opt into, for example — this page changes first and the date at the top moves with it. We will email account holders before a material change takes effect.

Contact

Privacy questions, data requests and complaints: support@model.cards.