Private document AI

Extract documents with AI and control your processing route

Bring your own AI OCR or run local inference without third-party data retention.
By Dynamite Docs Editorial TeamPublished Aug 15, 2026Updated 2026-08-31
G25.0/5Capterra5.0/5Google5.0/5
Dynamite Docs logoDynamite Docs
Source → result
Processing settings: Choose the processing routeFile storage: Browser-only or encrypted R2-backed library. Provider choice: Hosted route, own key or local Ollama. Training policy: Sensitive and no-training-only routing rules. Illustrative example, not extracted customer data.CHOOSE A PROVIDER ACCOUNTPROCESSING SETTINGSProcessingsettingsProvider key•••• •••• ••••ModelChoose before runningDynamite DocsOllamaYour keyMistralYour keyCheck provider terms
File storage
Browser-only or encrypted R2-backed library
Provider choice
Hosted route, own key or local Ollama
Check provider terms before processing. Illustrative example.
Sections08
Reading time8 min
EvidenceProduct guide

Answer in 30 seconds

Bring your own AI OCR or run local inference without third-party data retention.

Document privacy is a chain of choices, not one toggle. File storage, model routing, provider retention, account data and deletion all have separate boundaries. Dynamite Docs lets teams bring their own AI provider keys or run zero data egress workflows without vendor lock-in.

Use browser-only files for a quick trial, encrypted cloud storage when documents must persist, own-key routing when the provider account should stay under your control, or the local Ollama companion when model inference should run on your computer.

Try a private workflowCompare Pro and Ultra

Free files stay browser-only. Every plan supports BYOK; BYOK on Pro and Ultra is unlimited.

Input register

Choose the control before the upload using Dynamite Docs

01

Browser-only files

Anonymous and Free uploads do not become R2-backed library files.

02

Encrypted cloud files

Hobby, Pro, and Ultra can store supported files for later work.

03

Provider-controlled inference

Every plan can connect encrypted provider keys.

04

Local model inference

Hobby, Pro, and Ultra can use the signed Ollama companion.

Extraction schema

Controls that affect sensitive documents

Each control answers a different question. Check the route as a whole before treating it as suitable for financial, identity or legal records.

Dynamite Docs logoDynamite Docs
Inside the output
Processing settings: Choose the processing routeFile storage: Browser-only or encrypted R2-backed library. Provider choice: Hosted route, own key or local Ollama. Training policy: Sensitive and no-training-only routing rules. Illustrative example, not extracted customer data.Source-linked field inspectorProcessing settingsBrowser-only or encrypted…Hosted route, own key or…Sensitive and…File storageBrowser-only or encryptedR2-backed libraryProvider choiceHosted route, own key orlocal OllamaTraining policySensitive andno-training-only routing…
File storage
Browser-only or encrypted R2-backed library
Provider choice
Hosted route, own key or local Ollama
Training policy
Sensitive and no-training-only routing rules
Check provider terms before processing. Illustrative example.
File storageBrowser-only or encrypted R2-backed library
Provider choiceHosted route, own key or local Ollama
Training policySensitive and no-training-only routing rules
Residency policyEU-only policy on Pro and Ultra
RetentionDelete files or use published retention controls
Audit evidenceExtraction and account events on eligible plans

Procedure

From file to reviewed result

Dynamite Docs logoDynamite Docs
The handoff
Processing settings: Choose the processing routeClassify the document. Choose storage. Set the model rule. Review and delete. 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. 01Classify the document
  2. 02Choose storage
  3. 03Set the model rule
  4. 04Review and delete
Check provider terms before processing. Illustrative example.
  1. 01

    Classify the document

    Decide whether the file contains personal, financial, legal or regulated information.

  2. 02

    Choose storage

    Keep the file browser-only or use paid cloud storage when cross-device persistence is required.

  3. 03

    Set the model rule

    Use hosted routing, your provider key, a no-training policy or local-only inference.

  4. 04

    Review and delete

    Check the extraction, export only what is needed and remove stored files under your retention policy.

Product evidence

Provider and policy controls are visible

AI Settings shows available providers, keys and routing rules. A policy can narrow eligible models, but the selected provider terms and your account configuration still matter.

The real AI configuration panel used to choose providers and routing rules.

Workflow Tour

8 steps

01 / Bring in files

Bring documents into one workspace.

Upload from your computer or choose files from Google Drive. Connected Dropbox and Slack workflows can bring in files too.

  • Google Drive logoGoogle Drive
  • Dropbox logoDropbox
  • Slack logoSlack
  • Local upload
Workspace preview01 / 08
Start with Import, then choose where your file comes from.
1 of 8
Worked Example: Document Input & Extracted Rows

Control is different at each layer

The table separates what runs in the browser, the Dynamite Docs service, an external provider account and the optional local companion.

Private Document Extraction with AI | Dynamite Docs: AI provider selectionCompare hosted, own-key, and local processing options.
Private Document Extraction with AI | Dynamite Docs: multi-model document extractionBrowse the available models across connected AI providers.
Private Document Extraction with AI | Dynamite Docs: bring your own AI key setupConnect a provider key and control the model used for extraction.
Private Document Extraction with AI | Dynamite Docs: private document AI controlsRestrict sensitive documents to approved processing routes.
LayerWhat it handlesWhat to verify
BrowserUpload handoff and local file stateDevice access and browser storage
Dynamite DocsAccount, workspace, routing and optional cloud filesPlan, policy, deletion and retention
AI providerModel inference for routed documentsProvider terms, region and retention
Local companionModel inference through Ollama on your machineLocal host, model and hardware

