Privacy policy
AI Trading 212 is an independently operated market-data database maintenance application. It is used by its owner to maintain research data in Google Drive through automated GitHub Actions. This document describes the Google account information the application may access and why.
1. Information and access
When the Google account owner authorizes access, the application may read Google Drive files, folder names, file metadata, file contents and historical revisions that relate to the owner's database. It may create files, update stored datasets, organize backups and delete obsolete files or revisions when the owner authorizes a cleanup. The requested Drive OAuth scope permits writes and deletion; this is not a read-only integration.
2. Purposes
- Retrieve and maintain market history and derived research databases.
- Verify exact file revisions, data integrity and certified database snapshots.
- Retain backup generations and provide recovery or audit evidence.
- Review storage consumption and perform specifically authorized data-retention cleanup.
3. Storage and processing
Database files are stored in the account owner's Google Drive. Maintenance tasks execute using GitHub Actions and credential material stored in restricted GitHub Actions secrets. Operational logs and reports may store file identifiers, file hashes, timestamps and completion results. The public website does not receive Google OAuth credentials or host the private database.
4. Sharing and use restrictions
Google Drive data obtained for this application is used for the owner-authorized purposes above, not for advertising or sale. It is not transferred to data brokers or used to train general-purpose AI models. Information may be handled by Google and GitHub as needed for storage, authorization and maintenance operation, or where disclosure is legally required.
The operator intends to follow the Google API Services User Data Policy, including its Limited Use requirements.
5. Retention and deletion
Certified datasets and historical revisions are retained according to the owner's backup and storage-retention rules. When authorized, obsolete revisions may be irreversibly deleted after dependency verification. Maintenance records may be retained to demonstrate integrity and recovery. Revoking Google access does not automatically erase files already stored in Google Drive.
6. Security and account controls
Access uses Google OAuth authorization; secrets are not published through this website. The account owner may revoke the application's authorization from Google Account third-party connections. Once revoked, the application cannot continue accessing Google Drive until authorization is restored.
7. Contact and changes
For enquiries or data requests, use the application's support contact provided during Google authorization. This policy will be updated if the application's data practices materially change.