ExamPilot Backup

An operational utility that produces encrypted, checksum-verified backups of the ExamPilot study platform's databases.

What it does

For each database of the ExamPilot study platform, ExamPilot Backup produces a point-in-time export, encrypts that export with a symmetric key held only by the operator, records a SHA-256 checksum, and copies the encrypted file to a folder in the operator's own Google Drive.

Each backup is verified after it is written: the encrypted file is decrypted into an isolated temporary database, and integrity, foreign-key, table-count and row-count checks are run. A copy that fails verification is reported as a failure, not as a success.

How it is run

The process is started by an external scheduler or manually by the operator. A scheduled run may start later than its nominal time. The application does not claim guaranteed execution at a fixed time; the time of the most recent successful backup is recorded and can be checked at any time.

Who operates it

This is a single-operator utility for one project. It is not a public service, it has no user accounts, and it does not accept data from third parties. Access to Google Drive is granted by the operator to their own account.

Where data goes

The only external destination is the operator's own Google Drive: encrypted backup files are uploaded there and read back from there for checksum comparison. Nothing is sent to any other service, and no analytics or telemetry is collected.

What it does not do

It does not read, index or analyse other files in Google Drive in normal operation.
It does not access Gmail, Calendar, Contacts, Photos or any other Google service.
It writes only inside its own backup folder in Google Drive.
It does not collect analytics, telemetry or usage data.

Retention

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 nothing is deleted automatically.

Google Drive access

The application requests Google Drive access so it can upload backup archives and read them back for verification. The scope requested is broader than the folder it actually uses; see the Privacy Policy for the exact scope, what is stored, and how to revoke access.