Engineer-to-engineer: the guarantees, listed
A security page should be falsifiable, and it should not be a map. Every item below is a property you can put to the test in a technical evaluation, and we expect you to. The implementation behind each one is in the security pack, which we hand over under NDA rather than publish to everyone who can open a browser.
Keys are not recoverable from storage
API keys are never held in a form that can be replayed. Verification works against a one-way transformation of the key, so an attacker who walks off with the store walks off with nothing that authenticates.
Secrets shown once
A key is displayed at creation and never again, because we cannot show it again. Rotation is self-service, and losing a key means issuing a new one rather than asking us to look it up.
Expiry and revocation
Keys can carry an expiry date, so an integration you are still building gets a credential that dies on its own. Revocation takes effect on the next call, with no grace period to wait out.
The console holds nothing in the browser
Console authentication is established and validated server-side; no long-lived credential is handed to the page for JavaScript to lose. Yes, the leaked-cookie people worry about their own cookies. Professionally.
Tenant isolation
Every read is bound to the organization that made it, and the binding is enforced on the server on every request rather than assembled by the client. An organization sees the modules and watchlists it holds, and nothing lateral.
Access to the corpus is audited
Searches against the credential corpus are recorded with the caller, the query, the filters and the result count, alongside the lifecycle of every API key. Your organization can read its own history directly. Our staff access is recorded under the same regime and reviewed internally.
Encrypted in transit and at rest
External traffic is TLS-only. Storage is encrypted at rest, and service-to-service traffic inside the platform is authenticated and encrypted rather than trusted for being internal.
Responsible disclosure
security.txt is published and reports get a human response. We fix, credit and disclose in coordination with the reporter.
Probe every claim on this page.
Your engineers are welcome to try.
NDA-friendly briefings · global coverage · no slideware