Your offline authenticator
Authenticate websites or verify a person you paired with.
A new version is ready.
Create your vault
A passkey protects credentials stored on this phone. Your device will ask for biometric or screen-lock verification.
Demo-only passphrase fallback: lower assurance. Use at least 16 characters.
Paired sites
Paste QR text — accessibility / development fallback
People and phones
Pair in person once. Later, either phone can start a fresh verification of the saved keys.
Known contacts
Pair a new phone
Both people open this screen and enter a name. One chooses Start pairing; the other scans that phone's QR.
Paste a peer QR — accessibility fallback
Both phones compare a check code before saving. For a lost or replaced phone, forget the old contact and pair together again.
Compare this check code on both phones:
QR text — accessibility fallback
Paste their reply — accessibility fallback
Scan with rear camera
Security, storage and updates
People verification proves possession of previously paired keys. Pair in person, compare both check codes, and associate the keys with the person present. Remote relaying and compromised unlocked devices remain possible.
The phone checks the paired site's secret. A live phishing proxy can still relay both codes. Always compare the displayed origin with the browser address bar.
The website signs you in before you check its response. It cannot know whether you completed that final check.
Clearing browser data or losing this device loses credentials. No backup or export is provided. Local removal does not revoke the credential at the website.
A compromised deployment, script, dependency or service-worker update can misuse unlocked secrets. JavaScript cannot guarantee memory erasure.