Privacy policy

Personal AI Assistant Backup
Last updated: 31 October 2026

Purpose and operator

Personal AI Assistant Backup is an owner-operated, single-user backup utility. It uses rclone and Google Drive to store encrypted recovery archives, verify uploaded files, and support recovery of the owner's assistant deployment.

Google data accessed

The utility uses Google OAuth authorization. Its current configuration requests the full Google Drive scope, which permits access beyond a single backup folder. The runner is configured to operate within one backup folder; this does not technically narrow the OAuth grant to that folder.

The backup workflow reads folder and file metadata, uploads encrypted archives, and downloads backup files for integrity checks and recovery. Google account information is used to confirm that the authorized account matches the intended backup destination.

Data use and storage

Data is used for backup delivery, verification, and recovery. Archives can contain assistant state, task data, deployment configuration, and credentials. They are encrypted with age before being sent to Google Drive. Google Drive stores the encrypted archives and associated file metadata, such as names and sizes.

OAuth access and refresh tokens are stored in a private configuration on the owner's VPS so scheduled backups can run without an interactive sign-in. Copies of that configuration included in archives uploaded to Google Drive are encrypted. Private local capture files may also be retained on the owner's VPS. Recovery credentials, including the private archive decryption key, are held separately on the owner's recovery device.

The workflow sends authentication and storage requests to Google and runs on the owner's VPS. Access is also subject to the owner's server, device, and Google account controls.

Retention and deletion

Automated deletion or retention rotation of backup archives is not currently enabled. The owner can remove stored archives from Google Drive and remove local or server copies separately. This policy does not promise a fixed deletion or retention period.

Revoking authorization

The owner can revoke the application's access in Google Account settings. Revocation prevents future authorized requests using that grant. It does not remove archives already stored in Google Drive or copies on the owner's devices and server; those must be deleted separately by the owner.

Contact and updates

For privacy questions or requests, contact the application owner using the support email provided on the OAuth consent screen. This policy should be updated when the backup workflow or its data practices change.