Privacy

Last updated: 19 August 2026

In short: dsco-router is an LLM routing control plane. We keep the minimum account, routing, and billing data needed to operate your workspace. Provider credentials are encrypted at rest; API keys are stored as one-way hashes; prompts and model responses are not stored in usage logs.

Account data

When you create an account, we store your email address, account profile, and a password hash if you choose password sign-in. If you sign in with Google, we store the verified email, provider identity reference, display name, and avatar URL returned by Google. We use this information only to authenticate you and present your account.

Provider credentials and routing

Direct provider API keys you connect are encrypted before storage and are only decrypted inside the router to make a request for your workspace. We record request metadata such as selected model, provider, token counts, status, timestamp, and cost for usage and billing. We do not store prompt or response content in usage logs.

Payments

Credit purchases are processed by Stripe. dsco-router receives payment completion events and stores the resulting credit ledger entry; it does not receive or store card numbers or bank credentials.

Google Sign-In

Google Sign-In is used only to establish your dsco-router identity. We request standard identity information needed for sign-in, not access to Gmail, Drive, Calendar, or other Google account data.

Sharing and retention

Inference requests are sent to the provider lane selected for your workspace, such as a direct provider account or the DSCO-managed cloud lane. We do not sell account or Google identity data. Data is retained while the workspace is active so that account access, billing, and usage records work correctly.

Questions

For privacy questions or account support, contact the operator of the dsco-router deployment.