Newcastle rclone Backup privacy policy
Private backups for the owner of newbstercode.com.
Last updated: October 4, 2026.
Google user data accessed
Newcastle rclone Backup is a private utility used solely by the owner of newbstercode.com. It uses rclone and the Google Drive API with only the https://www.googleapis.com/auth/drive.file OAuth scope.
The utility accesses only the backup files and folders it creates in the owner's Google Drive. It reads their content and metadata, including file names, identifiers, sizes, timestamps and folder relationships, to create, verify, maintain and restore backups. It does not read other files in the owner's Drive. The scope technically also permits access to files explicitly made available to the app, but this utility uses it only for its own backup files.
How data is used
File content and metadata are used only to transfer, verify, maintain and restore the owner's backups. OAuth access and refresh tokens are used to authorize these operations with Google Drive.
Google user data is not sold, shared with third parties for their use, used for advertising or used for profiling. Google processes the data as the provider of Google Drive, the backup destination. The utility is not a service for other users.
Credential and backup storage
The utility runs on the owner's own machines. OAuth client credentials, access tokens and refresh tokens are stored in local configuration files. On Windows, access is restricted to the owner's account, SYSTEM and Administrators. On Linux, credential files are restricted to root; the controller's configuration uses owner-only file and directory permissions.
Copies of the credential configuration are encrypted with AES-256 and stored in the owner's Google Drive and on the owner's machines. The encryption passphrase is stored separately in the owner's password manager. Credentials and configuration contents are not published on this website or committed to source control.
Backup data is stored in dedicated folders in the owner's Google Drive and on the owner's machines. It includes PostgreSQL database dumps and checksums, encrypted controller-configuration snapshots, and encrypted credential-configuration backups. Controller snapshots use restic encryption. Google provides the Drive storage service; no other outside backup service operates the utility or receives backup data for its own use.
Retention and deletion
- Nightly PostgreSQL dumps and checksums in Google Drive are retained until the owner manually deletes them. Local dump copies on the backup machine are deleted after 30 days.
- Encrypted controller snapshots retain 7 daily, 4 weekly and 3 monthly snapshots. Older snapshots are removed and unneeded data is pruned after each backup run.
- Encrypted credential-configuration backups and legacy Drive backup folders are retained until the owner manually deletes them, for example after credential rotation.
- The owner's separate local database archive retains 4 weekly base backups and the write-ahead logs needed to restore from the oldest retained backup. Local encrypted credential backups are retained until manually deleted.
Files deleted through Google Drive may remain in Drive trash until permanently deleted under Google's trash handling or by the owner. Removing a file from a backup set does not necessarily immediately erase every retained copy.
The owner can revoke the app's Google Account access at any time through Google Account permissions. Revoking access prevents future authorized operations; it does not itself delete existing backups.
Contact
For privacy questions or deletion requests, contact the owner at support@newbstercode.com.