Programs Key Sync
Privacy policy
Last updated:
This policy describes a personal, locally operated rclone configuration for one account owner's encrypted KeePass database. It also explains this public information website.
1. Data accessed
After the owner grants Google authorization, rclone can access Drive file contents and metadata under the requested Drive permission. Metadata used for synchronization can include file names, identifiers, sizes, modification times and checksums. OAuth access and refresh tokens allow rclone to operate without asking the owner to sign in for every transfer.
The Google permission is broader than a single file. The local transfer filter selects only the encrypted database and a small safety-marker file; it is not a restriction enforced by Google on the OAuth grant.
2. Purpose and use
Google Drive data is used to locate the selected files, compare saved versions and synchronize them between the owner's computer and Drive. Local state, logs, backups and conflict copies support verification and recovery.
The synchronization configuration transfers encrypted database bytes. It does not decrypt entries or collect the KeePass master password. Google API data is not sold, used for advertising, used to train AI models or used for an unrelated purpose.
3. Storage and security
The database remains encrypted on the owner's computer and in the owner's Google Drive. Local encrypted backups and preserved conflicting versions may also exist. Credentials and tokens are stored in access-restricted local configuration, not on this website. Local configuration is sensitive; obscuring a value is not the same as encrypting the entire configuration.
Logs and synchronization state may contain file metadata or error details. They are kept locally, outside the public website. No database, backup, token or private configuration is intentionally included in the website's deployment files.
4. Transfers and sharing
Synchronization communicates directly between the owner's computer and Google's services. There is no developer-operated server that receives the database or authorization tokens, and this setup does not intentionally disclose Google user data to other people.
Google processes information under its Privacy Policy. Use of Google API data is limited to this personal synchronization function and follows the Google API Services User Data Policy, including its Limited Use requirements.
5. This information website
The site consists of static information pages. It has no sign-in or upload forms, and its source includes no advertising, analytics scripts or application cookies. Cloudflare hosts these public pages, not the private database.
As the hosting provider, Cloudflare may process website-request information, such as IP addresses and browser information, for delivery and security under its Privacy Policy. Visiting these pages does not authorize access to a Google account or start synchronization.
6. Retention, revocation and removal
The owner controls the computer's copies, backups, logs and synchronization state, and the files retained in Google Drive. They remain until the owner deliberately removes them or applies a retention policy; this website does not remove them.
Access can be revoked in Google Account connections by removing this application's access. Revocation stops future authorized access but does not delete existing local or cloud copies. Before removing any local copy, stop synchronization and verify the copies that must be retained.
7. Changes and contact
This policy will be updated if the personal setup's data practices change. The date at the top identifies the latest version.
The app's individual account owner is responsible for this configuration. For privacy questions, use the user-support email shown on the Programs Key Sync Google authorization screen. Never send the master password, database contents or authorization tokens.