> ## 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.

# Compliance

> TruU IDV certifications, encryption, privacy contacts, and how to request security documentation, reports, and the subprocessor list.

This page is for the person filling in a vendor security questionnaire. When you finish, you know what TruU is certified for, how to request reports and the subprocessor list, and who to contact for privacy requests.

Supporting detail lives in [Product security](https://docs.truu.ai/idv/security/overview.md), [Data handling](https://docs.truu.ai/idv/security/data-handling.md), [How data moves](https://docs.truu.ai/idv/security/data-handling.md#how-data-moves), and [Audit events](https://docs.truu.ai/idv/security/audit-events.md).

## Certifications

TruU is SOC 2 Type II and ISO 27001 certified. Reports are available under NDA from [support@truu.ai](mailto:support@truu.ai).

## Encryption

* **In transit:** all traffic between the verification page, the consoles, your systems, and the TruU IDV API runs over TLS. TruU's outbound calls to your directory, your ServiceNow instance, your storage, and vendors are TLS as well. See [Network requirements](https://docs.truu.ai/idv/security/network.md).
* **At rest:** stored verification assets and audit records are encrypted at rest. Credentials and secrets are held in a managed secrets service and never returned by any API.
* **Your key:** when you connect your own storage, you can additionally encrypt objects with your own AES key before they are written. See [Storage](https://docs.truu.ai/idv/connect/storage.md).

## Privacy

TruU IDV holds the minimum needed to show what happened. The precise list of what is stored, what is masked, and what is never stored, including what a document check leaves behind, is on [Data handling](https://docs.truu.ai/idv/security/data-handling.md). The short version:

* Submitted one-time codes are never stored.
* Camera frames from face checks are not retained after the result is recorded.
* By default, a document check leaves only its decision record. Face images and capture media are kept only if you turn them on in the Proofing factor settings.
* Phone numbers and email addresses are masked in stored display fields and consoles.
* All data is tenant-scoped.

### Privacy contacts

| Request | Contact |
| - | - |
| Privacy questions, DPA, legal | [legalandprivacy@truu.ai](mailto:legalandprivacy@truu.ai) |
| Deletion of biometric data (face references, proofing records) for a named individual | [biometricdeletionrequest@truu.ai](mailto:biometricdeletionrequest@truu.ai) |
| Security questionnaire, certifications | [support@truu.ai](mailto:support@truu.ai) |

### Legal documents

* [Privacy Statement](https://www.truu.ai/privacy-statement)
* [Biometric Use Policy](https://www.truu.ai/biometric-use)
* [GDPR Data Privacy Policy](https://www.truu.ai/gdpr-data-privacy-policy)
* [CCPA Notice](https://www.truu.ai/ccpa-notice)
* [Terms of Service](https://www.truu.ai/terms-of-service)

## Biometric privacy controls

TruU IDV is built to support biometric privacy and data protection programs, including Illinois BIPA and GDPR:

* Face and Proofing can be turned off entirely, or limited to specific groups with [use case rules](https://docs.truu.ai/idv/use-cases/overview.md).
* What a document check leaves behind is set in the Proofing factor settings.
* Evidence can be kept in your own storage under your own lifecycle rules. See [Storage](https://docs.truu.ai/idv/connect/storage.md).
* Biometric data for a named individual held in TruU managed storage is deleted on request to the contact above.

## Subprocessors

TruU's current subprocessor list, with the processing each performs, is part of our DPA and is available on request from [legalandprivacy@truu.ai](mailto:legalandprivacy@truu.ai). We notify customers of changes as described in the DPA.

### Your own processors

When the Proofing factor runs on a vendor you contract directly (Persona, PingOne Verify, or Entrust), that vendor is your processor, not a TruU subprocessor. TruU starts the session and reads the outcome; the vendor's media handling and retention follow your contract with them. See [Proofing](https://docs.truu.ai/idv/factors/proofing/overview.md).

## Evidence you can produce yourself

* **Who did what:** the append-only audit trail, exportable as CSV or JSON Lines. See [Audit events](https://docs.truu.ai/idv/security/audit-events.md).
* **What was configured when:** flow and use case change events with before and after diffs.
* **Who has access:** the team list under **Settings → Team** and the API client list under **Settings → API clients**, each change audited.
* **Where evidence lives:** the storage configuration under **Settings → Storage**.

## Related pages

> [card] [Product security](https://docs.truu.ai/idv/security/overview.md)
>
> The eight properties a reviewer should check.

> [card] [Data handling](https://docs.truu.ai/idv/security/data-handling.md)
>
> Stored, masked, and never stored.

> [card] [Data flow and custody](https://docs.truu.ai/idv/security/data-handling.md#how-data-moves)
>
> Diagram and custody table.

> [card] [Support](https://docs.truu.ai/idv/resources/support.md)
>
> How to reach the team.


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