FUN1MILL BACKUP · OWNER-OPERATED UTILITY

FUN1MILL Backup privacy notice

This notice describes the owner-operated FUN1MILL Backup utility and its Google Drive access. It does not replace the crowdfunding platform's separate privacy terms or claim that its pending legal review is complete.

Data accessed and purpose

The utility uses the owner's Google OAuth authorization solely to create, locate, upload and read back the encrypted backup files it is allowed to access under drive.file. It processes the necessary Drive file and folder identifiers, names and file bytes to store backups and verify their integrity. It does not request permission to read unrelated Drive files, Gmail, Contacts or Calendar.

Storage and security

Snapshot content, including database authentication and audit records and deployed application source, is encrypted by the backup process before upload. Only encrypted backup files and encrypted operational control records are copied to the selected Google Drive destination. Original decryption-key and OAuth-configuration copies stay in separate restricted local directories. If the owner enables reviewed hosted scheduling, copies of the existing key and dedicated Drive configuration are stored in the owner's private GitHub encrypted Actions secret store. The hosted backup process handles plaintext only in restricted ephemeral memory and temporary files outside its repository, then removes its private temporary files. The key is never uploaded to Google Drive. OAuth credentials are not included in the Drive backup. Local tools maintain integrity and operational receipts without printing credentials.

Sharing and use limits

Google Drive stores the encrypted files. The owner uses Google authorization through the existing rclone tools. When reviewed hosted scheduling is enabled, the owner's isolated private GitHub Actions runtime receives the dedicated Drive credentials through its encrypted secret store solely for backup operations. A separate Cloudflare watchdog handles authenticated operational statuses and failure notifications, without receiving the Drive credentials, decryption key or database contents. Backup data is not used for advertising, sold, or used to train AI models. The utility does not automatically share Drive backup files with other people. Access and any sharing changes in the owner's Drive remain subject to the owner's Google account settings. FUN1MILL Backup's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Retention, deletion and revocation

Backups are retained until the owner deliberately removes them; no automatic retention-based deletion is currently configured. Deleting a Drive copy does not delete a local copy or the source database. The owner can remove the utility's access in Google Account third-party connections and separately remove local and hosted OAuth configuration and selected Drive files. Revocation stops future authorized access but does not erase existing backups. Questions about retained data or access can be sent to support@fun1mill.com.

This informational website

These pages have no login, forms, application cookies, analytics scripts or backup data access. Cloudflare delivers the pages and may process ordinary request metadata for service operation and security. Visiting these pages does not authorize access to Google Drive.