Security
How we handle your data and who can touch it.
This page describes how the platform behaves. We don't claim certifications or third-party audits here; when we have them, they will be listed with dates.
Data
Nothing reaches a storage backend unencrypted. Records are sealed with XChaCha20-Poly1305, an authenticated cipher from audited open-source libraries. We did not write our own crypto, and we don't intend to.
Every bucket has its own key. Objects are sealed in 64 KiB chunks, each bound to the object it belongs to, so a chunk can't be moved or reordered without the read failing. Delete a bucket and its keys go with it.
Tokens and keys are stored as hashes or not at all. You see a secret once, when it is created, and it never appears in a log.
Access
Every request is authenticated and then checked against roles. If no role allows it, the answer is no. Roles are bound to people, groups and service accounts, and a role on a billing account carries down to its projects.
You can turn on two-step sign-in with a time-based code from any authenticator app, plus recovery codes. Access is shared with single-use invitation links that expire after 1 to 30 days, and an invitation can never grant more than the person who sent it holds.
Records
The audit log records every create, update and delete, and every refused attempt, with who and when. Request bodies are never stored, so a secret can't leak into it by accident.
The status page probes the public endpoints every minute and shows what it finds.
More detail for builders: team access, two-step verification, service accounts and token rotation.