Security & Privacy

Zerodoc is built so the privacy promise is enforced by the architecture, not just stated in a policy. Documents are processed in memory and discarded the moment we respond — they are never written to disk and never stored.

Your document never touches a disk.

It’s processed in memory and gone before you finish reading the response — we can’t leak, lose, or be compelled to hand over what we never store. Zero-retention and EU processing are included on every plan, the free one included; they are never a paid upgrade.

Zero-retention by default

Every document you send to /v1/extract is held only in RAM for the duration of the request, then discarded. There is no document store, no archive, and no “retain for N hours” setting — by design, there is no code path that persists a document or its extracted content.

Each response includes an explicit "retention": { "stored": false } block as a machine-readable confirmation.

How processing works

  • Documents are received only by our stateless EU processing service.
  • Bytes live in an in-memory buffer that is overwritten on completion (success or error).
  • Uploads are size-capped and never spooled to a temporary file on disk.
  • OCR and field extraction run locally with deterministic rules — there is no third-party LLM in the path and your documents never traverse an external model.
  • Usage telemetry records metadata only (page counts, size, timing) — never content.

Data residency & jurisdiction

Document processing runs on infrastructure in the EU — on every plan, including the free tier, never as a paid add-on. Zerodoc is operated by an Isle of Man company — an EU-adequate jurisdiction with a strong privacy reputation — which acts as the data controller.

What we store (metadata only)

The only data we retain is what’s needed to run accounts and billing: your email address, a one-way hash of your API key (never the key itself), and usage metadata (page counts, timestamps). We never store your documents or the data extracted from them.

API keys & transport

  • API keys are shown once at creation and stored only as a SHA-256 hash.
  • All traffic is encrypted in transit (TLS).
  • Per-key rate limits and monthly quotas protect against abuse.

Sub-processors

We use a small set of vetted providers, none of which receive your documents:

  • Cloudflare — authentication, billing and usage metadata (EU-localized).
  • Stripe — subscription payments.
  • Resend — transactional (sign-in) emails.
  • Hetzner (EU) — the stateless document-processing service.

Compliance

Zerodoc is built to be GDPR-aligned, with a Data Processing Agreement available. A SOC 2 Type II programme is on our roadmap. See our Privacy Policy for the full detail.

Reporting a vulnerability

Found a security issue? Email security@zerodoc.io — we welcome responsible disclosure.