Privacy is a design constraint, not an afterthought.
A password security tool that mishandles passwords isn't a tool worth using. Here is exactly what we see, what we store, and what never leaves your device — no legalese, no ambiguity.
Our privacy stance
- The free browser tools run 100% client-side. Your password is never transmitted, logged, or stored.
- Breach checks use k-anonymity — only a 5-character SHA-1 hash prefix is sent, directly from your browser to Have I Been Pwned (HIBP), not to our servers. HIBP and its CDN (Cloudflare) also receive your IP address.
- If you use the API, the password (or its full SHA-1 hash) is sent to us and processed in memory only. Our code does not log or persist it.
The browser tools
The strength analyzer, breach checker, and generator at
/tools require no account and transmit no
password. There is nothing to opt out of, because there is nothing being
collected by us: no form submission carries your input to our servers, and no
analytics script observes what you type into a password field.
The one exception is the breach check described below. The strength analyzer runs a breach lookup automatically as you type (about 300 ms after you stop typing), so a hash prefix is sent to HIBP without you pressing a button. The breach checker page does the same. Strength scoring and the generator make no network requests.
How k-anonymity protects a breach check
Checking a password against 900M+ breached credentials without ever sending the password itself relies on one property of cryptographic hashes: you can match a fragment of one without reconstructing the rest.
- 1 Your browser hashes the password locally with SHA-1. The plaintext never leaves your device.
- 2 Only the first 5 hex characters of that 40-character hash are sent, directly to HIBP at api.pwnedpasswords.com — never the password, never the full hash, and not to our servers.
- 3 HIBP returns every breach record whose hash shares that 5-character prefix, typically a few hundred candidates.
- 4 Your browser compares the full local hash against that list and discards everything else. The match happens on-device.
The result: HIBP only ever sees a prefix shared by many different passwords, and we see nothing at all. Because the request goes from your browser to HIBP, HIBP (and Cloudflare, which fronts it) can see your IP address and the usual request metadata alongside the prefix. We do not control how HIBP handles that; see HIBP's privacy notice.
The API
Integrating strength, breach, or validation checks into your own signup flow means sending us a password over the wire, so we hold ourselves to a stricter standard than "we promise not to look."
Every request travels over TLS. On arrival, the password exists only in process memory for the duration of that single request — it is never written to disk, never included in logs or error traces, and never persisted in a database, cache, or backup, on any plan. Our code does not log request bodies. The hosting platform (Azure) may record standard request metadata such as URL, status code and IP address in its own operational logs.
The breach endpoint has two modes. If you send a plaintext password, we hash it and forward only the 5-character prefix to HIBP. If you send a SHA-1 prefix and suffix, we receive the full hash, so that mode is not k-anonymous towards us (the plaintext still never reaches us). In both cases only the prefix goes to HIBP.
The only thing we store per request is a monthly request counter tied to your account, used for quota enforcement and rate-limiting. It is never linked back to the password or username you sent.
What we collect
We keep this list short on purpose. If it isn't needed to run the product or the business, we don't collect it.
For API accounts
You sign in with GitHub or Microsoft through Azure Static Web Apps; we store your account identifier, sign-in provider and the email or login name the provider returns, a hash of your API key (with its first and last characters), your plan, and a monthly request count. If you subscribe, Stripe processes your payment and we store your Stripe customer and subscription identifiers (we never see card numbers). We don't profile usage patterns or resell account data.
For passwordify.xyz
We run no analytics or tracking scripts on the site. Our hosting platform (Azure Static Web Apps) keeps standard server logs. No password content, form input, or keystroke is collected on the marketing site or the tools.
Cookies
We set essential cookies only — the authentication cookie needed to keep you signed in to the developer dashboard. There is no advertising or cross-site tracking cookie set by us on passwordify.xyz. Stripe Checkout and the GitHub/Microsoft sign-in pages are hosted by those providers and set their own cookies.
Your light/dark theme preference is saved to
localStorage on your device. It never
reaches our servers and never leaves your browser.
Data requests & contact
Who processes your data
Recipients of data, depending on what you use: Microsoft Azure (hosting, Static Web Apps sign-in, Functions and Table Storage for account and usage records), GitHub or Microsoft (the sign-in provider you choose), Stripe (payments), and Have I Been Pwned with Cloudflare (breach-check hash prefixes and IP address, sent directly from your browser).
Account, key and usage records have no automated expiry today; they are kept until you ask us to delete them. You also have the right to lodge a complaint with your data protection supervisory authority (in Italy, the Garante per la protezione dei dati personali).
Under GDPR and CCPA, you have the right to access, correct, export, or delete the personal data we hold about you. Since that data is limited to your account email and usage counts, most requests take minutes, not weeks — email hello@passwordify.xyz and we'll act on it, typically within 30 days at the outside.
Changes to this policy
If this policy changes in a way that affects what we collect or how we use it, we'll update the date below and, for material changes, notify account holders by email before the change takes effect.
Last updated: November 2026