Privacy Policy — Playforge Stage Backups
Last updated: 2026-11-21
Service status: This policy describes the planned design. Google Drive authorization and live backup operation have not been verified; it does not assert that backups are currently running.
Operator and contact
Operator: Daniel Kvasnicka.
Privacy and service questions: info@zerun.cz.
Google data the planned tool accesses
The planned tool uses Google Drive OAuth for the dedicated Stage backup Google identity. The intended OAuth scope is https://www.googleapis.com/auth/drive.file. It is intended to access files and folders created or opened for this application, not to read the account's unrelated Drive files. The backup destination folder must be created through the authorized rclone remote for this limited-scope design to work.
The tool is intended to upload encrypted PostgreSQL backup archives and their SHA-256 verification markers. It may list, download, verify, and move its own older backup objects to Drive Trash for retention and recovery operations. It does not need Gmail, contacts, calendar, or other Google API data.
Purpose and encryption
Drive access is intended solely to store, check, retain, and restore Playforge Stage database backups. The design uses rclone crypt to encrypt backup content and names before they are uploaded. Cryptographic keys and OAuth credentials are intended to be stored separately from the Drive backup objects and protected on the backup host. Google Drive may still expose object sizes, modification times, and other service-level metadata; this design does not claim to conceal all metadata.
Retention and deletion
The planned active-retention window covers verified backups from the current UTC day and the previous 13 UTC days. A separate retention operation is designed to move verified older copies to Google Drive Trash, not permanently erase them. Items in Trash may continue to consume storage and may remain recoverable under Google's retention behavior. This policy is not yet evidence that any live schedule or deletion job is enabled.
Sharing, access, and security
The planned destination is private and Stage-only; it is not intended to be shared with Production backup identities or unrelated users. Access is intended to be limited to the designated operators and Google infrastructure needed to provide Drive. Backup contents are encrypted before upload, but OAuth access and encryption-key custody still require protection. No sale, advertising use, or unrelated analytics use of Google user data is intended.
Revoking Google access
The Google account owner can review or revoke the application's access in their Google Account security settings. Revoking access prevents future Drive operations until authorization is restored. It does not itself delete backup files already stored in Drive or items in Trash; those must be handled separately by an authorized account operator.
Changes
This policy must be updated if the actual OAuth scope, backup data, access controls, retention, or sharing behavior differs from this planned design.