Privacy by design

Your password stays yours.

The FunPass analyzer runs entirely in your browser. It does not save, submit, log, or transmit what you type. The optional breach check sends only a partial hash after you request it.

  • No account required
  • No password database
  • No request while typing
  • Clear the field at any time
Open the private lab

Methodology and threat model

Trust should be
inspectable.

FunPass explains what it measures, what leaves the device, and where its conclusions stop. A security tool should make its limitations visible.

01

Local analysis

The estimator runs in this tab. The password is kept only in temporary component memory and is not logged, saved, placed in a URL, or submitted to FunPass.

02

Pattern-based scoring

Scores use zxcvbn-ts to model common passwords, dictionary terms, dates, repeats, keyboard paths, sequences, and likely guesses. It is an estimate—not a guarantee.

03

Optional breach request

Only after you press the breach-check button, the browser sends a five-character SHA-1 prefix to HIBP. Response padding is requested and matching finishes locally.

04

What strength cannot stop

No password score prevents phishing, malware, insecure server storage, or account recovery abuse. Unique passwords, MFA, passkeys, and secure services work together.

LIVE PRIVACY CONTRACT

What happens when you type

  • Password stays in temporary memory
  • No request while typing
  • No browser storage
  • No URL or analytics value
INPUTLOCAL MODELRESULTNothing sent