Privacy policy
Applies to the “Docomet backups” Google OAuth application, used only by its operator.
Who uses it
Docomet backups is used by one person, the operator of the Docomet server, with their own Google account. It is not offered to the public.
Google user data it accesses
The application requests only the drive.file scope. It accesses only the files and folders it creates in the operator's Google Drive: one backup folder and the encrypted backup files and metadata files inside it. It also reads the Drive storage quota to check there is room before uploading. It does not access any other Drive file, and requests no other Google data.
How the data is used
The files are used only to store, verify and, when needed, restore backups of the operator's Docomet server. Uploads are verified by downloading them again and comparing checksums. Restore tests download a backup to the same server.
Storage and security
- Backups are encrypted on the server before upload; the passphrase is kept outside the server and is never sent to Google.
- The authorization token is stored on the operator's server in a file only the server's backup account can read. It is never published, logged or shared.
- The backup folder is private to the operator's Google account and is not shared.
Sharing
No data is sold, shared with or transferred to anyone. No data is used for advertising, analytics or training of any model. Google stores the files as part of the operator's own Drive under Google's terms.
Docomet backups' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
The newest two verified routine backups and one protected rollback backup are kept. Older routine backups are moved to Google Drive's Trash, where Google deletes them after 30 days. The operator can delete the backup folder at any time in Google Drive.
Revoking access
Remove “Docomet backups” at myaccount.google.com/connections. The application then can no longer reach Drive. Deleting the server's stored authorization ends it on the server side as well.
Changes and contact
Changes are published on this page with a new date. Questions: [email protected].