Privacy
What UplinkSwitch stores
- Account details from checkout: the email address and the amount paid, as Whop 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.
What it does not store
Request and response bodies. Prompts and completions pass through the gateway and are not written anywhere.
Who processes it
- Cloudflare runs the service and stores the data above.
- Whop runs checkout and payments and holds your payment details.
- 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.
- A host for open-weight models will be listed here before it is switched on.
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
This site sets none. 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.