Privacy policy

1. Who operates DockerBackup

DockerBackup is a personal Docker backup and recovery utility operated by Chris Clark. It is used for owner-authorized backup of selected application configuration and data to Google Drive, and for recovery onto a replacement host. This website provides public information about that utility. Questions and requests can be sent to [email protected].

2. Google Drive permissions and data accessed

The owner authorizes the private tools through Google's OAuth consent flow. The current integration uses the scope https://www.googleapis.com/auth/drive, which permits broad access to Google Drive files, including viewing, downloading, creating, editing, and deleting files. The application is configured to operate within a designated DockerBackup folder; this folder setting is not an OAuth restriction on the permission granted.

For backup and recovery, DockerBackup accesses encrypted backup files and associated Drive metadata such as file and folder identifiers, filenames, sizes, timestamps, and checksums. The tools list backup packages, create or upload recovery files, verify stored checksums, download selected packages, and move eligible expired packages to Google Drive Trash. The current backup workflow does not scan unrelated documents for analysis or use their contents for another purpose.

OAuth credentials and tokens are also processed to authenticate these requests. They are stored privately on authorized backup or restore hosts, outside the public website's files.

3. How data is used

Drive data is used to provide the backup, integrity-verification, retention, and restore functions described on the DockerBackup homepage. Local application data may include configuration, databases, source/deployment inputs, and credentials needed to rebuild the owner's environment. This selected local data is encrypted before it is uploaded to Drive.

Downloaded packages are decrypted only on an authorized recovery host using a separately held recovery key. The restore process may create private plaintext staging copies and restored files containing the original application information.

DockerBackup does not use Google user data for advertising, profiling, sale, or training generalized artificial-intelligence or machine-learning models.

4. Storage and protection

Encrypted offsite packages are stored in the owner's Google Drive. Local snapshots, encryption keys, OAuth tokens, restoration staging, and recovered files reside on owner-controlled or owner-authorized hosts. Access to those hosts and files is restricted through host and file permissions. Encryption keys are stored separately from the offsite packages and are not uploaded as part of those Drive packages.

The public website serves static informational pages. It has no access to the backup directory, recovery key, OAuth configuration, or private restore controls. It provides no backup upload form or Google sign-in flow.

5. Sharing and human access

Backup packages and metadata are transmitted to Google to store and manage the offsite copies, and to an authorized host when the owner requests recovery. Google processes data under its applicable terms and privacy practices. The public website may be delivered through Cloudflare; that public delivery path does not provide access to private backups or recovery controls.

Data is not sold, rented, or shared with advertising services or data brokers. Human access to private backup information is limited to the owner and explicitly authorized operators for requested administration, troubleshooting, security, or recovery, or where required by law.

DockerBackup's handling of data received through Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.

6. Retention and deletion

The configured rolling policy keeps the newest backup on each of the latest seven backup dates, plus one backup from each of four older weeks. Cleanup runs after a successful upload and fresh checksum verification. Historical or supplemental recovery copies and necessary dependencies can be retained outside that rolling policy. Failed uploads can delay cleanup.

Expired Drive packages are moved to Trash and remain subject to Google's Trash and deletion behavior. Local snapshots and encrypted packages have their own cleanup. Decrypted restore staging and recovered data remain on the authorized restore host until the operator deliberately removes them; they are not automatically deleted by Drive retention.

The owner can delete backup files and local copies, remove stored OAuth credentials, and revoke Google's authorization. Revoking access stops future Drive access but does not itself remove previously stored backups or restored files. For assistance with data or deletion requests, contact [email protected].

7. Your choices and Google authorization

Authorization can be declined or revoked at any time through your Google account's third-party connections settings. Once access is revoked, the tools cannot continue Drive uploads, downloads, or retention until access is granted again. Existing local or already restored data can still be managed on the owner's hosts.

8. Website visitors

This static website does not use advertising, analytics scripts, tracking cookies, or account-registration forms. Hosting and network providers, including Cloudflare when configured, may process request information such as IP addresses, requested URLs, timestamps, and browser headers to deliver and protect the website. The site operator may process operational error information for maintenance and security. Emailing the contact address shares the contents of that email with the operator and their email provider.

9. Changes and contact

Changes to these practices will be reflected on this page with an updated date. If Google data would be used for a new purpose, the owner will be informed and any necessary consent obtained before that use begins.

Operator: Chris Clark
Application: DockerBackup
Contact: [email protected]