21Keys Backups
Privacy policy
Effective November 21, 2026
This policy covers the 21Keys Backups utility and this information website, operated by Purpose Driven Results. It does not replace the privacy information for the wider 21Keys listener or creator services.
Purpose and current status
The utility supports backup, integrity checking and recovery of the 21Keys platform. Independent scheduled operation is still being configured. The practices below describe the authorized backup workflow; automated retention cleanup is not currently enabled.
Google information and permissions
The intended Google permission is per-file Drive access (drive.file), covering files created by the utility or explicitly made available to it. The utility uses backup contents and metadata such as file names, identifiers, folder locations, sizes and checksums to upload, locate, verify, download and manage recovery copies. It does not request Gmail, Contacts or Calendar access, or general access to unrelated Drive files.
Google issues authorization tokens after administrator consent. These tokens allow approved backup operations without requiring a fresh sign-in for every run. We do not collect the administrator’s Google password. Authorization credentials are kept in restricted local setup storage and, when hosted operation is enabled, the runner’s encrypted secret storage. They are not included in public source code or backup download links.
Platform backup contents
Archives can contain account and authentication records, creator and venue information, playlists, listening records, uploaded music, artwork, lyrics, and recovery materials. This platform information is collected through 21Keys, not extracted from unrelated Google Drive documents. Backup archives are encrypted before they are uploaded to Drive. An authorized recovery operation decrypts a copy in a controlled environment.
Use and disclosure
Data is used only to operate, secure, verify, maintain and restore the backup service. We do not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. Access by administrators is limited to setup, support, security and recovery needs.
Google Drive stores the encrypted archives and associated file metadata. The planned hosted runner is GitHub Actions, which will temporarily process platform exports and use stored authorization credentials. An independent monitoring provider may receive backup timing and success or failure signals, not archive contents or Google authorization tokens. The public information pages are hosted using OpenAI Sites and its hosting infrastructure. These providers may process data in countries other than your own. Information may also be disclosed when legally required.
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
The proposed schedule retains seven daily, four weekly and three monthly successful recovery copies, with designated baseline backups retained separately. This schedule is not yet active; current backups remain until the administrator removes them. Operational records may be retained to investigate errors and document recovery checks. Authorization tokens are retained while the connection is needed, unless revoked or replaced.
The administrator can delete stored backup files through Google Drive and request removal of locally retained copies and credentials. Deletion from active platform records may not immediately remove those records from historical encrypted backups; they remain until those copies expire or are deleted. If a backup is restored, applicable deletion requests must be reapplied.
Revoking access and contacting us
Google authorization can be revoked at Google Account connections. Revocation stops future authorized Drive operations but does not itself delete existing backup files. For access, correction, deletion or privacy questions, email purposedrivenresults1@gmail.com.
This website
These pages contain no sign-in form, advertising, analytics scripts or embedded media. The hosting provider receives ordinary request information, such as IP address, browser details and request time, to deliver and secure the pages. Emailing us supplies the contact details and message you choose to send.
Changes
We will update this policy and its effective date when backup practices change. Material changes to requested Google permissions require an updated authorization process.