Review gate

Privacy controls do not replace document review

Common Failure States & Troubleshooting

A restrictive policy may leave no eligible provider. Local inference also fails when the companion, Ollama or selected model is unavailable.

Confidence

A private route can still return an uncertain value. Keep source review, validation and approval separate from the processing path.

Accuracy

Provider choice affects capability as well as policy. A model that meets the routing rule may still struggle with handwriting, dense tables or poor scans.

Failure state

A restrictive policy may leave no eligible provider. Local inference also fails when the companion, Ollama or selected model is unavailable.

Product boundary

The local companion moves model inference to the user's computer. It is not a self-hosted copy of the account, workspace, billing or token service.

Shared responsibility for private extraction

Dynamite Docs publishes the controls it operates. Customers still choose a plan, provider, policy, access model and retention schedule that fit their obligations.

AreaDynamite DocsCustomer
AccessAuthenticated workspace and capability gatesManage users, devices and shared exports
Provider keys[AES-256-GCM encrypted storage](/docs/document-security-and-data-residency) on every signed-in planChoose the provider account and rotate keys
FilesBrowser-only option and encrypted paid storageClassify, upload and delete the right documents
AI routingPolicy engine and eligible-provider filteringSelect policies and review provider terms
ResultsConfidence signals and editable tablesValidate values before operational use

Read the policy pages before a security review using Dynamite Docs

The Security page documents encryption and provider controls. The Data Processing Agreement covers customer data processing, and the retention policy explains how stored records and deletion work.

Choose storage, retention, and provider settings that match your document requirements. Use the published controls and contractual documents when completing your security review.

Choose the next document task using Dynamite Docs

Browse the full library of extraction guidesExplore all AI document extraction, PDF, and OCR tutorials.Review document extraction security controlsFinance team extraction review and approval.Data encryption and infrastructure security boundariesEncryption, model routing and operational boundaries.Review customer Data Processing AgreementCustomer data roles, subprocessors and contractual terms.Inspect audit trail retention and deletion policiesHow long records remain and how deletion works.Download the Windows companion for local loopbackRun 100% on-device document extraction with local Ollama models.Compare hosted, BYOK, and local provider pathsCompare hosted, own-key and local model paths.Step-by-step local Ollama OCR on WindowsRun model inference on the user's computer.Configure custom AI provider API keysConnect a key on any plan and select a model.Compare Pro and Ultra compliance capabilitiesReview BYOK, policy and storage entitlements.

Questions about private document ai

Is BYOK available on every plan?

Yes. Free and Hobby own-key processing uses monthly PE. Pro and Ultra BYOK is unlimited and does not use hosted PE.

Does local AI make the whole product self-hosted?

No. The companion performs model inference on your computer. Account, workspace and token issuance remain hosted services.

Can I prevent routing to training-permitted providers?

Yes. Sensitive Documents mode and no-training-only rules restrict eligible providers. Confirm the active rule and current provider terms before processing a sensitive file.

What is the difference between per-page OCR billing and BYOK unlimited extraction?

Metered OCR bills for provider usage under the vendor's pricing rules. BYOK routes model calls through your chosen provider account, while local Ollama runs inference on your machine. Pro and Ultra do not charge Dynamite Docs PE for BYOK runs, but the external provider may still bill its own usage.

Topic Cluster · In This Series

In This Series: AI Document Extraction Guides

Explore all 6 connected workflows in this series to master table extraction, invoice processing, data privacy boundaries, and local Ollama inference.

View guides hub
Core Workflow

Finance Document Extraction

Turn piles of mixed business paperwork into verified line items and tables with source-linked human check.

Explore guide
Multi-Page PDFs

PDF Data Extraction to Spreadsheets

Extract PDF tables and line items beside original pages, resolving wrapped rows and page-break continuations.

Explore guide
Tables & Forms

Complex PDF Forms & Nested Grids

Parse borderless tables, dense fillable forms, and multi-tier subtotal grids into normalized structured data.

Explore guide
Invoices to XLSX

Invoices to Audit-Ready Excel

Separate invoice headers from repeating item lines into a clean, audited Excel workbook with math checks.

Explore guide
Current guideData Security

Private Extraction & Zero Retention

Choose your processing path: zero-retention cloud models, client-isolated BYOK keys, or local loopback.

You are reading this workflow
On-Device AI

Local RTX GPU Inference with Ollama

Run vision models on your Windows PC via the companion app with zero external API calls for document bytes.

Explore guide

Looking for other workflows? AI document data extraction and OCR guides covers all supported formats and procedures.

Browse all 6 workflows in this cluster

Connected Accounting & Document Automation

Related Workflows

Local Document AI GuideOllamaSecurity & Compliance ControlsTrustData Retention PolicyComplianceDocument Extraction SoftwarePlatformAI Provider Integration PolicyBYOK
Browse all extraction guides

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.