KeyGlint / The policy
Privacy.
Your authentication data belongs on your Mac. Here’s how KeyGlint handles it.
KeyGlint Privacy Policy · Effective November 7, 2026
A local app
KeyGlint works locally on your Mac. The app does not collect or transmit your personal data, authentication secrets, account names, one-time codes, or usage information to the developer. It includes no advertising, analytics, tracking, or third-party SDKs.
Accounts and preferences
Account names and authentication secrets are stored in the macOS Keychain. Appearance and code visibility preferences are stored locally in the app’s preferences. QR images you select are processed on your Mac to import accounts.
Copying codes
When you copy a code, KeyGlint writes it to the system clipboard. Other apps may be able to read the clipboard. KeyGlint checks the clipboard when the copied code is about to expire and clears it if it still contains that code. Clearing requires KeyGlint to remain running.
Encrypted backups
Backups are written only to a location you select and are encrypted with your passphrase. KeyGlint does not save that passphrase. If you choose a cloud-synced folder, your storage provider handles that file under its own policies.
Removing your data
You can remove accounts in KeyGlint. Removing the app does not necessarily remove its Keychain items or backups. Delete backups separately when you no longer need them.
Questions
For privacy questions, use the developer contact details on KeyGlint’s App Store support page when the app is released. Our support guide covers common questions in the meantime. Do not include authentication secrets, QR codes, one-time codes, or backup passphrases in support requests.
This website
These pages use no cookies, analytics, tracking scripts, or third-party fonts. The interactive desktop demo runs in your browser with sample accounts. Search text, settings changes, account changes, and notifications exist only in page memory and reset when the page reloads. The demo does not read files, access the clipboard, save demo data, or transmit your input.
A future hosting provider may process ordinary connection information, such as IP addresses and request logs, to serve the site.