What it is for
Private mode is for Facial age estimation workspaces only. It also covers the ID document a person adds when the selfie cannot confirm their age. Age verification by ID document and Identity (KYC) always run in Protected mode. Moving a private workspace to the ID document method switches it back to Protected, with both options below on. Moving it back to facial age estimation does not restore Private.What is always true in Private
No face template is kept. So:- the face blocklist check does not run;
- duplicate detection does not run;
- a face from a private verification cannot be blocked.
The two options
Both are on by default.Where to set it
- In the console: when you create or edit the workspace.
- Through the MCP server:
create-workspaceandupdate-workspacetakeprivacy_mode,private_discard_mediaandprivate_skip_device_signals; the values they accept are in the MCP tools reference. Administrators and developers can use them. On a live workspace the change is previewed first and applied only when you confirm. Private is refused on a workspace that is not facial age estimation, and the two options are ignored on a Protected workspace. - Not through the REST API.
What your integration and your console see
Always in Private
duplicate_check.checkedisfalseon the verification.POST /v1/verifications/{verification}/blocked-faceanswers422 VALIDATION_ERROR, with the reason inerror.message. An account without the face blocklist gets403 FACE_BLOCKLIST_DISABLEDfirst.
When media is deleted (first option on)
GET /v1/verifications/{verification}/media/{media}answers404 MEDIA_NOT_FOUND. InGET /v1/verifications/{verification}/document, each media item keeps itsidandtypeand hasurl: null. This holds at every status from creation, not only after the decision, and also in a test workspace while the verification waits for its test outcome.- When the person added an ID document, its fields are deleted a few seconds after the final status. Save them from the decision webhook. Automatic retries of that webhook still carry them; a webhook subscription gets them only with
include_document_data: true. After that,GET /v1/verifications/{verification}/documentand a webhook retried or resent by hand return the fields asnull, withtypeandissuing_countrykept. - The verification’s
erasurefield staysnull, because this is not an erasure. - The console and the MCP server show no media for the verification.
When device data is not collected (second option on)
- The webhook has no
fingerprint_signals. - The console and the MCP server show no technical information for the verification.