Privacy policy

What the app accesses

The app processes selected Personal AI files and their metadata to create and restore backups. Google OAuth authorization provides access tokens and, when granted for continued access, refresh tokens. These credentials let the app access Drive without receiving your Google password.

The requested Drive scope is https://www.googleapis.com/auth/drive.file. It permits creating files and accessing or managing files created by the app or explicitly opened with or shared with it. Within that authorized set, the app can read, update, and delete files for backup maintenance and restoration. It does not grant unrestricted access to your entire Drive. See Google’s scope documentation.

How data is used

Google Drive data and authorization credentials are used only to operate the owner’s backup and restore workflow, including maintaining backup files and diagnosing failures. Google API data is not sold, used for advertising, or used to train generalized AI or machine learning models.

The informational website does not run the backup app, collect Google credentials, or provide an OAuth sign-in form.

Encryption and its limits

Restic encrypts and authenticates backup content and snapshot metadata before upload to Drive. The environment running a backup or restore can access plaintext and the keys it uses. Original source files and restored files are outside the protection of repository encryption.

Google Drive can still observe storage metadata such as encrypted object sizes, object names, and upload times. Some restic repository key-file metadata is also unencrypted. Encryption does not prevent deletion, loss of credentials, or service interruption. See restic’s design documentation.

Storage, access, and service providers

Encrypted backup repository files are stored in the owner’s Google Drive. OAuth credentials and repository keys are kept in the owner-controlled backup environment and must be protected separately from the public website. The app owner controls the backup workflow and access to its credentials.

Google processes Drive storage and authorization data under its own policies. Cloudflare hosts this website and may process connection information, including IP addresses and request details, to deliver and protect it. This site adds no analytics scripts, advertising trackers, or cookies of its own. Provider processing may still occur under Google’s privacy policy and Cloudflare’s privacy policy.

Retention, revocation, and deletion

Backups remain until the owner removes them under the configured retention policy or deletes the repository. Deleting a source file does not automatically remove older backup snapshots containing it. The owner must remove affected snapshots and prune unreferenced repository data, or delete the entire repository. Drive trash and provider retention may delay final removal.

You can revoke the app’s Google access in your Google Account connections. Revocation stops future authorized access; it does not erase existing backups. To disconnect fully, also remove stored OAuth credentials from the backup environment. Keep repository keys while backups are still needed; losing all usable keys can make restoration impossible.

For deletion help, contact the app owner below. A deletion request should identify the account or backup concerned without including passwords, tokens, keys, or backup contents.

Policy changes

The owner will update this page when the described practices change. The date above identifies the latest revision.