Privacy policy
Updated: 28 October 2026
This policy covers the Google Drive connection for BBC Workplace dashboards, administered by Tony Ball. Contact: balltony2025@gmail.com.
Data and purpose
Scripts process authorized energy supplier reports and building operational exports, which may include meter identifiers, site details, energy readings and account-related information. Google Drive folder and file metadata is read to locate configured archives and verify uploads. Reports and verification manifests are uploaded for reporting and audit history.
Google permissions
The uploader requests https://www.googleapis.com/auth/drive. This grants broad Drive access for the consenting account. The uploader is configured to operate in designated archive folders; that restriction is enforced by application code, not by folder-specific Google permissions.
Processing and storage
Scheduled collection runs on GitHub Actions. OAuth refresh credentials are stored as GitHub Actions secrets. Reports are processed temporarily on runners and archived in Google Drive. Run-status records and upload receipts may be kept in GitHub Actions for up to 14 days. Cloudflare hosts this information site and may process ordinary request metadata to deliver and secure it.
Use and sharing
Google user data is used for the reporting and archive functions described here. It is not sold, used for advertising, or used to train general-purpose AI models. Google and GitHub process information needed to provide the infrastructure. Data is available to people authorized to access the configured archives and dashboards, and may be disclosed where required by law.
The application’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Retention and deletion
Archived reports are retained for reporting and audit history until the administrator deletes them under applicable records requirements. No automatic archive deletion period is configured. Contact the administrator to request access, correction or deletion of application-managed data.
Revoking access
Remove authorization through Google Account connections. The administrator can also disable collection and remove stored GitHub credentials. Revocation stops future authorized access but does not automatically delete existing archived reports.
Security and changes
Credentials are stored separately from source code and public pages. Access is controlled through configured Google Drive and GitHub permissions. This policy will be updated when the application’s data handling changes.