Confidential files deserve clear answers.

Deep Proof is used on data rooms, credit files and other confidential dossiers. This page explains where documents go and who controls each part of the system.

Where Deep Proof runs

Deep Proof Community Edition is open-source software. You can run it in infrastructure you control: your own servers, or your own account with a cloud provider. In that setup, uploaded documents and review results are stored in your environment.

For a commercial implementation, we agree the deployment with you during scoping, based on your privacy, residency and compliance requirements.

Which AI provider processes the text

To analyse documents, Deep Proof sends relevant text to a large language model. You choose that model:

• Your own AI subscription. Text is processed under the agreement you already have with that provider, including its data-retention and training terms.
• A custom deployment. A model deployment designed around your privacy requirements, agreed with you.

Check your provider's enterprise terms before connecting it. Your security team stays in control of that relationship.

Who can see what

• Administrators manage users and project types.
• Access is granted by project type, including restricted viewers for sensitive reviews.
• Review criteria and playbooks are editable and versioned, so you can see which standard a review followed.

Transparency

The platform source code is published under GPL-3.0 on GitHub. Your engineers can review how documents are ingested, stored and sent for analysis, and can verify a deployment against that code.

Questions from your security team

Send your questions or your security questionnaire to . We answer them as part of scoping, before any confidential document is shared.

Last updated: 12 October 2026