Trust, But Verify: A Practical Anti-Deepfake Verification Guide

Deepfakes and AI voice cloning aren’t just "new tech threats." They’re trust threats. They target the moment a human decides: this looks right, this sounds right, Ill go ahead.

For families, that moment is usually a panicked call or message. For boards, it’s often a rare, high-stakes meeting where people haven’t seen each other in months.

The common pattern

• Believable message creates urgency.
• Move to voice or video where humans rely on "it sounds like them".
• Realism + pressure override skepticism.
• Irreversible action (send money, sign off a decision).

Why "spot the deepfake" isn't a family strategy

Relying on detection is unreliable. Calls are low-quality. People are distracted. A better rule is simpler:

• Trust in normal situations.
• Verify when the request is urgent, unusual, or involves money/access.

When to verify (parents + teens)

• "I lost my phone" / "I'm on a new number"
• "Don't tell anyone" / "It's a secret"
• "I need money right now"
• "I can't do video" / "My camera is broken"

VerifyHuman (Family): Built for the moments that matter

Establish trust once, then verify fast when it matters. Family version is free and limited to **5 trusted people**, keeping setup lightweight.

Three verification modes

1. QR verification: best when cameras are on.
2. One-time codes: best for audio-only or poor bandwidth.
3. Personal code word: last resort fallback.

The board problem

Boards are perfect targets because meetings are infrequent, people change, and NEDs sit on multiple boards. In that environment, "they look familiar" is not a security control.

VerifyHuman Pro for boards

• More identities: 25 or 100 trusted identities.
• Encrypted backup & restore: resilient across device changes.

A simple board ritual

• Start of meeting: everyone verifies (QR or one-time code).
• Before high-risk moments: re-verify before payments or approvals.