Subprocessors
Draft v1 · Aug 2026. Third parties Evidentum engages to process Customer Personal Data to provide the Services. Replace “intended / TBD” rows with live vendor names and regions before launch. Customer-configured integrations are not Evidentum subprocessors for data you choose to send.
Infrastructure (Cloud)
Locked preference: single VM (Hetzner or DigitalOcean) running app, workers, Postgres, and Redis. Postgres/Redis on that host are part of our environment—not separate SaaS DB vendors—unless we later add a managed database (then listed here).
| Provider | Status | Purpose | Location | Data |
|---|---|---|---|---|
| Hetzner or DigitalOcean (Cloud host) | Intended → Active at go-live | API, web, workers, Postgres, Redis | Region chosen at provision (confirm) | Hosted Customer Data (accounts, events, cases, media on disk) |
| DNS / TLS edge (Cloudflare or host + Caddy/Let’s Encrypt) | Intended | DNS, certificates, optional proxy | Per provider | Connection metadata (IP/TLS); not investigation content |
Storage
| Provider | Status | Purpose | Location | Data |
|---|---|---|---|---|
| Local disk on Cloud host | Active (default) | Clips, thumbnails, evidence, exports | Same as host | Camera-derived media / evidence |
| S3-compatible object storage | Optional / later | Durable media when needed | Bucket region | Same media classes |
Payments, AI, email
| Provider | Status | Purpose | Location | Data |
|---|---|---|---|---|
| Stripe, Inc. | Active when billing on | Checkout, invoices, Customer Portal, webhooks | Stripe regions | Billing identifiers & status (cards stored by Stripe) |
| OpenAI, L.L.C. | Active when AI key configured | Narratives, Ask Evidentum, text AI assists | Per OpenAI terms | Text prompts / investigative metadata — not raw video in current paths |
| Transactional email (Resend / Postmark / SES — TBD) | Intended | Invites, password reset, notices | Per provider | Email addresses, transactional message content |
Enabling AI Features instructs us to send text prompts and investigative metadata to OpenAI (when configured)—not raw video files in current product paths. See DPA and Privacy.
Optional monitoring
| Provider | Status | Purpose | Location | Data |
|---|---|---|---|---|
| Uptime monitor (TBD) | Optional | External health checks | Per provider | Uptime results; generally no Customer Content |
| Error tracking e.g. Sentry (TBD) | Optional | Diagnostics | Per provider | Stack traces / request metadata (minimize Customer Content) |
Not Evidentum subprocessors
- Your cameras, NVR, and network
- Integrations you install (Slack, Teams, Jira, webhooks, access control, etc.)
- Parties you export to (insurers, police, counsel) or that compel disclosure by law
- Your SSO identity provider, when you configure SSO
- End-user browsers/devices; mobile OS / push platforms when mobile is used
Our commitments
- Use subprocessors only as needed to run the Services
- Flow down materially protective data-protection terms
- Remain responsible to you for their performance of those obligations
- Keep this page accurate as vendors change
Changes
Material updates are published here. Enterprise Customers under a DPA may receive advance notice and an objection window as specified in that DPA. Questions: privacy@evidentum.ai · security@evidentum.ai · Contact Sales.
Full working draft: docs/legal/07-subprocessors.md
Related: Terms · Privacy · AUP · DPA · Subprocessors · Refunds · Cookies · Security · AI Disclaimer · Support · API Terms · SLA · Enterprise · Beta