Frequently Asked Questions

They could, but only within a 24-hour window before the code changes. And they would still need an existing connection to you (which you would have to approve first) or trick you into accepting them as a new connection (where the trust score would warn you). The time-limited nature of codes makes replay attacks very difficult.

At 100 connections (typical power user), the probability of a collision is less than 0.001%. If it does occur, the app shows both matching contacts and asks you to clarify which person you meant. No security breach occurs — you simply choose the right person.

Codes are based on 24-hour time windows. As long as your clock is within a few minutes of correct, codes will match. The app can also check adjacent time windows (±15 minutes) to handle slight clock drift. If your clock is very wrong, the app will show a warning.

No. Codes are generated on your device using the encrypted secret. The secret is encrypted end-to-end — only your devices can decrypt it. We never see the decrypted secret, we never see the codes (they're not transmitted), and even if we wanted to, we cannot generate your codes. This is called "zero-knowledge" architecture.

Even if our servers are completely compromised, attackers get only encrypted data they cannot decrypt. Your private keys never leave your device. Your secrets remain yours. A server breach is irrelevant to your security — this is called "data protection by design."

These are two different situations. If someone steals your account credentials, they gain almost nothing: verification secrets are end-to-end encrypted per device, so a stolen password alone cannot generate your codes — adding a new device requires your recovery key or approval from a device you already own. If someone takes control of your unlocked device, they can generate your codes for as long as they hold it — the same risk as with any device-bound credential. The damage stays contained: secrets live in the device's secure keychain behind biometrics, and there is no central code store, so only that person's own connections are affected. Recovery is straightforward: your contacts remove and re-establish the connection, which generates fresh secrets and permanently invalidates anything the attacker copied. For organisations, Beacon identities are tied to staff accounts and can be revoked centrally the moment a device is reported compromised.

Currently, no. Quantum computers that can break our encryption (X25519) don't exist yet and are estimated to be 10-20 years away. We're actively monitoring post-quantum cryptography standards and will upgrade before quantum computers become a threat. The three-word code generation itself is NOT vulnerable to quantum computers.

Yes. Protecting your family from scams shouldn't be a luxury. Our generous free tier covers most personal and family needs. We believe everyone deserves protection from impersonation fraud, regardless of their financial situation.

We're developing solutions for businesses and organizations with specific security needs. If you're interested, please contact us to discuss your requirements.

It doesn't require millions of connections — that's what Beacons are for. 1:1 connections are designed for people who already know each other. A bank registers a single organisation-level Beacon and assigns a Beacon identity to each outbound-calling employee. Any customer can then verify a Beacon code through a free web check — no app install, no account, no prior pairing. Rollout and pricing therefore scale with the bank's calling staff, not with its customer base. For full control over data residency and infrastructure, large institutions can also run the verification service as a self-hosted, federated server: their own node, their own data, fully interoperable with the wider network.