Google Drive Backup Privacy Notice

Purpose. Yuma Informed uses this Google Drive authorization only to store encrypted operational backups of its production database and uploaded files for recovery after a server failure.

Google Drive access. The app uses the drive.file permission to create and manage its own dedicated Yuma Informed Encrypted Backups folder. It does not need access to unrelated Drive files.

Backup information and encryption. Backups contain production database records and uploaded files, which may include news tips, corrections, contact information, or attachments. Restic encrypts backup content before Rclone uploads it. The VPS backup operator can access source data while creating a backup. Google Drive can observe account activity, object sizes, and timing, while the encrypted repository protects backup contents and names.

Credentials and recovery. OAuth credentials and the Restic encryption password are restricted on the VPS. Separate recovery copies are kept in a protected local Windows folder outside the VPS. Anyone restoring data needs both the Drive authorization and the Restic password. If the Restic password is lost, the encrypted backups cannot be decrypted.

Retention. The server is configured to create daily incremental snapshots and retain snapshots for 30 days. Older snapshots are removed from the dedicated encrypted repository.

Use and sharing. This authorization is not used for advertising, analytics, or unrelated file access. Backup data is not intentionally shared with other Drive users. Google processes and stores the encrypted repository under the account’s terms and service settings.