Security

When the platform says a key is stored securely, this is what we mean. We treat the API keys you bring (for example an OpenRouter key) as secrets, and protect them at every step below.

1. Encrypted at rest

Before a key is written to our database, it is encrypted using authenticated encryption (AES-GCM). The secret used to encrypt it is managed as a platform secret, separately from the application database — so a copy of the database alone does not expose your keys.

2. Write-only — never read back

Once saved, a key is never returned. It does not appear in any API response, it is not shown anywhere in the interface, and it cannot be read back — not even by you. The platform only uses it server-side to call the provider on your behalf. The only actions available afterwards are to replace it or delete it.

3. Isolated to your account

Your keys are bound exclusively to your account. The platform isolates data per account and per project, so one user's keys are never visible to another user or another workspace.

4. Deletion erases the secret

When you delete a key or a provider, the stored secret is erased. There is no archived copy left behind for that entry. Administrative actions on the platform are recorded in an internal audit log.

5. Infrastructure

The platform runs on Cloudflare's edge network (Workers and D1). For how we handle your personal data and your rights under the GDPR, see our Privacy Policy.

Questions about security? Contact us at office@universalmedia.pl.