1. Who operates this application?
HomeLab Backups is a private, owner-operated backup utility, not a public or commercial storage service. Questions about the application or this policy may be sent to raffle-amusing-yam@duck.com.
2. What Google information is accessed?
With the owner's authorization, the application uses the Google Drive API with the https://www.googleapis.com/auth/drive.file scope. This permits access to Google Drive files created by the application or explicitly made available to it. The application is not intended to read unrelated private Google Drive files, Gmail, contacts or other Google account data.
3. Why is Google data used?
Authorized Drive access is used only for backup operations: creating and uploading encrypted archives, listing and checking backup files, downloading archives for verification or recovery, and deleting older backups only when a separately configured retention procedure authorizes deletion. No unrelated profiling, advertising or marketing use is intended.
4. Where is information stored?
Backup content is encrypted by the local backup tooling before it is sent to Google Drive. Google Drive hosts the encrypted backup files and related cloud file metadata, such as file size and timestamps. OAuth credentials and encryption keys are held in the owner's private operating environment, not on this public website. The website itself does not accept files, credentials or user registration.
5. Sharing and processors
The application does not sell Google user data or share it with advertisers. Google Drive is used as the backup storage provider. This informational website is delivered through Cloudflare, which may process technical connection data such as IP addresses and security events to serve and protect the site. Cloudflare does not receive the backup contents or OAuth credentials through this website.
6. Retention and deletion
The owner controls backup retention and may remove encrypted archives from Google Drive. Retention automation is not represented as active until separately deployed and tested. Authorizations can be revoked from Google Account permissions. Backup files may also be deleted directly by the owner. Revoking access stops future API access but does not automatically remove files already stored in Google Drive.
7. Security and limitations
The planned backup workflow uses encrypted file storage and restricts OAuth access to the files needed for backup operations. No system can guarantee absolute security; successful backup, upload, restoration and retention must be verified separately in operation.
8. Website data
This website has no application login, forms, advertising, analytics scripts or intentionally set tracking cookies. The hosting provider may process limited technical access and security information as described above.
9. Changes
This notice may be updated when the backup workflow or its data handling changes. The effective date will be revised when changes are published.