Legal
Privacy Policy
The short version: we never store what you send to or receive from a model. We keep the minimum needed to run accounts, meter usage and keep the service safe.
Draft for launch. Review with counsel before publication. Effective date: to be set.
1. Request content
Prompts, messages, system prompts, completions, tool-call arguments and embedding inputs are processed in memory for the duration of a request and are not written to disk, logs, databases or backups by Unrefused. This is the default for every account and cannot be switched off. Details and how to verify are in the zero data retention documentation.
2. Request metadata we keep
| Data | Purpose | Retention |
|---|---|---|
| Timestamp, request id, API key id, model, endpoint, status, latency | Operating the service, support, abuse prevention | 13 months |
| Token counts and computed cost | Billing and usage views | Life of the account plus statutory accounting periods |
| Policy profile reference and decision codes | Your audit trail of guardrail decisions | 13 months |
Decision codes record which classifier matched and how many values were redacted. They never contain the matched text.
3. Account data
We store your email address, workspace name, membership and role, hashed API keys (never the keys themselves), policy profiles you write, and session records for sign-in. Sign-in links are single-use and expire after 15 minutes; only their hash is stored.
4. Chat
The Chat page keeps conversation history in your browser's local storage. We hold no server-side copy. Clearing site data in your browser deletes it. Requests made from Chat are metered like any API request.
5. Cookies
One strictly necessary cookie, unr_session, keeps you signed in for up to 30 days. We do not use advertising or cross-site tracking cookies.
6. Service providers
We use infrastructure providers to host the gateway, model servers and database, and an email provider to deliver sign-in links and account notices. Providers process data only on our instructions. A current list is available on request.
7. Legal bases and transfers
We process account and metadata on the basis of performing our contract with you and our legitimate interest in running a secure service. Where data crosses borders we rely on recognised transfer mechanisms.
8. Your rights
You can access, correct, export or delete your account data, and object to or restrict processing where the law provides. Workspace owners can delete members and revoke keys at any time. Contact privacy@unrefused.com.
9. Security
Keys and tokens are hashed, sessions are httpOnly cookies, transport is TLS, and the logger strips content-bearing fields by construction. Report security issues to security@unrefused.com.
10. Changes
We will notify workspace owners by email before material changes take effect.