Privacy policy

Last updated 12 September 2026

The application

QtPass runs entirely on your machine. It has no network code, no telemetry, no crash reporting, no update check and no accounts. We do not know who uses QtPass, how often, or on what.

Your password store is read and written by gpg and, optionally, pass and git, which you install and configure yourself. If you point git at a remote, your encrypted store goes wherever you point it; that is between you and your git host. QtPass itself never sends anything anywhere.

QtPass keeps its own settings (paths, timeouts, layout) in a local configuration file managed by Qt. When you click a URL stored in a password entry, QtPass hands that URL to your default browser and nothing else.

This website

qtpass.org is a static site. It sets no cookies and runs no analytics. Fonts and scripts are served from qtpass.org itself.

The pages embed version badges from repology.org and build badges from GitHub and AppVeyor. Your browser fetches those images from their servers, which see your IP address the way any image load does. That is the only third-party request this site makes.

The web server keeps ordinary access logs for operational purposes. They are not shared and are rotated away.

Contact

Questions about any of this: help@qtpass.org, or open an issue on GitHub.