Legal
Subprocessors
These are the companies that process data on zendoc's behalf. We will post changes here before a new subprocessor starts processing customer data.
Convex — application database and backend functions
Every record the product stores: firm and staff accounts, client records, workflows, form submissions, message history, and audit events.
Cloudflare R2 — storage for uploaded files, generated PDFs and signed documents
The file bytes themselves — everything a firm's clients upload through the portal, and every PDF zendoc generates from it.
WorkOS — authentication for firm staff and Customer accounts
Staff and Customer names, email addresses and sign-in events. A Customer's verified email is checked against the firm's Client record before a protected Portal link opens data.
Anthropic — AI review of documents uploaded through the client portal
The contents of portal-uploaded documents, sent for classification and checking. API inputs are not used to train Anthropic's models, and files firm staff upload for internal use are not sent at all.
LlamaIndex (LlamaParse) — Document parsing and structured field extraction for uploaded-document review
Document bytes and converted text sent for parsing and structured field extraction, alongside the existing visual review. zendoc requests deletion of source files and parse jobs after processing; provider retention and regional terms apply.
Twilio — SMS delivery, where a firm has enabled it
Client phone numbers and the content of the messages sent to them.
Loops — transactional email delivery
Recipient email addresses and names, plus the variables a template renders — a workflow name, a step, a link.
Stripe — subscription billing for firms
The firm's billing contact and payment details. zendoc does not store card numbers, and no client data reaches Stripe.
PostHog — product analytics
Usage events from the marketing site and the app, and the account they belong to.
Sentry — error reporting
Stack traces and request context from failures, which can include the identifier of the record being worked on.
Vercel — application hosting
Serves the app and the marketing site, and sees the request metadata that reaches any web host — the caller's IP, the user agent, the URL.
Fly.io — the HTML-to-PDF rendering service
The document content being rendered, for the duration of the render.
Where processing happens
- zendoc is operated by Mavdotso LLC, a Delaware company, on United States infrastructure: the HTML-to-PDF service runs in Fly.io's US East region, product analytics on PostHog's US cloud, error reporting on Sentry's US ingest.
- Several subprocessors above operate globally on their own infrastructure. We do not pin customer data to a region and we do not offer a data-residency guarantee today — if your firm needs one, tell us before a pilot rather than after.
Changes to this list
- We will post a change on this page before a new subprocessor starts processing customer data.
- If you want that in writing rather than on a page, email security@zendoc.ai and we will notify your firm directly.
Reviewing zendoc before a pilot?
Our data processing addendum is at zendoc.ai/dpa and the mechanisms behind it at zendoc.ai/security. Anything neither answers goes to security@zendoc.ai.