Paperless Backup Privacy Policy
Effective date: October 13, 2026.
Purpose and users
Paperless Backup is a personal-use integration operated by the account owner, not a public service accepting other users.
Google Drive access
The integration requests the Google Drive drive.file permission to create and access files associated with its authorization. It uses this access to store and retrieve encrypted backups and repository metadata, and to manage backup retention when configured.
Data and credentials
Backups may contain document files, metadata, pending imports, and configuration needed for recovery. Restic encrypts backup contents before uploading them. OAuth credentials are stored in protected local configuration and secure recovery storage; they are not published on this website. The repository password is kept separately.
Use and sharing
Google user data is used only for backup, recovery, and repository maintenance. It is not sold, used for advertising, or used to train AI models. Google Drive stores the encrypted backup files. Restic and rclone run locally; this integration does not send backup contents to another service. This informational website is hosted by GitHub Pages, which may process ordinary visitor request information under GitHub's own privacy policy. No document contents or OAuth credentials are sent to this website.
Retention and control
The owner controls backup retention and deletion. Access can be revoked in the Google account's third-party connections settings. Revocation does not itself delete existing backups; the owner can delete them in Google Drive. Deleting repository files may make remaining backups unrecoverable.
Contact and changes
The operator can be contacted through this site's GitHub repository. Do not include documents or credentials in public issues. This policy will be updated if the integration's data handling changes.