Legal / Privacy Notice

Privacy Notice

Last updated 31 October 2026.

Who we are

SafeGrd is provided by Kush Kumar Sharma, a sole proprietor trading as SafeGrd, of Bengaluru, India - 560048. We are the controller of the personal data we collect about users of our website and service. For personal data inside what you back up, you are the controller and we act as your processor under our Data Processing Agreement. For anything about your data, write to support@safegrd.dev.

Your backups and your key

Your database, file and mailbox backups are compressed and encrypted on your own machine before they leave it. They are written either to storage in your own cloud account or to compliance-locked object storage provided by SafeGrd, and kept there only as encrypted bytes. By default we never receive your database passwords, mailbox credentials or storage keys. With a customer-managed key, we never receive your private encryption key, so we cannot read your backups.

You can choose to have SafeGrd hold some of these instead: a database or mailbox credential for a surface, your storage bucket's secret key, or (with a SafeGrd-managed key) your private encryption key. Each is a separate choice, and the console shows which ones you made. Whatever we hold is stored encrypted and released only to your enrolled hosts when they run a backup or restore drill, or to a machine SafeGrd starts for one of your backups or drills, as described below. Your key access log records every release. What we hold is never displayed in the console or readable through the API.

With a SafeGrd-managed key you can also choose to run a surface’s restore drills on SafeGrd instead of on your own hosts. This is the only case in which we decrypt a backup. Each drill has a machine of its own, which runs nothing for anyone else and is destroyed with everything restored on it when the drill ends. Your key access log shows each release of your key to a drill. The restored data never reaches SafeGrd’s server, which keeps only the drill’s result.

With a SafeGrd-managed key you can also have SafeGrd take a surface’s backups from a database connection string, or a bucket’s S3 access key (such as a Supabase project’s Storage), that you give us to hold. Each backup has a machine of its own, which is given that credential for that backup alone and never your key. From a bucket it reads the objects under the prefix you chose. It encrypts the backup to your key, writes it to SafeGrd-hosted storage or your own bucket, and is destroyed when the backup ends. Your key access log shows each release of the credential. What the machine reads never reaches SafeGrd’s server, which keeps only the backup’s record. When you add a bucket, our server lists it once with the key, reading the names of at most one object, to tell you whether the key works.

For a Supabase project, a DigitalOcean cluster or a Heroku Postgres database, you can let SafeGrd sign in to the platform instead of typing a password or connection string. We then hold that sign-in’s tokens, encrypted, and use them only to get what each backup needs: from Supabase, a read-only database role whose password expires within minutes, and from DigitalOcean or Heroku, the database’s connection details. On a DigitalOcean cluster that lists trusted sources, we also use them, when you add the database, to add the addresses SafeGrd’s machines connect from. On Heroku the sign-in can read the config vars of every app on the account, and we read only the URL of the database you chose. The backup’s machine is given a connection string, never the sign-in. Your key access log shows each role made, each read and each release. To end it, revoke SafeGrd in Supabase, DigitalOcean or Heroku, or replace the credential in the console.

What we collect, and why

We do not sell personal data, and we do not use it for advertising.

Who we share it with

A complete, up-to-date register of our third-party processors is published on our Sub-processors page.

International transfers

Our servers are in the United States. If you use SafeGrd from elsewhere, your account data is transferred there. Where the law you are under requires it, we rely on appropriate safeguards for those transfers, such as the standard contractual clauses approved for this purpose.

How long we keep it

Your rights

Depending on where you live, you can ask us to: give you a copy of your personal data; correct it; delete it; restrict or object to how we use it; and receive it in a portable form. Where we rely on your consent, you can withdraw it at any time. Write to support@safegrd.dev; we answer within one month (extendable where the law allows, and we will tell you if so). You can also complain to the data protection authority where you live (in the UK, the Information Commissioner’s Office; in the EU, your local supervisory authority; and in India, the Data Protection Board).

Security, and if something goes wrong

We protect what we hold with encryption in transit (TLS) and at rest where supported, hashed passwords, access controls, rate limiting, and by keeping as little as we can. Your backups reach us readable only on the machine of a drill you chose to run on SafeGrd, and with a customer-managed key neither they nor their key reach us at all. If a breach affecting your personal data happens, we will tell you without undue delay, say what was affected and what we are doing, and notify the authorities where the law requires it.

If the business changes hands

If SafeGrd is sold, merged or transferred, the personal data we hold may pass to the new owner, who will be bound by this notice for it. We will tell you before that happens.

Other sites

Our site links to others (Paddle, GitHub, your storage provider’s documentation). Their own privacy notices apply there, not this one.

Cookies and local storage

We do not use cookies for advertising. What we set, and why:

You can change your answer at any time with the “Cookie settings” link at the foot of our public pages, or here: . Withdrawing removes the analytics cookies. The page or link you arrived from is carried in the addresses of the links between our pages, not in a cookie or in your browser’s storage, and is kept, with your organization, only if you sign up. When you pay through Paddle, Paddle’s checkout runs on our payment page and may set cookies of its own, which Paddle’s privacy notice describes.

Changes

If we change this notice we will post the new version here with its date, and tell you by email or in the console before a material change takes effect.