Data encryption, retention policies, and zero model-training guarantees

Encryption, provider isolation, and training controls

What security and model-routing controls does Dynamite Docs provide?

Dynamite Docs uses TLS for network traffic and AES-256-GCM for saved provider keys. You can choose hosted processing, your own provider account, or local Ollama inference based on the document policy.

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.

Dynamite Docs does not use customer documents to train models. The selected AI provider may receive document content, so review its retention and training policy before processing sensitive files.

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.