Security & privacy

Encryption, provider isolation, and training controls

What is security & privacy?

Definition: Security and privacy in Dynamite Docs encompasses end-to-end TLS encryption, AES-256-GCM credential protection, zero-model-training policies, and on-premise local Ollama processing.

All traffic is encrypted in transit (TLS), stored documents and tables are encrypted at rest, and API keys are encrypted with AES-256-GCM before storage.

Your documents are never used to train foundation models. They are processed for your extraction only.

AI Settings exposes routing rules that lock extraction to the providers you trust: Sensitive Documents mode, no-training-only, free-models-only, and local-only.

Connecting your own provider means your data never touches a model you did not choose.

Key fact: Customer documents are strictly processed for extraction and never used to train foundation models, with BYOK keys protected by AES-256-GCM encryption.

How does Dynamite Docs safeguard document privacy and ensure zero model training?

All traffic is encrypted in transit (TLS), stored documents and tables are encrypted at rest, and API keys are encrypted with AES-256-GCM before storage.

Related workflows and guides

Open the document extraction app, browse document input and export integrations, or compare PE, storage, and API limits.

Loading Dynamite Docs… This page is taking longer than expected. Reload page.