Archives are created separately
The source system creates backup archives. They should be encrypted before upload. Google Drive API does not itself back up PostgreSQL databases.
AffHelper Backup is an operational connector intended to transfer previously prepared AffHelper archives to an owner-selected personal Google Drive account. It uses Google OAuth with the narrowly scoped drive.file permission.
Administrative integration · not a public file-storage service
The source system creates backup archives. They should be encrypted before upload. Google Drive API does not itself back up PostgreSQL databases.
rclone uses OAuth to upload to the Drive account selected by the owner. Access is limited to specific files created by or available to the integration.
When needed, an authorized administrator can retrieve an archive and test recovery. Decryption keys should be held separately from archives.
The integration requests https://www.googleapis.com/auth/drive.file. It does not grant unrestricted access to all personal documents stored in Google Drive.
Within the granted permission, operations may include creation, metadata reads, upload, modification and deletion of specific files. Automatic deletion requires separate configuration.
The connector is not intended to read Gmail, scan all of Google Drive, create advertising profiles or provide Google data to advertisers. Access can be revoked in Google Account settings.
Our policy explains OAuth data, operational metadata, technical providers, token storage, archive security, deletion and revocation procedures, and privacy requests.
Read the privacy policy →These pages cover the AffHelper Backup connector only. They do not replace the separate privacy documentation needed for the main AffHelper business application.
The Google Drive connection has been tested. Daily uploads of encrypted backups and the planned 5 GB total backup budget have not yet been activated.