Private document AI
Private document AI on your terms
Know where the file lives, which model sees it and what still depends on your settings.
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 exposes those choices so teams can match a workflow to the document instead of relying on a vague private mode claim.
Use browser-only files for a quick trial, encrypted cloud storage when documents must persist, Pro or Ultra 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 workflow. Free files stay browser-only. BYOK setup and execution require Pro or Ultra.
Choose the control before the upload
- Browser-only files: Anonymous and Free uploads do not become R2-backed library files.
- Encrypted cloud files: Hobby, Pro and Ultra can store supported files for later work.
- Provider-controlled inference: Pro and Ultra can connect encrypted provider keys.
- Local model inference: Hobby, Pro and Ultra can use the signed Ollama companion.
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.
- 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
- Residency policy: EU-only policy on Pro and Ultra
- Retention: Delete files or use published retention controls
- Audit evidence: Extraction and account events on eligible plans
From file to reviewed result
- 1. Classify the document. Decide whether the file contains personal, financial, legal or regulated information.
- 2. Choose storage. Keep the file browser-only or use paid cloud storage when cross-device persistence is required.
- 3. Set the model rule. Use hosted routing, a Pro or Ultra provider key, a no-training policy or local-only inference.
- 4. Review and delete. Check the extraction, export only what is needed and remove stored files under your retention policy.
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.
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.
| Layer | What it handles | What to verify |
|---|
| Browser | Upload handoff and local file state | Device access and browser storage |
| Dynamite Docs | Account, workspace, routing and optional cloud files | Plan, policy, deletion and retention |
| AI provider | Model inference for routed documents | Provider terms, region and retention |
| Local companion | Model inference through Ollama on your machine | Local host, model and hardware |
Privacy controls do not replace document review
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.
| Area | Dynamite Docs | Customer |
|---|
| Access | Authenticated workspace and capability gates | Manage users, devices and shared exports |
| Provider keys | AES-256-GCM encrypted storage on Pro and Ultra | Choose the provider account and rotate keys |
| Files | Browser-only option and encrypted paid storage | Classify, upload and delete the right documents |
| AI routing | Policy engine and eligible-provider filtering | Select policies and review provider terms |
| Results | Confidence signals and editable tables | Validate values before operational use |
Read the policy pages before a security review
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.
Dynamite Docs does not claim a certification until it has been issued. Security questionnaires should use the published controls and current contractual documents, not assumptions from a logo or marketing phrase.
Questions about private document ai
Is BYOK available on every plan?
No. Connecting and using external provider keys requires Pro or Ultra. Own-key processing is unlimited on those plans 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.
Choose the next document task
Try a private workflow or compare processing, storage and integration limits.