Effective August 9, 2026
Privacy notice
Human Authenticator is designed to operate locally on participating devices. The production app has no Human Authenticator account, cloud database, analytics, advertising, crash-reporting integration, or production runtime backend.
Information stored on your device
The app stores the profile you enter, public device information, paired-contact display information and public keys, trust state, timestamps, and short-lived pairing and replay-prevention records in local app storage. On native iOS and Android, the private Curve25519 identity key is stored using the operating system through Expo SecureStore.
Pairwise keys and displayed comparison values are derived when needed and are not persistently stored. They exist in application memory while being used.
Information shared through a pairing QR
When you choose to show a pairing code, the QR contains your first name and optional last name, optional display phone number, public device key, random session ID, issue and expiration times, and the pairing protocol type and version. Anyone who can see or photograph the QR may read and copy that public metadata.
The QR does not contain your private key, pairwise key, displayed comparison values, photo, contact list, or message history. After scanning, the other person’s phone stores the shared display metadata and public key locally. Removing that contact from your phone cannot erase the copy on the other phone.
Camera access
Camera permission is requested only when you choose to scan another device’s QR code. The app processes the barcode result on the device and does not intentionally capture, retain, upload, or transmit camera photos or video.
Network activity and third parties
The production app does not send profile, paired-contact, key, phrase, QR, camera, or usage data to a Human Authenticator backend. It includes no Human Authenticator login, advertising network, analytics service, or telemetry endpoint.
Apple, Google, Expo, device manufacturers, operating systems, app stores, build and distribution services, and this public website may process technical information under their own policies outside the app’s local-first data flow.
Retention and your controls
Local data remains until you edit it, remove a connection, reset the app, clear app storage, or uninstall, subject to operating-system backup and uninstall behavior. Reset this device clears local app storage, replay records, legacy app data, and the native identity key. Resetting prevents the phone from reproducing existing pairwise phrases.
Human Authenticator has no account or server copy that the provider can access, retrieve, correct, or delete. To remove data from the app, use its profile, connection-removal, or reset controls. The other participant must separately remove information stored on their phone.
Optional phone number
A phone number is optional display text. It is not verified and is not used as an identity or authentication credential. Leave it blank if you do not want it included in your pairing QR or stored on a peer phone.
Children
The app is not directed to children under 13 and the provider does not knowingly collect children’s personal information through a Human Authenticator backend. Parents and guardians should supervise device pairing and the sharing of QR metadata.
Security and limitations
Native secure storage protects private key material at rest but cannot protect a key on a compromised, rooted, jailbroken, debugged, remotely controlled, or maliciously controlled device. The key must enter application memory when used. See the security overview for the complete signal and threat-model limits.
Changes and contact
This notice will be updated before a release materially changes runtime collection, networking, QR contents, accounts, telemetry, or third-party services. The effective date at the top identifies the current version.
For privacy questions, email zacharysean8@gmail.com. Do not send private keys, complete real pairing payloads, or other sensitive material through ordinary email.