Skip to content
Dynamite Docs logoDynamite Docs
The handoff
Processing settings: Set your document policyStorage location. Data residency. Provider training policy. Illustrative example, not extracted customer data.CHOOSE HOW TO PROCESS THE FILEHosted AIUse the hosted allowanceYour provider keyChoose a provider and modelLocal OllamaOn an eligible planSamesource-linked…Allowances and availability depend on your plan and provider.
  1. 01Storage location
  2. 02Data residency
  3. 03Provider training policy
Choose storage and processing deliberately. Illustrative example.
09Updated

Choose storage and model processing separately. Review the selected provider and your active routing rules before processing sensitive documents.

Encryption

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

Training and provider terms

  • Dynamite Docs does not use customer documents to train foundation models. Hosted and own-key requests are also subject to the selected provider's handling terms. Check the provider and routing policy before processing sensitive documents.
  • Local Ollama inference runs on your computer; account and workspace features remain hosted.
  • Provider keys never leave the server and are never sent to the browser

For stricter needs, AI Settings exposes routing rules that lock extraction to the providers you trust:

  • Sensitive Documents mode: only use models that do not train on your data. Gemini's free tier is excluded by default.
  • No-training only: block any model that may retain or train on submitted content (Gemini, OpenRouter).
  • Free models only: spend only your connected free keys, never host or paid quota.
  • Local only: route every extraction through the Windows companion (127.0.0.1:8756) to Ollama instead of an external AI provider. See our Local Document AI guide for setup details.
BYOK = data sovereignty: connecting your own provider means your data never touches a model you did not choose. You pick the provider, you pay the provider directly.

Related workflows & guides

Dynamite Docs logoDynamite Docs
The review
Processing settings: Set your document policyAll 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.. Illustrative example, not extracted customer data.PROCESSING SETTINGSProcessingsettingsProvider key•••• •••• ••••ModelChoose before runningReview before exportStorage locationAll traffic isencrypted in transit…Compare with the source on the leftAccept after reviewChoose storage and processingdeliberately.Original stays…
Storage location
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.
Data residency
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.
Provider training policy
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.
Choose storage and processing deliberately. Illustrative example.
Security & privacy document extraction guide: AI provider selectionCompare hosted, own-key, and local processing options.
Security & privacy document extraction guide: multi-model document extractionBrowse the available models across connected AI providers.
Security & privacy document extraction guide: bring your own AI key setupConnect a provider key and control the model used for extraction.
Security & privacy document extraction guide: private document AI controlsRestrict sensitive documents to approved processing routes.
Previous chapterAI providers & keysAll chaptersFull documentationNext chapterPlans & limits

Can we save optional cookies?

Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.