Where is my data stored and who can access it?
Where your data lives depends on your deployment: in managed cloud it stays in your isolated workspace, in private VPC or air-gapped setups it never leaves your environment, and on the Desktop app it stays on your device. iDBQuery queries sources in place rather than copying them, and only your authorized users can access them.
iDBQuery is built around the principle that you should control where your data physically resides.
- Queried in place, not copied. iDBQuery reads your sources to answer questions and assembles one live model on the fly. It does not bulk-export your databases into a separate warehouse, so there is no second copy of your data to worry about.
- Location follows deployment. On managed cloud, your data is isolated to your workspace. In a private VPC or air-gapped deployment it stays entirely within your own network. On the Desktop app it stays on the local machine.
- Access is yours to govern. Only the authorized users in your workspace can reach your connected sources. Your own database credentials and network controls remain in force.
This design is why iDBQuery fits teams with strict data-handling rules: the more sensitive your data, the more locally you can keep it, without giving up plain-language analysis or cited answers. When OCR or document ingest is used, the extracted content stays within the same environment as the rest of your workspace.
If you have specific requirements about storage location or access boundaries, we can match a deployment to them. Get in touch to discuss your constraints.
Updated 2026-06-22