Skip to main content
HumanCheck

Prove any user is a unique human,in about 3 seconds.

Passive signals score every visit. When they flag risk, an anonymous selfie confirms a live, unique person, with no ID to upload.

The problem

What a basic selfie check misses

  • Printed photo
    Passed a basic check

    Photos and masks pass as people

    A static selfie or a basic liveness check can be fooled by a printed photo, a video replay or a mask held up to the camera.

  • 21acct_0221Banned
    09acct_0309Looks new
    02acct_0402Looks new

    The same person comes back as someone new

    A banned or already verified person signs up again with a new email and device, and looks brand new to your systems.

  • ID uploadAbandoned
    Dropped off

    ID uploads slow everyone down

    A document upload adds minutes, personal data you don't need, and a step where good users drop off.

How it works

One check, most people never see

  1. 01

    Passive signals run first

    Device, network and behavior signals score every visit in the background and build a history, so most people never see a check at all.

  2. 02

    An anonymous HumanCheck for the risky ones

    When the signals flag risk, a selfie of about 3 seconds, the same motion as Face ID on your phone, confirms a live, unique human is at the camera, with no ID to upload.

  3. 03

    One check, two anonymous answers

    The same selfie anonymously confirms a real, live person, and whether you've seen their face before, so someone you've already blocked can't just sign up again.

Settings

Powerful verification configurations

Every check carries its own settings, so a strict payout gate and a light checkout run side by side in one workspace.

Once per lifetime

A permanent decision, like opening an account. One person, one pass, forever.

Once per period

Something recurring, like a weekly payout. One pass, then a wait before the next.

A few per period

A set number of passes inside the window you choose, then nothing until it resets.

Unlimited

A checkout or a login, where you only need a live human present.

Verification limits

Control how many times one person may pass. It counts successful passes, not attempts.

Age gates

Set a minimum estimated age from the face scan, with no document to upload. Thresholds at 13, 16, 18 or 21 and over, or one you set.

Returns an estimated range, not a precise year. Not legally sufficient for regulated products like alcohol, gambling or firearms: pair it with proper ID verification for those.

Known deviceReturningSkipped

Skip on known devices

Somebody returning inside a window you set passes without scanning again. It still counts as a verification: skipping saves them friction, not you a check.

Tor exit

Location aware

Gate on where a connection surfaced: a VPN, a datacenter, a Tor exit. Worth reading as where the traffic came out, not where the person is.

Let's talk trust

Start with a free pilot: see what the check catches on your own users, with no dev work to begin.

With tools like VerifyYou, AI becomes a force for good. It helps prevent AI-driven fraud and can be done with much lower friction than what we built over the years.
Wes MichaelFounder of Rare Patient Voice

Built by humans from

  • Quora
  • Pinterest
  • Square
  • Reddit
  • Gusto
  • Cohere Health
  • Google
  • Accenture
Security

Privacy and security in every decision

We keep a face code, not the photo, and hold it under SOC 2 Type II and ISO 27001:2022 compliant controls.

  • No images stored. VerifyYou does not store images.

  • No ID or documents. HumanCheck anonymously confirms there is a real, live, unique person, with no name or ID.

  • A face code, not a photo. We treat it as sensitive biometric data.

  • AICPA SOC 2SOC 2 Type II
  • Intercert ISO/IEC 27001 certificationISO 27001:2022
  • iBetaISO/IEC 30107-3 PAD Level 1 & 2
  • GDPRGDPR compliant

Common questions

What does the selfie actually check?

One selfie of about 3 seconds answers two questions: is a live person there, not a photo, a mask or a replay, and have we seen this face before in your user base. The same selfie can also return an estimated age range, which is an estimate, not legal proof of age.

Why is it anonymous?

An anonymous HumanCheck never asks for a name or an ID. It confirms a live, unique human is behind the account, so you get the fraud answer without collecting more personal data than you need.

What happens to someone who fails the check?

You choose in Workflows. On a duplicate, Block (the default) turns them away, and Allow and flag lets them through and tells your team. Most good users never see the check, since it only runs when passive signals flag risk.

Can a printed photo or a mask pass the check?

The liveness check is built to catch a printed photo, a screen replay or a mask held up to the camera, and it's iBeta-tested against presentation attacks.

What counts as a duplicate?

A duplicate is the same face already on record inside your own user base, whatever new email, phone or device it arrives with. You choose what happens on a match: turn them away, or let them through and flag it for your team.

How much work is it to add?

It's two API calls: one to start the check and one to read the result.

Do we have to replace our KYC or bot tools?

No. It sits on top of your stack, so you keep your KYC and bot tools.

What does it cost?

It's 50 to 100 times cheaper than KYC. You pay per check, and nobody uploads an ID document.

Ready to get started?

VerifyYou scales trust: passive signals on every session, a face check only when risk calls for it.

The VerifyYou dashboard on a laptop, showing verification volume and threat signalsAn anonymous HumanCheck running on a phone

We use cookies. Privacy