BDS Backup Drive
Privacy policy
Last updated: 6 November 2026
This policy describes BDS Backup Drive, a private administrative utility. Its scope is separate from the public-facing privacy notices for Disclosure Desk and Our Cinema.
1. Who operates this utility
BDS Backup Drive is operated by Boyd Digital Studios. It is used to protect the company's own Disclosure Desk and Our Cinema data, and is not offered as a public cloud-storage service. Questions about this utility or its use of Google Drive data can be sent to boyddigitalstudios@gmail.com.
2. Google Drive access requested
Authorised Boyd Digital Studios administrators connect a dedicated Google account through Google OAuth. The utility uses Google Drive to create and identify backup folders, upload encrypted archives, list stored backup files, read file metadata and verify uploads. It is intended to access only the backup destinations configured by its operator.
The present integration may request full Google Drive access because it must work with pre-existing folders. This permission is broader than those folders, even though our backup runner is designed to use its designated destinations only. We will review narrower permissions when technically feasible.
3. How Google user data is used
Information received from Google's APIs is used solely to establish and maintain the authorised backup connection, perform the backup operations described here, and check their integrity. We do not use Google Drive data for advertising, profiling, selling personal information, or training general-purpose AI models.
Our use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. What the archives contain
Snapshots of the two BDS applications may include database records, account information, investigation Boards, research documents, cinema history and associated Storage files needed for disaster recovery. These records are exported from the relevant service, not from unrelated files elsewhere in the connected Google Drive.
The runner uses age encryption to encrypt each archive before Google Drive upload. Its private decryption identity is held separately from the upload service. Temporary readable export files may exist on the controlled backup runner during execution and are removed when the temporary workspace is deleted. An encrypted archive is not a substitute for a tested restoration process.
5. Credentials, storage and service providers
OAuth tokens used for unattended Drive access and the credentials needed for database exports are configured in private GitHub Actions repository secrets. The runner receives these credentials only for its authorised task. Encrypted archive files are kept in dedicated project folders in the BDS-controlled Google Drive account. Supabase, GitHub and Google are infrastructure providers involved in these workflows.
We do not intentionally disclose readable backup contents to unrelated third parties. The Google account owner controls the permissions granted to this app.
6. Retention and deletion
Encrypted backups are currently retained until an authorised operator removes them. An automatic deletion or retention schedule is not yet active. When we adopt an automated retention policy, this notice will be updated. OAuth tokens remain configured until revoked or rotated. Revoking Google access does not automatically delete archives already stored in Drive.
7. Security and recovery limitations
Our security measures include encryption before upload, separately held decryption keys, access-controlled credentials, integrity verification and isolated recovery testing. They reduce risk but cannot guarantee absolute security. The Google Drive authorisation scope is wider than the intended backup destinations and is a security consideration.
Database and Storage archives do not by themselves preserve every cloud platform setting, external integration or service credential. Additional steps may be needed in a real recovery.
8. Revoking access, questions and requests
The Google account owner may revoke this utility's access through Google Account → Third-party apps and services. Revocation prevents future authorised operations but does not automatically delete existing encrypted files. Owners can delete retained archives separately through Google Drive.
For privacy questions, access requests or deletion enquiries relating to BDS Backup Drive, email boyddigitalstudios@gmail.com. Requests concerning individual Disclosure Desk or Our Cinema accounts are handled in accordance with those products' own privacy notices and applicable law.
9. Changes to this policy
This page will be updated if the utility's Google permissions, processing practices or retention rules materially change. The revision date above identifies the version shown.