Skip to content
Pending legal review. These documents are a complete draft, but they have not been reviewed by a lawyer and are not legal advice. Have counsel review and adapt them for your jurisdiction before this service accepts real money.

Privacy policy

Last updated: 2026-09-20.

What SurgeX stores about a request

For every request, the following metadata is retained:

  • Request id, timestamp and the API key used
  • Requested model, and the model and provider that served it
  • Token counts, latency, cost and HTTP status
  • The routing receipt: task class, complexity tier, routes considered and attempted

What SurgeX does not store

Prompt and completion bodies are not retained. The database columns for them exist and are left null. Retention can be enabled by an operator through the LOG_REQUEST_BODIES setting, which is off by default; if a deployment turns it on, that deployment's privacy statement must say so.

The routing receipt returned with each response contains operational facts only. It never contains prompt content or model reasoning.

What upstream providers receive

Your prompt is forwarded to whichever provider serves the request, and that provider's own privacy and retention policy applies to it. SurgeX cannot control or shorten an upstream's retention. The response header x-surgex-provider names the provider on every request, so you can always tell where your data went.

Auto-routing classification runs locally inside SurgeX. No part of your prompt is sent anywhere in order to decide which model to route to.

Account data

An account may hold an email address or a wallet address, plus its ledger of deposits and charges. Deposit records include on-chain transaction hashes, which are public by nature.

Retention

Request metadata is retained for 90 days for operational purposes, debugging, abuse investigation and capacity planning. Ledger entries and the records needed to substantiate them are retained for seven years, which is the common floor for financial record-keeping; the exact obligation depends on where the operating company is established. Prompt and response bodies are not retained at all.

Your rights

You can ask for a copy of the data held about your account, ask for it to be corrected, and ask for your account and its request metadata to be deleted. Ledger entries cannot be deleted on request: they are the financial record, they are append-only by design, and keeping them is a legal obligation rather than a choice.

To make any of these requests, write to [email protected] from the email on the account, or from a message signed by the wallet the account was created with.

The specific rights you have, and the deadlines we must answer within, depend on where you are and where SurgeX Network operates. GDPR, the CCPA and similar regimes each set their own, and counsel should confirm which apply before this policy is relied on.

Privacy policy · SurgeX