Privacy Policy

Data accessed and handled

The application requests the Google Drive drive.file scope. It creates and accesses archive files and folders created by or explicitly authorized for this application; it does not request blanket access to the owner's entire Drive.

Data handled includes OAuth client and grant identifiers, access and refresh credentials, the Drive account's stable permission identifier, file and folder identifiers, parent and ownership/permission metadata, archive names and sizes, integrity checksums and manifests, and the research artifacts included in the owner's archive. Research artifacts may themselves contain information selected or captured by the owner.

Purpose of use

This information is used to authorize the collector, bind access to the correct owner and archive folder, upload and retrieve archive contents, verify integrity, restore backups, and support the owner's research archive and recovery workflow. Initial qualification uses isolated synthetic archives.

The application does not sell Google user data or use it for advertising. It does not transfer Google user data for an unrelated third-party purpose. Access is limited to the archive and recovery practices described here. Any materially different data use must be disclosed and authorized before it is introduced.

The application's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including applicable Limited Use requirements.

Storage and service providers

Research archives are stored in the owner's Google Drive and the collector's storage. OAuth credentials and binding records are stored in access-controlled local and collector-server files. The owner's setup uses a private transfer through the collector hosting provider's secret configuration to install the authorization.

Google processes data to provide OAuth and Drive services. Render processes data to host the private collector. Cloudflare provides domain/DNS services and hosts this public informational website. These providers operate under their own applicable terms and privacy practices. This informational website has no connection to the collector and does not receive its Google credentials or archive contents.

Connecting Google Drive to another application, including an owner-selected research assistant, is a separate permission decision. This collector grant does not automatically authorize another application or publish an archive.

Retention, deletion and revocation

The owner controls archive retention and deletion in Google Drive and collector storage. Authorization records are retained while the integration is in use and for recovery as needed by the owner. Deleting one copy does not necessarily delete another backup or a provider-managed retained copy.

The owner can revoke the application's access in Google Account third-party connections. Revocation stops future access under that grant; it does not automatically delete existing archives or local/server authorization records. The owner can remove those separately after preserving any required records.

For a privacy, retention or deletion request, contact the operator using the address below.

This informational website

These are public information pages. The site contains no archive viewer, account registration, Google login, analytics scripts or advertising scripts. The hosting provider may process request information such as IP addresses and browser metadata to deliver and secure the pages.

Contact and changes

Operator contact: broxigar@googlegroups.com.

This policy will be updated when the application's data practices change. The effective date identifies the current policy version.