Trust and security
For a security review of SafeGrd. Each section links to the detail.
Where encryption happens
Your host compresses each backup with zstandard and encrypts it with Age (X25519 and ChaCha20-Poly1305) before upload. Writing a backup needs only the public key. Security and key custody has the details.
What SafeGrd never receives
- Your backup data. It never passes through SafeGrd’s server. A drill you set to run on SafeGrd restores on a machine started for that drill alone, destroyed when it ends, in a place the sub-processor list names.
- Filenames, table contents or email subjects.
- Your private key, with a customer-managed key.
- Database, mailbox and storage passwords, unless you choose to have SafeGrd hold them.
Choose how your key is managed
Each backup has its own data key, wrapped by your age key pair, the KEK (details). The console shows which mode you chose. Credentials are a separate choice.
| Mode | What it gives you |
|---|---|
| SafeGrd-managed key (the default) | SafeGrd keeps your key sealed and releases it only to your enrolled hosts, so you can restore even after losing a host. Each release is audited first. No console session, access token or administrator can retrieve it. |
| Customer-managed key | Only you can decrypt these backups. Keep a copy of the key file somewhere safe. |
| Credentials held by SafeGrd | Sealed per organization and sent only to your enrolled hosts when a surface backs up. They cannot be read back through the console or the API. |
Backups under Object Lock
S3 Object Lock in compliance mode stops anyone deleting a backup before its lock ends: your bucket’s root credentials, an AI agent’s token, and SafeGrd. Your plan or your retention settings set that date (Storage and retention). A bucket without Object Lock, such as DigitalOcean Spaces, locks nothing, and the console marks its backups Not locked. See Threat Shield and AI agents (MCP).
If SafeGrd is unavailable
Your hosts keep backing up on their own schedule. The CLI lists, verifies and restores from
your bucket without an account. safegrd restore --to-sql writes SQL that plain
psql loads, and every snapshot carries a plain-text RECOVERY.md
(what it holds).
RECOVERY.md gives the commands, including psql alone for PostgreSQL.License and continuity
The CLI and daemon are public at github.com/safegrd/cli under the Business Source License 1.1 (license), so you can check every claim on this page in the code.
- Listing, verifying, restoring and exporting your backups is allowed at any time, with or without an account.
- If SafeGrd stops running its service, all production use is allowed.
- Each version becomes GPL v3 four years after release.
Sign-in
- Passwords stored as bcrypt hashes. New accounts confirm their email with a 6-digit code.
- Session cookie
HttpOnly,SecureandSameSite=Strict. Every page has a Content Security Policy. - Two-factor sign-in (TOTP) with ten recovery codes, asked again before deleting anything, handing over an organization or canceling. An organization can require it of every member.
- TOTP secrets stored encrypted. Recovery codes stored only as keyed hashes.
Data protection
Data Processing Agreement (GDPR Article 28), sub-processors and what each can see, and the Privacy Notice.
Reporting a vulnerability
Email security@safegrd.dev. Do not test against other customers’ data. We take no legal action against good-faith reports kept private until fixed. Machine-readable contact: /.well-known/security.txt.