What we collect, where it goes, and what you control.
Celexta routes AI requests to model providers. This page describes, in plain language, exactly what that involves for your data. Last updated July 10, 2026.
The short version
- Every request produces a routing event — the model asked for and served, token counts, latency, status, and price. These events contain no prompt or response text.
- With Improve my routing on (the default, shown at signup and in Settings), your prompts and responses power your prompt history and improve routing. You can turn it off at any time.
- Independent of that setting, Celexta keeps a restricted operational copy of each request and its response, for operations and legal compliance. It is never used for training, never shown in the product, and we delete it on request.
- Your prompt is processed by the model provider that serves it. You choose, per key, which regions may serve — including whether China-based providers are allowed.
- We do not sell your data, and we do not show ads.
What we collect
Account data
Your email address and authentication records, held with our database and authentication provider (Supabase). Payment details live with our payment processor (Stripe); Celexta never stores card numbers.
Routing metadata — every request
Each request produces an event recording the model requested and served, the provider, token counts, latency, HTTP status, the billed amount, and the routing geography. These events power your activity view, receipts, spend caps, and billing. They are content-free by design: prompt and response text never enters them.
Request content — two separate stores
Product store (your choice). When the Settings toggle “Improve my routing cost & performance” is on — it is on by default and disclosed at signup — Celexta stores prompts and responses to power your per-key prompt history and to improve routing quality and cost. Turning it off stops new content from entering this store and stops any training use. There is no automatic expiry; we delete it on request.
Operational archive (not optional — disclosed here). Independent of that setting, Celexta retains each served request and its full response — including intermediate model output that is not returned to you, such as reasoning traces — as a restricted operational record, kept for operations and legal compliance. Access is restricted within Celexta; the routing service and the product never read from it; it is never used for training. Records leave the archive in exactly two cases: you ask for your own data, or we must respond to valid legal process. There is no automatic expiry; we delete your records from it on request, subject to any legal hold.
Feedback you submit
If you approve, correct, or reject a response through the feedback API, we store that verdict. The text of a correction is only stored when the product store above is on.
Surface inputs
The Excel add-in sends only the text you explicitly paste or select for extraction — nothing else is read from your workbook. Those requests are handled like any other request above.
Where your prompts go
Celexta is a router: your request is dispatched to a model provider’s endpoint, and that provider processes it under its own terms. The provider that served each request appears on your receipt and in the x-celexta-routed-to response header.
You control the serving regions per key. The default Global setting includes China-based providers — this is labeled when you create the key, and your choice is recorded before the key is issued. You can restrict any key to exclude China, or to US-hosted lanes only. Prompts on a key are only sent to providers in regions that key allows; keys with no recorded choice are served from US and EU regions only.
If you bring your own provider key, requests pinned to that provider are dispatched on your key, under your own agreement with that provider.
Subprocessors
| Model providers | Inference — serve the requests you send. Scoped per key by your routing-geography setting (see above). |
| Supabase | Database and authentication. |
| Railway | API hosting (the router). |
| Vercel | Website and console hosting. |
| Stripe | Payments. Celexta never stores card numbers. |
| 1984 Hosting | Transactional email (sign-in codes, account notices). |
Retention at a glance
| Data | Kept | Your control |
|---|---|---|
| Routing events (no content) | While your account is active | Account deletion |
| Prompt history & routing-improvement store | No automatic expiry | Settings toggle stops new collection; deletion on request |
| Operational archive | No automatic expiry | Deletion on request (subject to legal holds) |
| Account & billing records | While your account is active | Account deletion |
Your controls
- Settings → Data controls: turn prompt history and training use off (or back on) at any time.
- Per-key routing geography: choose which regions may serve each key, set when the key is created.
- Provider preferences: deny any provider account-wide in Settings; a denied provider is never used.
- Export: ask for an export of your own stored request records at fnd@celexta.com.
- Deletion: ask us to delete your stored content — including the operational archive — at fnd@celexta.com. Account deletion removes account data as well.
What we don’t do
- We do not sell your data or share it for advertising.
- We do not train on your content when the data-controls toggle is off.
- We do not put prompt or response text into routing events, receipts, or analytics.
- We do not hand data to anyone outside the subprocessors above except in response to valid legal process.
Changes and contact
When our data practices change, this page changes with them and the date at the top is updated; material changes are announced to account email addresses. Questions, export requests, or deletion requests: fnd@celexta.com.