Privacy Policy — OMEX Backup Rclone
What this application is
OMEX Backup Rclone is a private, owner-operated utility. It is not offered to the public and has no external users or customer accounts. It is being built to let its owner run encrypted backups of OMEX's own infrastructure and application data to a dedicated Google Drive account.
What Google user data this application accesses
This application requests exactly one Google OAuth scope:
https://www.googleapis.com/auth/drive.file.
This scope limits access to:
- files and folders this application itself creates, and
- files a user has explicitly opened or selected with this application.
It does not grant, and this application does not request, access to the wider contents of any Google Drive account, Gmail, Contacts, or any other Google service.
How this data will be used
Once operational, authorization will be used only to let
rclone create, list, update, and delete the specific files
making up the OMEX backup repository in Google Drive — solely for
backup and, when needed, restoration of OMEX's own infrastructure and
application data.
Encryption
Once operational, Restic will encrypt the source backup content and associated backup metadata before upload. Google Drive will store the resulting Restic repository; it will not receive plaintext source backup content.
What we don't do
Google user data accessed through this application is not sold, is not used for advertising, analytics, or profiling, and is not transferred to unrelated third parties. Encrypted repository objects are stored in Google Drive solely to provide backup storage — Google Drive is the selected storage service for those encrypted repository objects.
How authorization data will be protected
OAuth authorization material will be stored only on owner-controlled infrastructure and will not be exposed publicly.
Revoking access
You can review and revoke this application's access at any time from your Google Account's permissions page (https://myaccount.google.com/permissions → Third-party apps & services). Revoking access stops future access; it does not delete files already created — see "Data retention" below.
Data retention and deletion
Backup files created by this application will remain in Google Drive until deleted by the application owner. Scheduled backup execution, automated retention/rotation, and restore testing are not implemented yet — this policy will be updated when they are. Revoking access does not itself delete previously created files.
Contact
Questions about this private integration can be directed to the support contact displayed by Google during the authorization process.