Your backup connection,
explained.

1. Operator and purpose

The utility is operated by the RAKER factory application operator for backup and recovery. It uses Rclone on the operator's computer to transfer encrypted backup copies to Google Drive and retrieve them when required.

2. Google data and permissions

The connection requests the Google Drive permission https://www.googleapis.com/auth/drive.file. This permits creating new files and accessing files associated with this connection, rather than general access to all existing Drive files.

Information handled includes the encrypted backup files and their names, sizes, file identifiers, folder information and transfer metadata. Google authorisation credentials, including access and refresh tokens, are used to perform authorised transfers.

3. How information is used

Files and metadata are used to upload, organise, check, list and retrieve backup copies, diagnose transfer failures and perform recovery tests. Google data is not sold, used for advertising or used to train AI models.

RAKER Encrypted Backup's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

4. Storage and protection

Factory application backups are encrypted on the factory computer before they are uploaded. Backup decryption passphrases are kept separately from the uploaded backup copies. Google authorisation credentials are stored on the computer running the backup connection and protected using operating-system file permissions.

Copies remain subject to the security of the operator's computer, Google account and passphrase storage. Encryption does not protect against every form of device or account compromise.

5. Sharing and service providers

Encrypted backups and the metadata needed to store them are transferred to Google Drive. Google processes information under its own privacy policy. Access follows the authorised Google account's sharing settings.

Factory records, backup files, decryption passphrases and Google authorisation tokens are not published on this information website. The website hosting provider may process ordinary web request information, such as IP addresses, for delivery and security. These pages contain no analytics scripts, advertising or forms.

6. Retention and deletion

Backup copies are kept until the operator deletes them or applies a configured retention policy. Local copies and Google Drive copies are separate; deleting one does not necessarily delete the other. Deleted Drive files may remain in Google Drive's trash until permanently removed.

Authorisation credentials remain on the backup computer until removed or invalidated. The operator should remove unused credentials when retiring the connection or computer.

7. Your controls

The Google account holder can revoke the connection through Google Account connections, stop scheduled transfers, and delete backup copies from Google Drive. Revoking access stops future authorised transfers but does not automatically delete existing copies.

The backup decryption passphrase is required for restoration. Keep a separate recovery copy of that passphrase; losing it may make encrypted backups unrecoverable.

8. Contact and policy changes

For questions or deletion assistance, contact the RAKER factory application operator using the support email displayed on the RAKER Encrypted Backup Google authorisation screen.

Changes to the connection's data practices will be reflected on this page with an updated effective date.