Last updated: April 16, 2026
QEV does not collect, store, transmit, or process your personal data. We cannot read your vaults. There is no account, no analytics, no tracking, no cookies, and no server-side storage of your content.
QEV encrypts messages on your device using a phrase you choose. The encrypted output (a .vault.json file) never leaves your device unless you explicitly send it somewhere. The phrase never leaves your head (or your keyboard, briefly).
Nothing.
localStorage on your browser only./vault runs under Content-Security-Policy: connect-src 'none', which means the browser itself refuses to let the page call anywhere.QEV's Phase 3 relay at secure.imagineqira.com:7892 is a store-and-forward courier. When you send a vault to a paired peer via the relay, the server sees:
The server does NOT see: your name, device label, IP address (beyond what TCP requires), message content, vault phrase, or any metadata inside the envelope.
Envelopes are deleted from the relay after the recipient fetches them (or after 30 days if never fetched).
QEV has no third-party dependencies that process your data:
The npm package (@bryan237l/qev-cli) is distributed via npmjs.com. npm's own privacy policy applies to the download transaction, but the CLI itself makes zero network calls.
The source code is available at github.com/TheArtOfSound/qev-desktop. You can audit every claim on this page by reading the code.
QEV is not directed at children under 13. We do not knowingly collect data from anyone, including children.
If this policy ever changes, the update will be committed to the repository with a clear diff. The Last updated date at the top of this page will reflect the change.
Questions about this policy: bryanleonard@imagineqira.com