Privacy
What UplinkSwitch stores
- Account details from checkout: the email address and the amount paid, as our payment processor reports them.
- API keys as a salted hash, with the key name, status, limits and timestamps. The key itself is shown once and not stored.
- Provider keys you store for bring-your-own-key mode, encrypted with AES-256-GCM.
- One usage record per request: request id, model, host, mode, token counts by class, the source of those counts, and the charge.
- The ledger of balance changes: top-ups, charges, refunds and disputes.
- SHA-256 fingerprints, never the text: of each request and response, so a signed receipt can show what was billed; and of large system prompts, kept 7 days, to find prompts many accounts send and cache them for everyone. A request sent with the header x-uplink-crowd-cache: off is not fingerprinted for caching.
- Where your first visit came from: the referring site, the link's campaign tags and the page you landed on, saved with your account when your first sign-in creates it, and passed to our payment processor with each checkout.
What it does not store
Request and response bodies, unless you turn on replay for a key, which keeps that key's request bodies for 7 days. Otherwise prompts and completions pass through the gateway and are not written anywhere.
Who processes it
- Cloudflare runs the service and stores the data above.
- Our payment processor runs checkout and holds your payment details. UplinkSwitch never sees your card number.
- Our payment processor's analytics script runs on uplinkswitch.ai and records which pages a visitor viewed before a purchase. It sends page URLs and a browser identifier to the processor, not request or response content.
- Every model on the Models page, Claude, GPT and Gemini as well as the open-weight models, is served by third-party model hosting providers under contract with UplinkSwitch. They receive the request and response content for those calls.
- In bring-your-own-key mode, your requests go to Anthropic, OpenAI or Google on your own account, under your own agreement with that provider.
Provider keys
A stored provider key is decrypted only to forward your request. The API never returns it. Write to hello@uplinkswitch.com to have one removed from the vault.
Retention
Keys and provider keys are kept while the account is open. Usage records and ledger entries are kept as accounting records after it closes.
Cookies
Signing in to the console sets a cookie that keeps you signed in, and one that remembers which organization you picked. A referral link sets one that holds its code for 30 days. Your first visit sets one for 90 days with the site that sent you, the campaign tags in the link (utm_source, utm_medium, utm_campaign) and the page you landed on; when your first sign-in creates your account, they are kept with it. Your theme choice is kept in your browser's local storage and never sent to a server.
Changes
The date at the top changes when this page does. Questions go to hello@uplinkswitch.com.