Operator/contact: 8303junyoung@gmail.com. This disclosure covers BioCompute Private Backup, not unrelated Google applications or a public research-data submission service.
Only the drive.file permission is requested. The integration accesses metadata and content of the specifically granted backup folder and backup objects it creates, including object identifiers, names, sizes, checksums, parent folders and access permissions. Metadata is used to verify the destination, owner-only access and integrity. OAuth access and refresh tokens are used solely to perform the authorized backup and recovery operations.
Consistent SQLite snapshots and their reference/restore manifests are encrypted before off-site upload. Private research sequences and plaintext databases are not uploaded to Google Drive by this integration. Ciphertext may contain encrypted research records and is stored in the owner's selected private folder. The owner controls the recovery identity separately. Authorized recovery decrypts only in an isolated environment.
The deployment provider processes server-side authentication material and the original service data; Google processes the explicitly authorized Drive metadata and encrypted objects. Tokens and private recovery keys are not included in source repositories, frontend bundles, review packages or monitoring emails. Email alerts contain allowlisted operational event codes rather than research sequences.
The integration does not sell Google user data, use it for advertising, or transfer it for unrelated model training. Use of Google user data is limited to the disclosed owner-requested backup, integrity verification, recovery and operational-support purposes. It follows the Google API Services User Data Policy, including its Limited Use requirements.
The planned online analysis availability period is 30 days. This is not a claim that every database record or off-site recovery point is automatically erased after 30 days. Approved scientific records, shortlists, audit history and backup retention are governed separately. Destructive cleanup remains disabled until an explicit owner-approved policy is applied. The owner can revoke the app in Google Account settings, stop future backups, and request coordinated object/credential deletion by contacting the operator. Revoking access does not itself delete existing ciphertext or restore records.
Owner-only folder access, verified TLS, per-file checksums and authenticated encryption are used. Tokens can be revoked or expire. The recovery identity is essential; losing every copy can make encrypted data unrecoverable. Operational validation and recovery drills do not guarantee uninterrupted service or wet-lab/scientific outcomes.