Privacy
What Sable collects to run the service, how long it is kept, and what is never kept at all.
- Prompts and outputs
- Never logged, stored or used for training. They exist on our servers only while a request is being processed.
- Prompt cache
- When a request begins with the same text as an earlier one from your account, the model can reuse its internal state for that shared beginning instead of computing it again. That state is numerical, not text. It is used only for later requests from the same account and is discarded when newer entries need the space, usually within an hour to a few days.
- Your account
- Your name and email address, and your password, which our authentication provider stores only as a one-way hash. Each signed-in session records the IP address and browser it was created from.
- API keys
- Stored only as a one-way hash. The full key is shown once, when you create it.
- Usage and billing records
- The time of each request, the model, the usage and the amount charged, plus keyed one-way hashes of prompt beginnings to match the cache. None of it contains the request or the response. Billing records are kept after an account is closed, as accounting requires.
- Cookies
- Only the session cookie that keeps you signed in. There are no analytics, advertising or tracking scripts, and pages load nothing from other sites.
- Service providers
- Sable runs on third-party infrastructure: a database and authentication provider, and the servers that run the models. They handle data only as needed to provide the service. Sable does not sell your data or share it with anyone else, unless the law requires it.
- Your data
- You can revoke API keys at any time from your account. To see the account data we hold or to close your account, write to support@sableapi.com.
- Changes
- If this policy changes, the new version is posted here with a new date.
Last updated 25 October 2026