Does my data leave my systems when I use iDBQuery?
It does not have to — iDBQuery can query your data in place and, in Desktop, VPC and air-gapped deployments, your data never leaves your environment. It reads only what is needed to answer a question, protected by encryption in transit and role-based access.
Whether your data leaves your systems depends on how you deploy iDBQuery — and it is built so that it does not have to.
- Query in place. iDBQuery reads only what a question requires, at query time, rather than bulk-copying your data somewhere else.
- Deploy where you want. Run it in the cloud, inside your own VPC, on your own hardware, or fully air-gapped with no external connectivity at all.
- Desktop keeps it local. The Desktop app processes data on your machine, so sensitive information stays put.
- Protected in transit. Where data does move between components, it is encrypted, and role-based access controls who can query what.
For the strictest environments — a bank, a government body, a hospital's operational data — air-gapped or on-prem deployment means your data physically never crosses your network boundary, and you can still ask questions and get cited answers. For teams comfortable with cloud, the same query-in-place model means iDBQuery is not accumulating copies of your database. iDBQuery leads with architecture here rather than a compliance badge: the guarantee is that you choose a deployment where data stays within your walls, and the product is designed to work fully in that mode.
Updated 2026-06-22