> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently asked questions

> Quick answers for IT administrators and security evaluators: what TruU IDV is, directory access, what is stored from face and document checks, certifications, SIEM export, agent visibility, proofing vendors, and testing.

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

> [accordion] What is TruU IDV, and how is it different from a proofing API?
>
> 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](https://docs.truu.ai/idv/factors/overview.md), [Flows](https://docs.truu.ai/idv/build/flows.md), and [Use cases](https://docs.truu.ai/idv/use-cases/overview.md).

> [accordion] Does TruU IDV replace our MFA or IdP?
>
> 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.

> [accordion] Which directories are supported?
>
> Microsoft Entra ID. See [Microsoft Entra ID](https://docs.truu.ai/idv/connect/directory/entra-id.md). Sample mode lets you explore the full product without connecting a directory.

> [accordion] Which factors are available?
>
> 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](https://docs.truu.ai/idv/factors/overview.md).

> [accordion] Do end users need to install an app?
>
> 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](https://docs.truu.ai/idv/end-users/what-to-expect.md).

## Directory and access

> [accordion] What access does TruU IDV have to our Entra ID tenant?
>
> 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](https://docs.truu.ai/idv/connect/directory/entra-id.md).

> [accordion] Does TruU copy our directory?
>
> 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.

> [accordion] How do verification links get delivered, and can an attacker redirect them?
>
> By default, links go to the email or phone already on the user's directory record, so an attacker would need control of the legitimate user's mailbox or phone. Agents can enter a different destination when needed; the guidance is to prefer the contact on file. See [Threat model](https://docs.truu.ai/idv/security/threat-model.md).

## Data and privacy

> [accordion] Does TruU store biometric data?
>
> 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](https://docs.truu.ai/idv/security/data-handling.md) and [How data moves](https://docs.truu.ai/idv/security/data-handling.md#how-data-moves).

> [accordion] What happens to one-time codes and other sensitive values?
>
> 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.

> [accordion] How long is data retained?
>
> Retention of verification records and audit events is set by your agreement with TruU; see [How data moves](https://docs.truu.ai/idv/security/data-handling.md#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](https://docs.truu.ai/idv/admin/activity.md#send-to-your-siem).

> [accordion] Is TruU SOC 2 or ISO 27001 certified?
>
> TruU holds SOC 2 Type II and ISO 27001. Reports and certificates are available under NDA from support. See [Compliance](https://docs.truu.ai/idv/security/compliance.md).

> [accordion] Who are the subprocessors?
>
> The current list, with the processing each performs, is part of TruU's DPA and is available from [legalandprivacy@truu.ai](mailto:legalandprivacy@truu.ai). Persona, PingOne Verify, and Entrust are your own processors when you bring your own vendor. See [Compliance](https://docs.truu.ai/idv/security/compliance.md).

> [accordion] We operate under biometric privacy laws such as BIPA. What should we do?
>
> 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](https://docs.truu.ai/idv/security/compliance.md#biometric-privacy-controls).

## Security and audit

> [accordion] Can we get IDV events into Splunk or our SIEM?
>
> 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](https://docs.truu.ai/idv/security/audit-events.md) and [Send to your SIEM](https://docs.truu.ai/idv/admin/activity.md#send-to-your-siem).

> [accordion] Can audit events be modified or deleted?
>
> 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.

> [accordion] What can help desk agents see?
>
> 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](https://docs.truu.ai/idv/admin/team-and-roles.md).

> [accordion] Can an agent override a failed verification?
>
> 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.

> [accordion] What stops an attacker who calls the help desk pretending to be an employee?
>
> 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](https://docs.truu.ai/idv/security/threat-model.md).

## Configuration and operations

> [accordion] Can different user populations get different verification requirements?
>
> 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.

> [accordion] What happens when a user cannot complete a factor?
>
> 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](https://docs.truu.ai/idv/build/flows.md).

> [accordion] Can we use our existing identity proofing vendor?
>
> 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](https://docs.truu.ai/idv/factors/proofing/overview.md).

> [accordion] Should we use SMS or email for codes and links?
>
> Check coverage first. SMS coverage is often far lower than email coverage because directory phone numbers are missing or not in E.164 format. Many organizations also restrict SMS. Prefer Email unless your phone data is clean.

> [accordion] Should users verify on a laptop or a phone?
>
> 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](https://docs.truu.ai/idv/resources/troubleshooting.md).

> [accordion] Can we test flows before rolling them out?
>
> 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.

> [accordion] Do we need to open anything on our firewall?
>
> No. Every connection is outbound from your side or from TruU. See [Network requirements](https://docs.truu.ai/idv/security/network.md).

Still have questions? See [Troubleshooting](https://docs.truu.ai/idv/resources/troubleshooting.md) for operational issues, or [contact support](https://docs.truu.ai/idv/resources/support.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.