Security one-pager

A condensed reference for security review. The full treatment is on the security page; this is the file-and-forward version.

Trust boundaries by deployment mode

On-prem (Mode 1) — runs on your own hardware and needs no internet once installed. As installed, with the standard on-prem engines, DocMark sends nothing off the box: no model call, no DocMark telemetry. You author; DocMark renders and verifies locally (the deck gate is on by default). An operator can enable AI engines; a job that uses one sends content to the model provider and is never zero-egress (see point 3 of the security page).
Client cloud (Mode 2) — runs in your own cloud tenant.
DocMark cloud (Mode 3) — runs on DocMark’s managed Azure. DocMark processes content, but user identity and PII never reach the rendering plane.

On-prem zero-egress = as installed, DocMark sends nothing off the box. The render path needs no network, so the box can run fully air-gapped once installed; that isolation is your network’s control. The render step itself also runs in a container with no network access. The render sandbox is on by default, and the box will not start without it; an operator can still turn it off, but that takes a second, deliberate override, so ask for confirmation at handover that it is not set.
DocMark-cloud zero-egress = no PII to the execution plane. The control plane holds identity; the worker that renders never receives the user’s email or principal — only the job content it must render.
Client cloud is deliberately not called zero-egress — content reaches your chosen LLM, under your account and your contract. Its AI-authored watched-folder decks are labelled contract-protected-api.

Synthetic presenter media (a presenter likeness or a cloned voice) — not offered in any deployment mode today. If it is offered, it will run only with a consent record on file for the person depicted (DocMark checks that the record exists; it cannot verify the consent itself), and every such video will carry a visible disclosure that it is synthetic. No plan or entitlement removes these conditions. (The narration in DocMark videos offered today uses a generic synthetic voice, with no human likeness and no voice cloning.)

The verification gate withholds. A deliverable that fails the gate is not delivered — it is withheld with findings. What the gate checks for each format, and where it does not apply, is set out in point 7 of the security page: on a self-managed install the deck gate is on by default and turning it off takes a second, deliberate override as well (named at handover), a partly blank video can ship, and the optional agentic engine’s own visual review is not verified by DocMark — which is why its decks are gated like every other engine’s.
Pixels come from deterministic code. Rendering is tested code; the model authors content. The exception is the optional agentic engine (self-managed deployments only, off unless an operator turns it on), where an AI agent writes and runs each deck’s build script with shell access.
No PII to the execution plane (DocMark cloud) is enforced by construction, not by policy.
On-prem needs no internet with the standard engines. The render path makes no network calls, and by default the render step runs in a container with no network access; each deck’s egress record says whether it did. A public bind is refused unless the sandbox is explicitly configured. An AI engine, if an operator enables one, calls its model provider.
Decks sent in through the watched folder are labelled with their egress class, written by the pipeline itself. Web-app, /v1 API and MCP jobs are not labelled.

Last updated: 10 October 2026 (client cloud: the trust-boundary and egress lines narrowed).