How your credentials are held

The API key you give us is the most sensitive thing you hand over. It is treated accordingly.

What happens to it

1. 1It is encrypted where it arrivesEncryption happens through a key management service the application can write to and cannot read from. The application holds no decryption key.
2. 2The ciphertext is storedThe database holds only the encrypted form. A database backup, or a copy of it, is not a set of working credentials.
3. 3It is decrypted only in the workerThe evaluation worker decrypts it in memory for the duration of a run, in a workload with a different identity from the one that stored it.
4. 4It is never returnedNo endpoint returns it. Not to you, not to an owner, not to staff, not to an administrator with a database console.

What you should do

• Issue a key scoped to the model being evaluated, if your provider supports scoping.
• Rotate it after a run if your policy calls for it. Nothing here depends on the old value.
• Never put a key in a URL. The connection test refuses that, and says why.