Privacy policy

1. Scope and operator

The utility is used by its owner to back up selected projects and related recovery material to Google Drive. It is not a public upload or backup service, does not offer public accounts, and is not an official OpenAI or Google product.

This public website provides information only. It does not provide a login, collect backup files, or receive the utility’s OAuth tokens or recovery keys.

2. Information the backup workflow handles

The owner chooses the material to back up. It can include project source code, database exports, uploaded assets, archives, and recovery documentation. Selected payloads can contain personal information or credentials; the utility does not represent those payloads as secret-free.

Archive payloads are encrypted locally before upload. Reviewed, non-sensitive summaries, object manifests, checksum records, or restoration instructions may be uploaded as readable documents. These documents are reviewed separately from the encrypted payloads.

The utility uses the owner’s Google account identity to verify that it is accessing the intended account. OAuth credentials and tokens are held in private local configuration on the owner’s Mac. Private recovery-key material is not uploaded in plaintext; an encrypted recovery-key file and a public encryption recipient may be stored with backup recovery documentation.

3. Google access and permitted use

The utility uses Google OAuth with rclone to access Google Drive. The Drive scope can permit viewing, creating, editing, and deleting files across the authorized account. That permission is broader than the workflow’s single designated backup folder; the folder configuration is not a Google-enforced folder-only restriction.

The configured workflow uses access to upload backup objects and reviewed recovery documents, list or inspect those objects, and download objects for checksum and restoration checks. It is not a Drive-wide crawler and does not use that access to modify unrelated Drive content.

Google account information and Drive data are used only to operate and verify the owner’s backups. The utility does not sell that information, use it for advertising, or use backup content to train general-purpose AI models.

4. Storage, access, and service providers

Backup preparation takes place on the owner’s Mac. Backup objects are stored in the configured Google Drive destination. Access to that destination is managed by the owner. Encryption reduces exposure of payload contents, but it does not guarantee the security or recoverability of every backup.

Google processes account authorization and Drive storage under its own terms and privacy practices. This informational website is hosted on Cloudflare Pages. Cloudflare may process ordinary web requests and technical logs, such as network addresses and request metadata. This website does not add analytics, advertising, cookies, external fonts, or tracking scripts.

For provider practices and API requirements, see the Google Privacy Policy (opens in a new tab), Google API Services User Data Policy (opens in a new tab), and Cloudflare Privacy Policy (opens in a new tab).

5. Retention and deletion

The owner manages retention. Dated backup sets are not automatically deleted by this workflow, and no unlimited-retention commitment is made. Local staging files, cloud backup objects, and recovery documents may have different retention periods.

The owner can remove backup files from Google Drive or local storage when appropriate. Deleting a working project does not by itself remove copies held in an earlier backup.

6. Revoking access

The owner can revoke the utility’s Google authorization through the Google Account connections page (opens in a new tab). Revocation prevents future access through that authorization, but it does not delete previously uploaded backup files. Those files must be managed separately in Google Drive.

7. Contact and changes

This is a single-owner tool with no public accounts or public customer intake. Authorized collaborators with a question about material included in a backup should contact the owner through their existing private communication channel.

The owner may update this policy if the utility’s data handling changes. The date at the top identifies the latest version. This policy is descriptive; it is not a promise of regulatory certification, Google verification, or guaranteed backup security.