InsightQueries run on your machine
The desktop client connects straight to your database. The cloud never holds a connection to your data — block the engine's domain and you'll see every prompt fail, proving generation is the only thing that's remote.
Security & privacy
Your data never leaves.
Insight O' Mate is local-first by design. The NLP engine sees your prompt and your field names — never your rows, your connection string, or your credentials. Here's exactly how, and how to verify it yourself.
What leaves your machine
Your prompt
The plain-English question you type, so the engine can work out what you're asking for.
Field & collection names
Names only — e.g. “orders”, “createdAt” — used to route the query. Never the values inside them.
What never leaves
Your documents & row values
Not one field value ever leaves. The engine produces a query; it never sees a result.
Your connection string
Stored in your OS keychain and used only by the desktop app to reach your database directly.
Your credentials & API key contents
The API key is only ever sent to our stateless engine to authenticate you, and is never forwarded to any other service.
How it's built
Keychain-backed credentials
Connection strings live in the OS keychain — macOS Keychain, Windows Credential Vault, or libsecret on Linux — with an AES-256-GCM encrypted-file fallback. Never written to disk in plaintext.
Built so writes can't slip through
We recommend a read-only database role, and the app is designed around find/aggregate reads. An accidental $merge or $out from a misread prompt can't mutate your data.
Nothing is stored or trained on
The hosted NLP engine is stateless — it reads a prompt, returns an analysis, and forgets both. No prompt database, no input logging, no training feedback loop on your data.
Don't trust us — verify
The claim above is checkable in three ways, without taking our word for it.
01
Inspect the traffic
Run the app with IOM_LOG_ENGINE_REQUESTS=1 and every outbound request is written to ~/.insight-o-mate/engine.log as plain JSON. Diff it against the contract.
02
Cut the cord
Firewall the engine domain. Every prompt fails — proof that query generation is the only thing that ever leaves, and nothing is smuggled elsewhere.
Compliance
GDPR
The NLP engine acts as a processor under Art. 28. A Data Processing Agreement is available with Pro and Team plans — reply to your purchase confirmation to receive the countersigned copy.
HIPAA / SOC 2
A self-hosted engine for your own VPC is currently in work and marked on the roadmap. Once released, it will support environments that need a BAA or stricter audit posture.