A face has to be live before it's verified
Every verification starts with a liveness check — before any comparison against a registry photo runs. If the capture doesn't pass, the flow stops there.
What liveness detection catches
Printed photos
A static image held up to the camera is rejected at the liveness stage — it never reaches face comparison.
Screen replays
A photo or video played back on another screen is caught the same way, before any match attempt runs.
Low-quality captures
A capture that can't be confidently assessed is rejected rather than passed through and matched on weak data.
First in the pipeline, not an afterthought
Liveness runs before any face comparison — a failed check returns a liveness_failed outcome and the person is asked to recapture, rather than letting a bad capture reach the matching engine at all. It's enforced on every face verification call, with tighter rate limiting on face-verify endpoints as a brute-force control — see the Developers page.
How liveness captures are kept
Photographs and video frames captured during verification, including liveness-detection frames, are retained for a maximum of 90 days from the date of capture, then securely deleted unless needed for an active fraud investigation or legal proceeding. Full detail is in the Data Retention Policy and Security page.
See liveness detection in the full pipeline
Talk to us about where liveness fits in your onboarding or verification flow.