Privacy

WithPasskey holds no personal data in the conventional sense — no names, emails, or phone numbers exist in the product. What little it stores is public credential material and operational metadata.

The service

Accounts are identified by opaque binary ids and pairwise sub values — deliberately unlinkable across relying applications. Stored per credential: public key, signature counter, transports, aaguid. Stored per flow: hashed tickets/codes, short-lived request state, tenant-scoped audit events.

This website

Analytics (Google Tag Manager) load only after you accept them in the consent banner — choose “analytics only” or decline and the tag never ships to your browser. Declining costs you nothing functionally. Server logs carry the usual request metadata (IP, user-agent, path) for security and reliability.

Your rights

Because the service stores no identifiers that map to you, a data request is satisfied by construction: there is no name or email to look up. If you are an operator or relying party with account data questions, contact us via the channels on this site.

This page describes current product behaviour; material changes will be published here before they ship.