Privacy
Your documents stay on your machine.
What stays, what leaves
Data flows
| Data | Path |
|---|---|
| PDF bytes, extracted values, file names, template content | Never sent. Extraction runs inside the process on your computer. |
| Licence validation and aggregated usage counts | Sent to api.monaiq.com: the licence identifier, which features ran, how many units, and when. Aggregated before sending; sent periodically and when the process exits. |
| Template JSON | Sent only to a template store you configured (a Pro feature). The default local store makes no network call. |
The usage report contains
- The licence identifier
- Which features ran (for example execute, classify)
- How many units, per feature
- When
It never contains
- PDF content
- Extracted values
- File names
- Template content
- Anything typed into your AI assistant
The report lets Sidub apply your plan’s limits, bill usage-based charges where they apply, and troubleshoot. Section 2 of the Privacy Policy describes it.
Evidence
How the guarantee is enforced
There is no way to hand the engine a link
The engine reads a file that is already open on your machine. Every PDF-consuming method takes a Stream, never a URL or a remote handle, and the stream is opened and closed within the call.
There is no upload step
Reading, matching, extracting, transforming, and rendering all run inside the one process on your computer.
The licence check is blind to your documents
The licensing component is handed a feature name and a count, never a PDF, a record, or a template.
The shared template store cannot accept a PDF
The store host rejects any request body other than JSON with HTTP 415. A test named PrivacyInvariantTests fails the build if that changes.
Check it yourself
Check it on your own machine
Watch the connections
Run an extraction with your firewall log or a network monitor open. Docuoria contacts api.monaiq.com and, only if you configured one, your template store. No request carries PDF content.
Block the network (developers)
In an SDK host, turn licensing off with the setting below and cut the connection. Extraction completes and no connection is attempted.
DOCUORIA_ENFORCEMENT=DisabledLimits of the guarantee
Four cases the guarantee does not cover
Your AI assistant is a separate product
Claude Code, Copilot, Cursor, and the others have their own privacy terms. Whatever your assistant reads while doing a task, including text Docuoria extracts from a PDF while a method is being written, is handled under those terms, not these.
Your own host code
If you wrap the engine with a logger, telemetry sink, or storage handler in your own application, that code can transmit whatever you give it. The guarantee covers the library.
Templates can contain text from your documents
A template holds the patterns used to find values, and a pattern can include a label or token copied from a PDF. With a remote template store, those patterns cross the network. PDFs do not.
Downloading a PDF by URL
If your application fetches a PDF with the HTTP retrieval provider before extraction, the network sees that URL. The guarantee covers what happens once the engine has the bytes.
Your PDFs are read on your computer and nowhere else.
Vendor bills, client records, anything you would rather keep in-house.