Operator: AT Smart Home Pte Ltd
Application: Adrian Content Engine — GitHub Drive Archive
Contact: adrian@atsmarthomesg.com
Status: Pre-launch — automatic archival is not yet operational
1. Purpose
GitHub Drive Archive is a private internal utility under development to transfer authorised GitHub Actions evidence to Google Drive for backup, verification, troubleshooting and recovery.
The application is not intended for public registration or general consumer use.
2. Google Drive access
The application is configured to request the Google Drive drive.file OAuth permission.
This permission allows access to specific files created or made accessible to the application, rather than unrestricted access to the account owner’s entire Google Drive.
Google Drive access requires authorisation by the Google account owner.
3. Information processed
When operational, the application may process:
- Approved GitHub workflow evidence and archive packages.
- Repository, commit, workflow and run identifiers.
- File names, sizes, timestamps and SHA-256 checksums.
- Google Drive file identifiers and archive verification receipts.
- OAuth credentials required for authorised access.
The application is not designed to collect unrelated personal Google Drive files.
4. Use of information
Information is intended solely for internal evidence preservation, integrity verification, troubleshooting and recovery.
Google user data will not be sold, used for advertising or used to train general-purpose AI models.
The application is intended to comply with the Google API Services User Data Policy, including applicable Limited Use requirements.
5. Sharing and service providers
The intended workflow involves GitHub for authorised workflow execution and Google Drive for storage.
GitHub Actions encrypted secrets are the preferred credential-protection design but have not yet been configured.
No additional service providers have been approved to receive Google user data as part of this archive workflow.
6. Security
The planned security measures include restricted workflow access, protection of OAuth credentials, archive-integrity checks and independent verification of uploaded files.
These measures are still being implemented and tested. The application is not yet operational.
7. Retention and deletion
The operator has approved a 90-day retention target for ordinary Google Drive CI evidence after the archive system becomes operational.
Critical evidence may be retained separately for longer-term recovery.
The planned application may automatically delete an eligible GitHub Actions artifact only after its corresponding Google Drive archive has been independently downloaded, verified and recorded successfully.
Automatic deletion of Google Drive archives is not enabled or authorised. Protected historical and critical evidence is excluded from automatic GitHub cleanup.
8. Revoking access
The Google account owner can revoke the application’s Google Drive authorisation through Google’s third-party connection settings.
Revocation will stop further authorised operations but will not automatically remove previously stored archives.
9. Changes to this policy
This policy may be updated to reflect changes in the application’s operation, security measures, retention practices or service providers.
10. Contact
AT Smart Home Pte Ltd
adrian@atsmarthomesg.com
This utility is currently in pre-launch development. Described future automation must not be interpreted as functionality already deployed.
