How HumanPass works in product reality.
This page explains the real verification loop: what runs in the browser, what flows to the backend, and where the current product should stay conservative in public claims.
Session starts in the product
A host product or dashboard flow creates a session, opens the hosted verify route, and prepares to receive the final result.
The browser runs live checks
The verification runtime initializes the selected profile, detector, and anti-spoof path, then guides the user through a prompt sequence.
Signals are evaluated and finalized
Prompt completion, liveness confidence, anti-spoof results, and policy signals are assembled before the session is finalized.
The app receives a usable result
The host surface can use the session result, token, or operator review flow according to the integration path being demoed.
Profile-aware prompts without pretending unsupported features exist.
This remains the proven baseline and safest demo path.
This uses a real alternate profile path with simple directional prompts, but it should still be presented as expanding unless separately rehearsed.
These are meaningful alternates with profile-specific policies, but they should remain clearly marked as experimental modes.