Data and privacy

Sonoe's API keeps almost nothing from your requests.

What we keep

For each request, only:

• the number of tokens it read,
• the number of questions,
• how many milliseconds it took,
• which account and key it was charged to, and when.

That's what the console's usage pages show and what quotas are counted from.

What we don't keep

• The state, the questions, the options and the answers are not stored. They're processed in memory and discarded when the response is sent.
• Nothing to train on. Since the text isn't stored, your requests can't be used to train Sonoe.
• No request bodies in logs.

Keys

API keys are stored as a SHA-256 hash, never in clear. The console shows only the first characters of each key so you can tell them apart; the full key is shown once, when you create it. A revoked key stops working immediately.

In transit

Every request goes over HTTPS. The API runs at api.sonoeai.com, separate from the console.

Your responsibility

Send Sonoe only what the decision needs. If a state contains personal data, it's processed (not stored) to answer your questions, so make sure your own privacy policy covers sending it to a service like Sonoe. Use keys only from your servers.

Your usage history and your keys are in the console at sonoeai.com, where you can also revoke keys and delete your account.