Skip to main content

One password per person

Anything you hand out on a link can be forwarded, shared, and taken twice. A survey, a giveaway, a beta invite, an event registration, a claim form. The link cannot tell a real first-timer from the same person on a second browser. It bites hardest in market research and academic panels. Bots, duplicate respondents, professional survey-takers and survey farms clear a simple screener and land in your data, so you pay for completes that are not real and clean it up afterward. HumanCheck moves the check upstream, before your first question, so only a real, unique, present human ever reaches it. One idea holds the whole thing up: every password is tied to one unique human and works exactly once.
1

Each verified person receives a one-time passcode, created for their face alone and dropped onto their link. It fills itself in when they arrive.

One-time passcode
vyp_k2•••••••4qt
Filled in from their link. Works exactly once.
2

A bot never earns a passcode, because it cannot pass a live face check. The same face never earns a second one. And each passcode works exactly once, so a forwarded or shared one is already spent.

Through
Blocked
Same face, second try
3

Only real, first-time people get through. Everyone else stops at the check, so there is nothing to clean up afterwards.

rsp_78421Verified
rsp_78422Blocked
rsp_78424Verified

Why the gate holds

Each password is a claim ticket. We only hand one to a person who just proved, on camera, that they are live and unique. Your survey platform enforces the ticket with its own built-in gate: Alchemer’s Login/Password action, or Qualtrics’ Authenticator, set to individual one-time passwords that deactivate after use. Your platform’s feature, your platform’s wording. So every cheap trick fails: a shared link carries a spent password, a guessed password does not exist, a bot never earns one, and the same face can never get a second one for the same thing, on any device. One honest limit: the check proves a real, unique human, and says nothing about how carefully they answer. Keep your speeder and attention checks.

What we never touch

No photo is shared with you or with the platform on the other end, only a yes or no. You receive a verdict and a password, never a face, a name, or personal information.

What it costs

Pricing depends on your volume and your use case. Tell us what you are running and we will give you a number. Blocked traffic never enters your data.

Set it up on your platform

Four platforms have a full step-by-step guide. Pick yours and follow it, no code on any of them.

Qualtrics setup

Five steps, no code.

Alchemer setup

Five steps, no code.

Google Forms setup

Five steps, with a script for the response sheet.

Tally setup

Five steps, with a webhook.

Works on more than these four

Nothing about the mechanism is specific to one platform. The check and the single-use credential are always the same; only the platform’s own lock changes shape to fit. So the gate works anywhere you can hand each respondent a link or password that works exactly once. The strength of the lock varies a little by platform. Qualtrics and Alchemer enforce it server-side before a single question shows, which is why those two came first, but the hosted wrapper plus uniqueness protect every platform. We are actively building out more guides. Not sure about your platform? At the top of this page, open the Copy page menu and pick Open in Claude or Open in ChatGPT. It carries this page across, including the table above, so you can ask whether HumanCheck works with your tool and get an answer grounded in how the gate actually works. Curious what the respondent goes through? See what your users see.