Security and privacy
Everything on your computer. Nothing in the cloud.
KeyPing has no account, server or sync. This page explains what it protects, how, and where its limits are, using facts taken from the current version’s source code.
Where your data lives
The vault is an encrypted file in your user’s application data folder:
- Windows:
%APPDATA%\keyping-ui - Linux:
~/.config/keyping-ui
It is not sent anywhere. To move it to another computer, export an encrypted file and import it there.
Encryption
| Vault | AES-256-GCM, with a random 12-byte nonce on every write and a 16-byte authentication tag. |
|---|---|
| Key | Derived from your master password with PBKDF2-HMAC-SHA512, 600,000 iterations and a random 32-byte salt. |
| Master password | Never stored. Only a check value encrypted with the derived key is kept, to tell whether the password is correct. |
| Key in memory | Held by the main process while the vault is open and overwritten with zeros on lock. |
| Exported files | AES-256-GCM with a key derived from the master password using PBKDF2-HMAC-SHA256, 600,000 iterations and its own 16-byte salt. |
| Older vaults | Vaults from 1.0.x (120,000 iterations and a key file) still open and move to the current scheme after the first unlock. |
Protection while in use
- Failed attempts: after 3 free attempts, each failure adds a growing delay (5 seconds, doubling up to 1 hour). The counter survives an app restart.
- Auto-lock after 1 to 30 minutes of inactivity (5 by default) and when the computer suspends or the session is locked.
- Clipboard: copied secrets are cleared after 20 seconds only if the clipboard still holds the same content, and on lock. On Windows they are flagged to stay out of clipboard history (Win+V) and cloud clipboard; if that fails, a normal copy is made.
- Links: only http and https are accepted, with no embedded credentials, and they always open in your browser, never inside the app.
- Electron isolation: the interface has no access to Node.js (contextIsolation, sandbox, nodeIntegration off), the app denies permissions such as camera or microphone, and the executable ships with Electron fuses that prevent running it as Node.js, debugging it from the command line or loading code outside the verified package.
- Integrity: the app checks the vault structure and warns if it detects corruption.
Which connections the app makes
By design, only one: checking GitHub Releases for a new version, a few seconds after start-up and when you ask in Settings. You can turn the automatic check off. Automatic download is off by default: you decide when to download.
Known exception on Linux. In the current version, when it starts on Linux, the Electron engine tries to download a spell-check dictionary from a Google server (redirector.gvt1.com), even though KeyPing has spell checking turned off. Nothing from your vault is sent, but it does reveal your IP address and system language. A fix is pending for an upcoming version.
There is no analytics, telemetry, remote crash reporting or icons fetched from the internet. Your accounts’ links only open when you click them, and your browser opens them.
How updates are verified
Since 1.3.0, each version’s metadata (latest.yml and latest-linux.yml) is signed with an Ed25519 key whose public half is built into the app. KeyPing refuses to download or install an update if the version, file names, sizes or SHA-512 hashes are not covered by a valid signature. So even if someone replaced a release file, the app would not install it.
For the first install, each release ships SHA256SUMS.txt with the SHA-256 of every installer. How to check it.
Limits, plainly
If you forget the master password, there is no recovery. There is no back door and no copy of the key: neither the author nor anyone else can open your vault without it. Exported backups are also encrypted with the master password, so they do not help without it either. Keep it somewhere safe.
- No sync: if you lose or wipe the computer without an exported backup, you lose the vault.
- KeyPing protects data at rest. It cannot protect you from malware that already controls your computer while the vault is open.
- On Linux, your desktop’s clipboard history may keep copied secrets; KeyPing can only clear the current clipboard.
- There is no browser extension or autofill: you copy and paste.
- Installers are not code-signed for Windows, so SmartScreen may warn during installation.
- The code has not had an external security audit. It is open so anyone can review it.
Found a security problem? Contact the author through GitHub.