Effective September 4, 2026
Privacy Policy
CDossman Personal Backup is a personal, locally operated backup tool maintained by Christopher Dossman.
Data access and purpose
The app requests Google Drive’s drive.file permission. It creates, reads, updates and, when the owner instructs it, deletes app-accessible backup repository files. This permission is limited to files created by or explicitly made available to the app, not unrestricted access to all Drive contents.
The app reads the authenticated account’s email address and storage quota through the Drive API to verify the backup destination and available space. These results and backup verification records may be stored in local operational logs.
Processing and storage
Selected local file contents are encrypted by restic before upload through rclone. The encrypted repository is stored in the owner’s Google Drive. Restores download repository data and decrypt it locally using the restic password.
Encryption does not hide all metadata. Google may receive repository object names, sizes, timestamps and account/API activity. Repository key records can also contain informational metadata. Local source files, restored files and operational logs are not made private by repository encryption alone.
OAuth credentials and the restic password are stored locally with restricted file permissions. They are not submitted to this information website. The owner is responsible for device security and an independently protected recovery copy of the password.
Sharing and limited use
Google Drive receives the encrypted repository and the API requests needed to store, check and restore backups. The app does not sell Google user data or use it for advertising, profiling, data brokerage, or training AI or machine-learning models. It does not provide third parties access to backup contents as a service.
CDossman Personal Backup’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Retention, deletion and revocation
Backup versions remain until the owner removes them or runs an explicitly configured retention process. Local files and logs remain until removed locally. No automatic deletion promise is made.
The owner can revoke authorization in Google Account connections. Revoking access does not delete existing Drive backups, local credentials, source files or restored files. Deleting a backup does not revoke authorization. Drive trash and Google’s storage-retention behavior may delay permanent removal.
This information website
This site does not offer a backup upload form or collect Google OAuth credentials. No advertising or analytics scripts have been added by the app operator. Hosting and delivery providers may process technical request data such as IP addresses, requested URLs and browser information to serve and secure the site. If you email the operator, your message and contact details are used to respond.
Questions and changes
Contact chris@orbitalclaw.com about these practices. Material changes will be reflected on this page; new uses of Google data or additional permissions require updated disclosure and any applicable consent.