Understand security and data residency for AI extraction

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.

Dynamite Docs does not use customer documents to train foundation models. Hosted and own-key requests are subject to the selected provider's handling terms.

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

• Read our formal data handling and retention guarantees in the Privacy Policy.
• Run model inference on your computer while the workspace and sign-in remain online with the Windows Ollama companion.
• Enforce sensitive document routing and no-training policies via the AI provider routing guide.