Company / Trust and security

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.

Your host encrypts each backup and sends it straight to your bucket. SafeGrd receives only a record of it: sizes, checksums, row counts and drill results. your host encrypts each backup the backup, encrypted a record of it your bucket locked for the days you set SafeGrd sizes, checksums, row counts, drill results Your host encrypts each backup and sends it straight to your bucket. SafeGrd receives only a record of it: sizes, checksums, row counts and drill results. your host encrypts each backup backup, encrypted record only your bucket locked for the days you set SafeGrd sizes, checksums, row counts, drill results
The backup goes from your host to the bucket, on SafeGrd-hosted storage too. SafeGrd's server gets a record of it.

What SafeGrd never receives

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.

ModeWhat 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 keyOnly you can decrypt these backups. Keep a copy of the key file somewhere safe.
Credentials held by SafeGrdSealed 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).

While SafeGrd is unreachable, your host keeps backing up on its own schedule into your bucket, where each locked snapshot carries a plain-text RECOVERY.md. The safegrd CLI lists, verifies and restores from the bucket with no account. your host backs up on schedule SafeGrd unreachable your bucket locked snapshots, each with RECOVERY.md backups safegrd CLI list, verify, restore with no account reads
With the bucket and the key, the CLI restores without an account. 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.

Sign-in

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.