Skip to main content
2 of 6Next: Alchemer setup One idea holds the whole thing up: every password is tied to one unique human and works exactly once.
1

Each verified respondent receives a one-time passcode, created for their face alone and dropped onto their link. It fills itself in at your study’s gate.

One-time passcode
vyp_k2•••••••4qt
Filled in from their link. Used once, then dead.
2

Bots and returning humans get locked out. A duplicate face never earns a second passcode, and a spent passcode is dead forever.

Into the study
Blocked
Same face, second try
3

You only pay for real, first-time respondents. Blocked traffic never enters your data and never gets paid.

rsp_78421Verified92%
rsp_78422Blocked
rsp_78424Verified61%

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 study enforces the ticket with Alchemer’s own Login/Password action, set to individual one-time passwords that deactivate after use. Alchemer’s feature, Alchemer’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 study, on any device. One honest limit: the check proves who they are, not how carefully they answer. Keep your speeder and attention checks.

What we never touch

No photo is shared with you or with Alchemer, only a yes or no. Your study receives a verdict and a password, never a face, a name, or personal information.

Start here