Notice the pressure
Urgency, secrecy, and demands for immediate payment are reasons to slow down, not reasons to skip a check.
Trust for high-pressure calls
A familiar voiceisn’t proof.Verify the relationship.
Handshake is an Android-first prototype for checking trusted relationships before pressure turns into a rushed decision. Pair people in advance, review the trust evidence available for a session, and pause whenever it cannot be confirmed.
Pair in advanceConfirm togetherPause when unverified
Prototype limits: Handshake does not detect cloned voices or access two-way remote audio from ordinary phone calls or third-party calling apps.
Android prototype
Try Handshake on your phone.
See how to get the latest test APK, install it on Android, and understand what this prototype currently supports.
Why it matters
Scams create urgency. Verification creates a pause.
A familiar voice and a familiar caller ID can both be misleading. The safest response to a high-pressure request is to stop and confirm it independently.
Verify out of band
If a session is not confirmed, contact the person using a number or channel you already know. Do not rely on the incoming call alone.
How it works
Set up trust before you need it.
Pairing happens in advance. Both people confirm the relationship, so a later check has a known starting point.
- 01
Add a trusted person
In the Handshake app, choose someone you know in real life — a parent, partner, sibling, or close friend.
- 02
Pair the phones
Tap “Show my QR” on one phone and “Scan a QR” on the other. The invitation is short-lived and single-use — and both of you confirm on your own phone. The trust is mutual.
- 03
Recognize the device
When one of you calls the other, the paired phone is recognized through the trust backend. The app shows one honest state: Trusted connection, Verify, or Risk detected.
Pairing happens in the Handshake app, on two phones side by side — not on this website.
A pairing is not a guarantee that every conversation is safe. A status is useful only when the current session is actually confirmed by the available trust evidence.
Trust states
One clear state. No false certainty.
The prototype separates a confirmed relationship from a session that still needs checking and from a risk signal. Each state is named and explained; color never carries the message by itself.
Interactive illustration of the app’s overlay. It shows how each state is presented — it is not a live call and not real-time detection.
Handshake overlayillustration
Trusted connection
Paired device · backend-verified session
The required trust evidence was confirmed — you have a reason to carry on.
IdentityPaired phone
Shown whenBoth phones confirmed + session verified
Selected state: Trusted connection. Both phones confirmed the relationship and the backend verified the session between them. The required trust evidence was confirmed — you have a reason to carry on.
These states describe the evidence Handshake has available—not whether a voice is genuine or whether the conversation itself is safe. When confirmation is missing, pause and verify independently.
In the prototype
A few useful tools. One clear purpose.
Start with the trusted relationship. Use the supporting tools when a message feels wrong or something has already happened.
Start here
Trusted pairing
Establish a relationship between two devices in advance, with confirmation from both people.
Explore pairingAdvisory
Pressure Check
Submit text you choose to share and review possible signs of urgency, secrecy, or payment pressure. It is not proof of fraud or identity.
Check a messageAfter an incident
The first hour
Follow a practical checklist if money or personal information may already have been shared.
Open the checklistKnow the limits
This release does not detect voice clones or analyze remote two-way audio from carrier calls, WhatsApp, or Google Meet. Call-state and overlay behavior varies by device, permission, and app. Text analysis can be wrong and must not be the only basis for a safety-critical decision.
FAQ
The important questions.
What the prototype can help with, what it cannot confirm, and what to do next.
No. Handshake does not classify voices or detect deepfakes. It explores trusted-device pairing and shows the trust state supported by the available evidence. If a request feels wrong, confirm it through a separate channel you already trust.
No. A trusted state means the configured relationship and session evidence were confirmed. It does not prove that every request is legitimate or that a device has not been compromised. Never send money or share secrets solely because a state looks reassuring.
No. The current release does not receive two-way remote audio from ordinary carrier calls or third-party calling apps such as WhatsApp and Google Meet. Call-state and overlay behavior may vary by device, permission, and app, and does not mean live speech analysis is running.
It reviews text you choose to submit and may flag tactics such as urgency, secrecy, or pressure to pay immediately. The result is advisory: it is not proof of fraud, speaker identity, or intent, and it can be wrong.
Pause the request. Hang up if needed and call the person back using a number you already know, or confirm with them through another trusted channel. If money or personal information may already have been shared, follow the first-hour checklist.
Want to inspect the implementation? Read the public source or report an issue.
Start with a trusted person
Make room for a second check.
Explore the pairing flow, see how the states are presented, and review the prototype’s limits before relying on it.