Skip to main content
This page is for the evaluator who wants the short answer first. Each answer links to the page with the full detail.

Product and architecture

TruU IDV is a workforce identity verification platform. Rather than a one-shot document-and-selfie API, it is an orchestration layer on top of your directory: factors are assembled into flows with fallback columns, and use cases decide which flow each group gets. The same engine covers help desk verification, self-service resets, onboarding, and enrollment. Document proofing is one factor within it. See Factors, Flows, and Use cases.
No. TruU IDV does not replace Entra ID or your authenticators. It answers a different question (“is the human we are interacting with right now the employee we think they are?”) at the moments where MFA alone is insufficient: help desk resets, MFA re-enrollment, and onboarding.
Microsoft Entra ID. See Microsoft Entra ID. Sample mode lets you explore the full product without connecting a directory.
Face, Proofing (document check), SMS, Email, Knowledge, and Badge (a badge or smart card tap on a reader, matched to a mapped directory attribute). See Factors.
No. Users complete verification on a short-lived web page in their own browser. Camera factors need browser camera access; a QR handoff moves the camera steps to the user’s phone. See What to expect during verification.

Directory and access

Read-only, through an app registration your organization creates and owns, with User.Read.All, Group.Read.All, and Organization.Read.All. TruU never writes to your directory and never sees passwords or tenant admin credentials. Revoke access at any time by removing the app registration. See Microsoft Entra ID.
No. Users and group memberships are looked up live at verification time. TruU caches attribute coverage statistics for schema discovery and a list of group names and IDs for the use case rule picker, nothing more.

Data and privacy

Face checks: camera frames are not retained after the result is recorded. Document checks: by default TruU keeps only the decision record (outcome, scores, extracted identity fields), in your own storage if you have connected one, otherwise in TruU managed storage. The verified selfie is kept as a face reference, and document images and selfie video are stored, only if you turn those settings on. See Data handling and How data moves.
Submitted codes are never stored. Phone numbers and email addresses are masked in stored display fields and consoles, and every audit event carries a flag indicating whether redaction was applied.
Retention of verification records and audit events is set by your agreement with TruU; see How data moves. For long-term retention, export the audit trail to your SIEM or data lake, where your own retention rules apply. See Send to your SIEM.
TruU holds SOC 2 Type II and ISO 27001. Reports and certificates are available under NDA from support. See Compliance.
The current list, with the processing each performs, is part of TruU’s DPA and is available from legalandprivacy@truu.ai. Persona, PingOne Verify, and Entrust are your own processors when you bring your own vendor. See Compliance.
Face and Proofing can be limited to specific populations or turned off, evidence can be kept in your own storage under your own lifecycle rules, and individual biometric data in TruU managed storage is deleted on request. See Biometric privacy controls.

Security and audit

Yes. Export the trail as CSV or JSON Lines from Activity or the API; the payload is OCSF-aligned JSON, so it maps into Splunk, Sentinel, Datadog, or a data lake without a proprietary parser. ServiceNow customers can also have lifecycle events pushed to their instance. Generic webhooks are not available. See Audit events and Send to your SIEM.
No. The trail is append-only: no API or console path updates or deletes events, and exports are replayable so downstream copies can be reconciled against the source.
Agents create and watch requests and see the timeline for the request they are handling, and the email and mobile on file when sending a link. They do not get workspace-wide Activity, export, configuration, or other directory attributes. See Permissions and roles.
No. A request that exhausts its attempts fails, and agents cannot change the outcome. Follow your escalation procedure, which may include a new request once the cause is fixed.
The agent sends a verification instead of judging the story. The link goes to the directory-known channel, the use case selects a flow strong enough for that group, and Face and Proofing with liveness resist the deepfake and social-engineering attacks that defeat knowledge questions. Every step lands in the audit trail. See Threat model.

Configuration and operations

Yes. Each use case’s rules send directory groups to different flows, checked top to bottom. Executives can require Face plus Proofing while general staff use Email plus Knowledge, in one workspace.
Flows have fallback columns. If a user has no phone on file or no reference photo, the flow offers the next column rather than failing. Fallback selection is recorded in the audit trail. See Flows.
Yes. TruU IDV ships an integrated provider (Didit) and also supports Persona, PingOne Verify, and Entrust with your own credentials. Your vendor’s check runs as the Proofing factor and TruU records the outcome and transaction reference. See Proofing.
Phone. Desktop webcams frequently fail face capture; the QR handoff on the verification page moves the camera steps to the phone and succeeds where the webcam does not. See Troubleshooting.
Yes. Sample mode lets you build and exercise flows against fictional users before connecting a directory, and every flow change is recorded in the audit trail.
No. Every connection is outbound from your side or from TruU. See Network requirements.
Still have questions? See Troubleshooting for operational issues, or contact support.