Privacy disclosure

Privacy policy

Effective October 25, 2026

This policy describes how the owner-operated 3XMR Homelab Drive Backups application handles Google user data. It is a private backup and disaster-recovery tool, not a public cloud storage or account-registration service. Its static informational website does not itself connect to Google Drive or receive backup files.

Who operates this application

The 3XMR infrastructure operator administers the application and the authorized Google Drive accounts. Questions or requests may be sent to wrightpt@gmail.com.

Data requested and accessed

When the Google account owner explicitly consents, the local rclone-based utility may use the granted OAuth permissions to access designated Google Drive files and folders for backup and recovery. The data involved may include Google account identity needed to complete authorization, file names, file IDs, file sizes, checksums, and the bytes of operator-selected backup archives. The exact Drive access available depends on the scopes the operator grants and Google's permissions.

No Google password is requested or stored by this website. The website has no sign-in form, advertising pixels, or application analytics scripts.

How the data is used

Google user data is used only to upload, list, verify, retrieve, or restore operator-authorized backup objects and to maintain the related connection. It is not sold, used for targeted advertising, shared for advertising, or used to train generalized AI models. No transfer to a third party occurs other than the Google services required to store or access those objects, or a disclosure required by law.

Where data and credentials are kept

Backup objects are stored in the operator's selected Google Drive account(s), subject to Google's storage policies. OAuth client credentials and tokens are maintained on restricted operator-controlled systems and are not published in this website's source. Backups using the new integration must pass client-side encryption and independent restore checks before unattended production use; this policy does not claim historical backup copies were encrypted.

Normal HTTPS connections protect transfers in transit. Google and the static site's hosting providers may process technical request logs under their own terms. This website does not intentionally set advertising or tracking cookies.

Retention and deletion

The operator decides which backup objects to retain for recovery and how long to retain them. The public website does not delete backups. An OAuth revocation stops future access under that grant but does not automatically delete previously stored Drive files; those remain governed by the owning Google account and its retention controls.

Access, revocation, and questions

The Google account owner can review and revoke permissions in Google Account connections, and can remove files from their own Drive according to Google's controls. For access, retention, or deletion questions, email wrightpt@gmail.com.

Google API Services User Data Policy

Use of information obtained from Google APIs is limited to the backup and recovery features described here and follows the applicable Google API Services User Data Policy, including its Limited Use requirements. Application data is not transferred for advertising or other unrelated use.

Changes to this policy

Material changes to data access or handling will be reflected on this page with an updated effective date before the modified use is enabled.