DiligenceVDR.ai
DiligenceVDR.ai declares 12 subprocessors in its trust center, which we last checked on Nov 20, 2026 (evidence). They include Google Cloud, Stripe and Cloudflare. No published changes since we first read it on Sep 29, 2026. A newer version, seen on Oct 30, 2026, is being checked before its changes are shown; the entries below are from the version before it.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors CSV of DiligenceVDR.ai's subprocessors · Atom feed of DiligenceVDR.ai's subprocessors DORA draft CSV of DiligenceVDR.ai's subprocessors as declared by DiligenceVDR.ai what's this? ·
12 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Better Stack | Centralized application log management — aggregates server logs from the API, workers, sidecar, and web for operational diagnostics and alerting; Log management | EU region (DPF + SCCs) | |
| Cloudflare R2 | Object storage; Stores encrypted customer document files uploaded to data rooms | EU or US (per project; DPF) | |
| ConvertAPI | Converts CAD drawings (.dwg/.dxf) and Apple Numbers spreadsheets to viewable PDFs when such files are uploaded. Routed to the regional endpoint matching the project's residency (EU projects → EU endpoint, US projects → US endpoint), so document bytes stay in-region; Document conversion / rendering (optional per project) | EU or US (per project; regional endpoints) | |
| DeepL | Document translation (optional per project); Translates uploaded Word/Excel/PowerPoint files when a project user requests translation — the primary engine for files above roughly 50,000 characters of text, and the quality fallback for smaller ones if Azure cannot complete them. DeepL never receives PDFs: its PDF pipeline would introduce a further document-conversion sub-processor, so PDFs stay with Google | EU (DeepL SE, Cologne, Germany — EU data centers) | |
| Google Cloud (Vertex AI & Cloud Translation) AI | AI / LLM provider (optional per project); Vertex AI: document text extraction, vector embeddings, semantic search, chat-based Q&A, and the terminal text fallback for any translation the document engines cannot complete. Cloud Translation: translation of PDF documents when a project user requests it, and failover for Word/Excel/PowerPoint files when the primary engine cannot complete them. Both only when AI features are enabled by the project administrator | EU or US (per project; DPF) | |
| Google Cloud SQL (PostgreSQL) | Hosts the PostgreSQL databases that store project metadata, permissions, and audit logs. Three instances: control plane (US-East, shared) for user accounts and project index; US data plane (US-East) for US projects' room data; EU data plane (EU-West, Netherlands) for EU projects' room data. EU projects' document metadata and audit logs never leave europe-west4.; Managed database | US-East and EU-West (DPF) | |
| Microsoft Azure AI Translator | Document translation (optional per project); Translates uploaded documents when a project user requests translation: data and text formats (CSV, TSV, TXT, HTML, Markdown, Outlook MSG, OpenDocument spreadsheets), images (JPEG, PNG, BMP, WebP — translated via OCR), and Word/Excel/PowerPoint files under roughly 50,000 characters of text, which is the majority of Office documents in a typical room. Larger Office files go to DeepL first. Azure never receives PDFs | EU or US (per project; West Europe / East US resources; DPF) | |
| Railway | Cloud hosting & compute; Hosts the Redis cache and Sidekiq job queue per region (US and EU). No customer document content is stored in Redis; only ephemeral job metadata and session keys.; Managed cache & queue; Runs the web frontend, API, background workers, and document-processing jobs that serve customer traffic. Two regional stacks: US (us-east4, Virginia) and EU (europe-west4, Netherlands). | US-East and EU-West (DPF) | |
| Resend | Delivers invitation, notification, and security emails to account holders; Transactional email | EU region (DPF) | |
| Sentry | Collects application error telemetry to diagnose service failures; Error monitoring | EU region (DPF) | |
| Stripe | Payments; Processes billing and subscription payments for paid plans | US (DPF) | |
| WorkOS | Authentication & identity; Sign-in, enterprise SSO/SAML, directory sync, and multi-factor authentication | US (SCCs) |
Web TechnologiesCSV of DiligenceVDR.ai's web technologies · Atom feed of DiligenceVDR.ai's web technologies
DiligenceVDR.ai's homepage made 20 requests to 2 domains, and 1 service controlled by another company.
1 third party by category: Analytics 1
Service statusCSV of DiligenceVDR.ai's status page incidents · Atom feed of DiligenceVDR.ai's status page incidents
90 days agotoday
No incidents reported since Sep 30, 2026
As DiligenceVDR.ai's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by DiligenceVDR.ai's subprocessorsCSV of incidents reported by vendors DiligenceVDR.ai lists · Atom feed of incidents reported by vendors DiligenceVDR.ai lists
27 reported incidents in the last 30 days, by 5 of the vendors DiligenceVDR.ai lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that DiligenceVDR.ai was involved.
And 2 more. All of them: CSV · Who is around them.
ChangesCSV of DiligenceVDR.ai's changes · Atom feed of DiligenceVDR.ai's changes
See the list as we read it on any date: Time machine
None since tracking began.