Privacy Policy
ExamPilot Backup ("the application") is a single-operator utility that backs up the databases of the ExamPilot study platform. This policy describes what Google user data the application accesses, why, how it is stored, and how access can be revoked.
1. What Google data the application accesses
| Data | Purpose |
|---|---|
| Files created by the application inside its own backup folder in Google Drive | Uploading encrypted database backups, and reading them back to verify that the stored copy is byte-identical to the local one. |
| Basic account and storage-quota information for the connected account | Checking that the destination is the expected account and that there is enough free space before an upload. |
In normal operation the application does not open, modify, move or delete any file in Google Drive other than those it created itself in its own backup folder. It does not access Gmail, Calendar, Contacts, Photos or any other Google service.
2. OAuth scope requested
The application currently requests the scope https://www.googleapis.com/auth/drive, which grants access to all files in the account.
This is broader than the application needs. The file-transfer tool used by the application supports narrower Drive scopes — for example drive.file, which limits access to files the application itself creates — so the broad scope reflects a configuration choice made when the connection was set up, not a requirement of the tool. In practice the application only writes to, and reads from, one dedicated folder.
A narrower scope would be more appropriate. Changing it requires re-authorising the connection; if the scope changes, this policy will be updated accordingly.
3. How the data is used
- Backup archives are encrypted on the operator's machine before they are uploaded. The uploaded files are encrypted containers; Google does not receive readable database content.
- Uploaded files are read back by the application itself, solely to compare checksums.
- Data is not used for advertising, profiling, model training or any secondary purpose.
4. Storage and retention
- Encrypted backup files are stored in a dedicated folder in the operator's own Google Drive. That folder is private to the account and is not shared publicly.
- Backups are currently retained until the operator removes them. The software contains a rotation policy for daily, weekly and monthly copies, but that policy is not enabled at present, so no backup is deleted automatically.
- Deleting backup files or the backup folder in Google Drive removes those copies. It does not revoke the application's authorisation: the application keeps its granted access and can upload again on the next run.
- Revoking the application's authorisation (see section 7) is what ends its access to the account. Revocation takes effect immediately and does not delete any files that already exist in Google Drive.
5. Sharing and transfer
The only external destination for data is the operator's own Google Drive, used as the storage location for encrypted backups. Data is not sold, rented or disclosed to any other third party, and the application communicates only with the Google Drive API.
6. Security
- Backup archives are encrypted with AES-256 symmetric encryption before upload. The encryption key is held by the operator and is not stored in Google Drive.
- OAuth credentials are stored on the operator's own machine with owner-only file permissions.
- Integrity is checked after every backup is written; a copy that fails verification is reported as a failure.
No system is perfectly secure. This section describes the measures actually in place, not a guarantee.
7. Revoking access
Access can be revoked at any time at myaccount.google.com/permissions by removing ExamPilot Backup from the list of apps with account access. Revocation takes effect immediately; the application will then fail to upload or read backups until it is authorised again.
8. Changes to this policy
If the application's data practices change, this page will be updated and the date at the top revised.
9. Contact
Questions about this policy or about data handling can be sent to the support address listed on the OAuth consent screen for this application.