Privacy policy

Closer Cultures Backup · Effective date: 15 November 2026

This notice covers the private Closer Cultures Backup application, not the general public Closer Cultures website.

Operator and contact

The application is operated for the Closer Cultures project by its authorised account holder. For privacy questions or requests about this application, email scottheptonstall@gmail.com.

What Google data we access

With authorisation from the Google account holder, the application uses the Google Drive API with the drive.file scope. This permits access to files created by the application or expressly made available to it, rather than blanket access to unrelated Drive files.

It processes OAuth access/refresh credentials needed for authorisation and Drive file identifiers, names, app-specific properties, upload/download results and verification checksums. It does not request Gmail, contacts or general Drive access.

Why we use that data

The application creates encrypted secondary copies of selected historical Closer Cultures research audit archives in an application-owned Google Drive folder. It may retrieve those files to check that decryption succeeds and that recovered contents match the source archive manifests. It does not use Google user data for advertising, profiling or model training.

How data is stored and protected

The audit file contents are encrypted using AES-256-GCM before upload to Google Drive. Archive decryption keys are managed separately from the uploaded ciphertext. The authorised local backup workflow stores Google OAuth credentials on the account holder’s computer. Google processes stored encrypted files and related account/service metadata under its own policies. The current application does not operate an unattended cloud-based backup schedule.

Sharing and use restrictions

Encrypted files and necessary metadata are transferred to Google Drive to provide the requested backup and verification service. The application does not sell Google user data or share it with advertisers or unrelated third parties. Disclosures may occur where required by law. Use of Google API information follows the Google API Services User Data Policy, including applicable Limited Use requirements.

Retention and deletion

Encrypted historical audit backups are currently retained for record preservation and disaster recovery; no automatic expiry or deletion schedule is enabled for these files. Requests about access or deletion can be sent to the contact email above and will be assessed against the project’s preservation obligations. Account holders may revoke OAuth access via Google Account connections. Revocation prevents future authorised access but does not itself delete files already stored in Google Drive.

Policy updates

Material changes to requested permissions, recipients, storage locations or processing practices will be assessed and reflected in this notice before an amended workflow is activated. The effective date will be updated when changes are published.