R3X Backup System Privacy Policy
This policy describes the personal-use R3X Backup System desktop workflow and its access to Google user data. The backup application is operated by the owner for preservation and recovery of selected R3X development files.
Google data accessed
With the account owner's consent, rclone uses the Google Drive API and its full Drive OAuth scope to locate, read, create, modify, upload, download, verify, and, when specifically configured, remove files in Google Drive. This scope technically enables access to the account's broader Drive, not just one folder. The intended backup workflow targets the owner's designated R3X backup location.
Purpose and use
Google Drive access is used solely for owner-directed backup, integrity verification, recovery, and related backup maintenance. It is not used to advertise, profile users, train AI models, or sell Google user data. The backup workflow does not require access to student accounts.
Where data is stored
Selected backup files may be stored on the owner's Windows computer and in the owner's Google Drive account. The application uses the owner's private OAuth connection; the public informational pages do not receive or store Drive files, client secrets, or access tokens. Google's own service terms and account controls also govern files stored in Google Drive.
Sharing and disclosure
The intended workflow does not transfer backed-up Google Drive files to third-party buyers, marketers, or AI services. Google processes data as the Drive storage and API provider. The owner controls the Google account, file permissions, and any future authorized sharing or transfer.
Student information and credentials
Identifiable student information and private credentials must not be included in backups. Backup selection and review are intended to exclude these categories. This rule is a data-handling requirement, not a guarantee that arbitrary files cannot be selected by a misconfigured computer.
Retention and deletion
Backups and historical versions remain until removed under the owner's backup retention and recovery procedures. The owner can inspect or delete backup files from Google Drive, revoke the application's Google access using Google Account security controls, and delete local configuration or backup copies. Revocation prevents future API access but does not automatically erase existing backup files.
Security
The desktop client uses Google's OAuth authorization and rclone to communicate with Google Drive. Access tokens and secrets must remain private; they are not published on this informational site. No backup system guarantees perfect security, and the owner is responsible for reviewing permissions and recovery procedures.
Informational site
These pages contain no sign-in, tracking scripts, form submissions, or file-upload interface. The web host may process ordinary request logs under its own infrastructure and privacy practices.
Questions
This is a personal-use application operated by the Google account owner. The Google OAuth consent screen lists the owner's support contact.