Privacy policy

Draft for legal review. Replace the bracketed parts and have counsel review. Edit /etc/tcpai/legal/privacy.html on the server.

[Company legal name] ("we") operates tcpapi. This policy says what we collect, why, and for how long.

What we collect

• Account: your email address, account number, API key fingerprints (we store a one-way hash of each key, never the key) and a record of account actions.
• Usage: for each request: time, model, input and output token counts, price, cost, which backend served it, whether a failover happened, and its receipt hash. We use these for billing, your usage history, reconciliation and abuse prevention.
• Payments: handled by Stripe. We receive the amount, status and Stripe identifiers, not your card details.
• Technical logs: IP addresses and request paths in web server and application logs, kept for security and debugging.
• Cookies: one session cookie to keep you signed in. No advertising or analytics trackers.

Prompts and outputs

The exchange does not store the content of your prompts or of the model's answers. Content is held in memory while the request runs (including, if a backend fails, to let a replacement continue the answer) and is then discarded. The backend that serves a request receives your prompt to generate the answer. Backends we operate do not log content. Third-party backends [list providers] process content under their own terms: [links].

Who we share data with

Stripe (payments), [email provider] (sign-in emails), the model backends that serve your requests, and authorities when the law requires it. We do not sell personal data.

Retention

Account and usage records: while your account is open and [period] after, for accounting and legal obligations. Technical logs: [period]. Encrypted backups: up to [period].

Your rights

You may ask for a copy of your data, its correction or its deletion (subject to records we must keep) at [contact email]. [Add jurisdiction-specific rights, e.g. GDPR/CCPA, and the supervisory authority.]

Security

Traffic is encrypted with TLS; API keys are stored as hashes; services run isolated with least privilege; backups are encrypted.

Last updated: [date]. Contact: [contact email].