Security
Built for documents you would not paste into a chatbot.
EvidenceDock handles sensitive supplier and product documentation. The architecture assumes that and keeps every trust decision explicit.
How your data is handled.
EU data residency
Documents, extracted text, metadata and audit events are stored in EU-jurisdiction Cloudflare D1 and R2 (EEUR). No multi-region replication.
No model content logging
Model calls run through a named Cloudflare AI Gateway with content logging and response caching disabled. Prompts and document text are not kept as telemetry.
Human approval is structural
Model output starts as a proposal. Approved evidence and approved answers need an explicit reviewer decision, recorded in a content-minimizing audit trail.
Tenant isolation
Every data access is scoped to one organization, enforced in the data layer and covered by cross-tenant tests at every API boundary.
Untrusted documents stay data
Uploaded files are parsed in a bounded pipeline; their content is never treated as instructions, and extraction runs without tools or network access.
Bounded by design
File types, sizes, page and sheet counts, model budgets and change rates are capped per organization, with cost telemetry per run.
Subprocessors
The providers that process customer data on our behalf.
| Provider | Purpose |
|---|---|
| Cloudflare (EU jurisdiction) | Compute (Workers), EU D1 and R2 storage (EEUR), Workflows, AI Gateway, and email for one-time sign-in codes |
A GDPR Art. 28 data-processing addendum is provided to pilot customers before onboarding.
Report a security issue
Write to security@evidencedock.com. We acknowledge reports and coordinate disclosure.
Need the DPA before you start?
We send the data-processing addendum and the pilot agreement with the first reply.