Security
What protects your data, where it lives, and — because you will ask in diligence — what we have not built yet.
Tenant isolation
Every record Operant stores belongs to exactly one organisation, and the database enforces that with row-level security rather than leaving it to application code. A query that forgets a tenant filter returns nothing, instead of returning someone else's data.
Credentials
- Provider keys are encrypted with AES-256-GCM before storage, decrypted in memory only to make a call you asked for, and never returned to the console or written to a log.
- Passwords and API keys are stored only as one-way hashes. An Operant key is shown once, at creation; we cannot recover it for you.
- Transport is TLS throughout.
Where it runs
Google Cloud, region asia-south1 (Mumbai). Model calls reach providers
in the United States. We are an Australian company and our infrastructure is not in
Australia — if your policy requires onshore residency, say so early, because today we
do not meet it. Section 7 of the Privacy Policy sets this out in
full, along with the sub-processor list.
What we have not built
Diligence goes faster when this part is written down rather than extracted.
- No SOC 2, ISO 27001 or equivalent certification. We are pre-seed; there has not been an audit and we will not imply one.
- No automated retention or deletion. Stored traffic data does not expire on a schedule yet. We delete on request, manually, within 30 days.
- A small team can reach production. Access is not yet role-separated in the way a larger organisation would require.
Reporting something
Write to security@operantlabs.com. Tell us what you found and how to reproduce it. We will not pursue anyone acting in good faith to make this safer.