Privacy policy

This policy describes the intended operation of Backups, an owner-operated internal utility. It does not cover unrelated services.

Effective date: 8 September 2026.

Information and purpose

With owner authorization, the app handles selected Drive folder and file identifiers, names, ownership and permission metadata, sizes, checksums, timestamps and encrypted backup contents. The configured owner's email is used to verify ownership. Data is used only to create, verify, retain and recover authorized backups, enforce privacy and storage checks, and diagnose failures.

The source database may include customer, order and other operational records. The backup runner processes the export temporarily and encrypts it before upload to Drive. These information pages do not display those records.

Google access

The app requests drive.file: files it creates and specific existing items selected for use with it. Selecting a folder does not automatically authorize every existing child file. It does not request Gmail, Contacts or full-Drive access.

OAuth credentials are held in GitHub's protected environment secrets for unattended operation. The private recovery key is retained separately by the owner, not supplied to the app or stored in GitHub.

Providers and protection

Cloudflare supplies the database export. A GitHub Actions runner temporarily processes and encrypts it. Google provides authorization and stores encrypted backups in Drive. These providers process information to deliver their services; processing may occur outside the owner's country.

Transfers use HTTPS. Plaintext necessarily exists during export and processing, before encryption. Encryption does not remove every risk: a compromised authorized account or runner could expose data. Authorized owner access is limited to operating, troubleshooting and recovering backups.

Retention and deletion

When cleanup is approved and enabled, intended retention is the latest backup on each of seven successful backup dates, the first successful backup in each of three represented months, and a separately protected recovery baseline. A backup can meet multiple rules.

Only eligible app-managed backups are automatically deleted after verification. Deletion is permanent, not a move to Trash. The protected baseline and unrelated files are excluded. With cleanup disabled, backups accumulate until the configured storage limit stops uploads.

The owner can delete backups directly in Drive and remove stored credentials. Downloaded copies must be deleted separately. Provider-held logs and recovery copies may remain under provider retention practices.

Revocation and control

Revoke Backups through Google Account connections and disable backup jobs in GitHub. Revocation prevents subsequent authorized Drive access but does not delete existing backups. A running job may need to be stopped separately.

Website visits and logs

These pages contain no analytics scripts, advertising, tracking cookies or sign-in forms. Hosting providers may process IP addresses and request details to deliver and secure the pages. Backup logs are designed to report operational results without backup contents or credentials.

Google data commitments

Backups' use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including Limited Use requirements. Google user data is not sold, used for advertising, or used to train generalized AI or machine-learning models. Broader permissions or new uses require updated disclosure and appropriate authorization.

Contact and changes

For access, correction, deletion or privacy questions, contact sulcobullion@gmail.com. Requests may require verification of authority. Material changes to these practices will be reflected here before the changed use begins.