Architecture and privacy
Where document bytes are processed, which runtime assets are loaded, and when network or support flows occur.
Normal viewing stays in the browser
During normal viewing, document bytes are passed to browser JavaScript, Workers, and WebAssembly from the host application. DocViewKit does not send the source document to a third-party conversion service and does not require a document-processing backend.
- The customer hosts the Viewer entry, Worker, Wasm, fonts, codecs, and optional format packs.
- Optional format packs load only when configured and needed by the current document.
- License verification exchanges signed license material, not document content.
- The official support flow excludes source bytes, file names, paths, text, screenshots, and hashes by default.
The host still owns its security boundary
The embedding application remains responsible for authentication, authorization, upload policy, content security policy, size limits, trusted asset hosting, telemetry choices, and incident response. Browser-local processing does not make untrusted documents harmless.