Snapshot 239363
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Security at DiligenceVDR Sensitive documents. Considered protection. Protect the work behind your next deal with scoped access, encrypted content, and a clear record of who did what. Review the controls, their scope, and the evidence behind them. Explore the Trust Center Security FAQs For your security review Know what protects your room. Control access Identity, group permissions, and project isolation. Protect content Encryption, regional hosting, and AI choices. Review the evidence Documented controls, processing partners, and assurance status. Request a security overview Platform controls Protection across the room. From sign-in to document processing, each layer has a defined role. The Trust Center summarises the controls and explains how to request detailed scope and supporting materials. Encryption with project-level keys AES-256 protects stored data, with TLS 1.2+ on external connections. Sensitive content has an additional application encryption layer using project-specific keys wrapped by regional key-management keys. Encryption and key management Access scoped to the room Group permissions define what each reviewer can view, download, or manage. Database row-level security reinforces project isolation. SSO and multi-factor authentication help protect account access. Identity and access scope A choice of US or EU residency Choose Virginia or the Netherlands when creating a project. Project documents, permissions, and audit records stay in that region. Accounts, the project index, and billing use a shared US-hosted control plane. Infrastructure and regional scope AI under your control Disable AI for a project to keep document content from external AI providers. When enabled, in-app AI and external MCP have separate access controls, and document access follows the user’s permissions. AI processing and exceptions A record you can investigate Document integrity checks compare content against its recorded fingerprint. A tamper-evident audit trail records activity, while access and session signals help investigate potential misuse. Document integrity and audit records Documented processing partners Review the providers involved in operating the service, the data they process, and their hosting regions. Request the detailed register and processing scope through our Trust Center. Request subprocessor details Document controls Put protection into practice. Choose how documents are prepared, shared, and reviewed. Explore the feature guides for configuration, supported workflows, and limitations. Permissions and access preview Set reviewer access, preview a group’s view, and publish reviewed permission changes. Watermarking and protection Configure recipient-specific watermarks and control delivery of permitted document renditions. NDA and agreement workflows Require agreement acceptance before access and review acceptance records. Reviewed redaction Find sensitive information, review proposed redactions, and prepare sanitised copies. Assurance and transparency Evidence for your own assessment. Review published controls and processing terms, then discuss the requirements of your transaction with our team. Visit the Trust Center Readiness status, stated clearly SOC 2 Type II and ISO/IEC 27001 readiness programmes are active. They are not presented as completed attestations or certifications. Review assurance status ↗ Processing terms you can review Read our Data Processing Addendum alongside the sub-processor register and regional processing details. Read the DPA ↗ A deeper review under NDA Request the Security Overview for architecture, incident response, and business continuity details. Request security documentation ↗ Your questions, answered Security FAQs. A starting point for your vendor review, with links to the underlying documentation. Are uploads checked for malware? Uploads pass through malware scanning. Files that exceed scanner limits are marked unscanned and may still be delivered with preview renditions; text extraction and embeddings remain blocked for that status. Scanning does not guarantee that a file is harmless. Review upload screening and limits ↗ Does every room enforce MFA for external reviewers? DVDR Auth supports multi-factor authentication and enterprise SSO. Enforcement depends on the organisation’s sign-in or identity-provider policy; it is not a separate room-entry MFA requirement for every external reviewer. Review identity and access scope ↗ Where is our data stored? Project data is hosted in US (Virginia) or EU (Netherlands) infrastructure, selected when the project is created. The shared control plane for accounts, the project index, and billing is US-hosted. Some document translation and AI redaction processing has separate regional rules; review those exceptions when assessing residency requirements. Read residency and processing details ↗ How is our data encrypted? Stored data uses AES-256 encryption and external connections use TLS 1.2+. Sensitive document content also uses application-layer encryption with project-specific keys. Document, folder, and project names remain searchable and rely on database encryption, access controls, and row-level security rather than column-level encryption. Read the encryption scope ↗ Can we use a room without AI? Yes. AI is enabled by default. The project’s master AI setting can disable all AI functionality. In that mode, no document content is sent to an external AI provider; native document extraction and full-text search remain available. In-app AI and external MCP also have separate controls within AI-enabled projects. Review AI controls ↗ Is our content used to train AI models? Our in-app AI uses a managed AI service under provider terms that prohibit customer data from being used for model training. Provider details and terms are available on request through our Trust Center. Connecting an external MCP client can send requested content to that client’s AI provider; assess its terms separately. Review providers and AI processing ↗ Do you hold SOC 2 or ISO 27001 certification? SOC 2 Type II and ISO/IEC 27001 readiness work is not presented as completed attestations or certifications. Request the confidential package for recorded programme status, self-assessments, and supporting evidence. Request assurance details ↗ Where can we review sub-processors and data-processing terms? Request the confidential subprocessor register through the Trust Center for processing partners, their purposes, the data they access, and hosting regions. Our Data Processing Addendum sets out the contractual processing terms. Use both when assessing the service for your organisation. Request the subprocessor register ↗Read the DPA ↗ Can our security team request more detail? Yes. A Security Overview covering controls, architecture, incident response, business continuity and disaster recovery, and sub-processor attestations is available under NDA for prospective and current customers. Request the Security Overview ↗ How do we report a suspected vulnerability? Email [email protected] with a description, reproduction steps, and any proof of concept. We acknowledge reports within two business days. Read the disclosure policy below for testing scope and safe-harbour terms. Read the disclosure policy ↗ Preview group CorporateView FinancialsDownload Internal notesHidden See their view before they do. Buyer A can view Corporate and download Financials. Internal notes are hidden. Sample permissions only. Changing this selector does not change access or publish anything. On this page Vulnerability disclosure Last Updated: April 19, 2026 DiligenceVDR appreciates the security researchers who help keep our platform and our customers' data safe. This page describes how to report a vulnerability, what is in scope, and the safe harbor we offer for good-faith research. How to report Email [email protected] with a description of the issue, reproduction steps, and any proof-of-concept. We acknowledge reports within 2 business days. Scope In scope diligencevdr.ai and all subdomains (including app.diligencevdr.ai) The DiligenceVDR web application and public APIs Out of scope Third-party subprocessors (listed in our Trust Center) — please report those directly to the vendor Denial-of-service, volumetric, or rate-limit testing Social engineering of staff, customers, or vendors Physical attacks against offices or data centers Automated scanner output without a working proof-of-concept Missing security headers, SPF/DMARC nits, or cookie flags without demonstrated impact Safe harbor We will not pursue legal action against researchers who: Act in good faith and stay within the scope above Do not access, modify, or exfiltrate customer data beyond the minimum needed to demonstrate the issue Give us reasonable time to remediate before public disclosure (typically 90 days) Do not violate applicable law What we offer We publicly acknowledge researchers who report valid issues, with permission. We do not currently run a paid bug-bounty program.