Data practices

Privacy policy

Personal backups, limited file access and owner-controlled recovery.

Purpose and access

This personal app uses Google Drive solely to store and verify the owner's encrypted backups. Google authorization is limited to the specific-file scope. It does not request Gmail, contacts, calendar or general access to the owner's Drive.

Data used and stored

The app transfers encrypted archive bytes and operational metadata, including file names, sizes, checksums and timestamps. The backup host processes the owner's source data to create encrypted archives. Backup contents remain encrypted during upload and cloud readback; recovery keys are held separately from the cloud copies.

Google access and refresh credentials are held in a restricted administrative credential store. They are not provided to general agent accounts or included in public documents. Connections to Google's API use TLS. Recovery archives containing configuration or credentials are encrypted before offsite storage.

Use and disclosure

Google Drive data accessed by this backup app is used for backup storage, integrity verification and owner-authorized recovery. The app does not sell this data, use it for advertising or use it to train AI models. Google and the owner's infrastructure providers process data as necessary to deliver their respective services under their own terms. The app does not intentionally share backup files publicly or with unrelated parties.

Public information pages

These static pages are hosted by Cloudflare. The hosting provider processes routine connection information, such as network addresses and browser request details, to deliver and protect the website. The pages add no advertising, optional analytics, sign-in, forms or tracking scripts.

Retention and owner control

Backup copies are retained under the owner's recovery and retention decisions. The automated uploader does not delete cloud backup copies. The owner can remove copies through Drive and revoke the app's access in Google Account third-party connections. Revocation stops future authorized API activity; it does not itself delete existing Drive files or recovery copies.

Contact and updates

Operator: Mahmoud Hafez. Contact: eng.mahmoudhafez@gmail.com. This policy is updated if the app's data practices change. Version: 16 October 2026; effective when published with the owner's approval.