Private utility · Effective November 12, 2026

Privacy Policy

Quartercast Backup is a private archival utility under preparation for the account owner's own research records. The Google Drive connection is not activated by this informational website.

Purpose and scope

When configured by the owner, the utility will transfer verified research backup archives and their integrity manifests to a Google Drive location controlled by that owner. It is not a public application for other users.

Google user data access

The intended authorization uses the Google Drive drive.file scope, limited to files and folders created or authorized through the application. The utility does not need to read the owner's unrelated Google Drive documents, Gmail, or Google Photos. The actual authorized scope will be confirmed before first use.

Storage and processing

Backup archives may include the research records explicitly selected by the owner. Archive files and integrity manifests will be stored in the owner's Google Drive. OAuth credentials, if configured, must be kept in a private server-side configuration and must never appear on this public website. Data is transferred over authenticated HTTPS connections. Access and retention remain under the owner's control.

Sharing and use restrictions

Archive contents are not intentionally made public or sold. The utility does not use Google user data for advertising or unrelated profiling. The service uses Google's infrastructure to store authorized backups; it does not share those archives with other third-party services as part of this workflow.

Website data

This is a static informational website without account registration, analytics scripts, advertising trackers, or form submissions. The hosting provider may process standard HTTP request data according to its own policies.

Deletion, retention, and revocation

The owner can remove archived files in Google Drive and revoke the app's Google account authorization at Google Account connections. Revocation stops future authorized access but does not by itself delete previously stored archive files. Source-database retention and removal are separate, explicitly approved processes.

Changes and contact

This policy must be updated if the implementation or Google Drive permissions change. For privacy or access inquiries, contact the developer using the support contact shown on the Google OAuth consent screen.