Legal / Sub-processors

Authorized Sub-processors

Last updated 31 October 2026.

Overview

Under Article 28 of the GDPR and our Data Processing Agreement, SafeGrd engages third-party service providers (“Sub-processors”) to run our service, store backups for customers who choose SafeGrd-hosted storage, run restore drills for customers who choose to run them on SafeGrd, and deliver account email.

SafeGrd reviews a Sub-processor's security and privacy practices before engaging it: its security certifications, its confidentiality obligations and its data protection terms, which must be no less protective than our own.

What Sub-processors can see

Customer backup contents (database tables, files and mailbox messages) are compressed and encrypted on the customer’s own host before they leave it. Our object storage provider stores hosted backups only as that ciphertext.

With a SafeGrd-managed key, the default for each host, SafeGrd keeps that host’s age private key, and any credential the customer asks us to hold, sealed: encrypted before it is written to our database. We release them only to the organization’s enrolled hosts and to the machines described below. For a host with a customer-managed key the private key never leaves that host.

For a surface with a SafeGrd-managed key, an organization can have SafeGrd run its restore drills, or take its backups from a credential it gives us to hold. Each of those backups and drills runs on a virtual machine of its own at Fly.io, which serves no other organization, backup or drill. A drill’s machine is given the key for that drill alone and decrypts one snapshot to test it. A backup’s machine is given the credential for that backup alone, never the key, and encrypts what it reads before storing it. Each machine is destroyed when its backup or drill ends or reaches its time limit, a drill’s machine with its storage. Every release is recorded in the organization’s key access record. The data these machines read never reaches SafeGrd’s server. Where the organization lets SafeGrd sign in to Supabase, DigitalOcean or Heroku instead, we hold the sign-in, encrypted, and the machine is given only a connection string.

The other Sub-processors process account data and technical metadata.

Current Sub-processors

Sub-processor Role / Activity Location Safeguards
DigitalOcean, LLC Cloud hosting infrastructure and managed data storage. United States EU–US Data Privacy Framework; Standard Contractual Clauses (SCCs)
Backblaze, Inc. Object storage for SafeGrd-hosted backups, as client-side encrypted ciphertext under compliance-mode object lock. Used only for customers who choose hosted storage. United States Standard Contractual Clauses (SCCs)
Fly.io, Inc. Compute for the backups and restore drills an organization runs on SafeGrd: one virtual machine per backup or drill, destroyed when it ends. Used only for surfaces with a SafeGrd-managed key that are set to back up or drill on SafeGrd. United States Standard Contractual Clauses (SCCs)
Mailtrap (Railsware Products Studio LLC) Delivery of account email: verification codes, password resets, invitations and backup alerts. United States Standard Contractual Clauses (SCCs)
Google LLC Website analytics on the public landing, documentation and legal pages, only for visitors who consent. Never loaded in the console or on sign-in and account pages. United States EU–US Data Privacy Framework; Standard Contractual Clauses (SCCs)

Independent controllers

These are not Sub-processors: they decide how they use the data they receive, under their own privacy notices.

Company Role Location
Paddle.com Market Ltd Merchant of Record: sells the subscription, takes payment, and handles invoicing and tax. Paddle collects payment details itself. United Kingdom

Sub-processor changes and notification

SafeGrd maintains an up-to-date record of all Sub-processors on this page. When we plan to engage a new Sub-processor or replace an existing one, we will notify registered administrators by email at least thirty (30) days before granting that Sub-processor access to any Personal Data.

Customers with an active subscription may object to any new Sub-processor on reasonable data protection grounds by emailing support@safegrd.dev within thirty (30) days of receiving notification.