Does my data leave my network when I use iDBQuery?

Where your data goes is determined by how you deploy iDBQuery, and every option is built to keep it under your control.

• Air-gapped or on-prem - nothing leaves your network; the application, the language model, and your data all stay inside your boundary.
• Your own VPC - iDBQuery runs in your cloud account and reaches sources over private networking, so data stays within your infrastructure.
• Cloud - data is queried in place and protected with encryption in transit and at rest; it is not sold, and it is not used to train an AI model.
• Query-in-place - across all options, iDBQuery runs SQL against your live sources instead of bulk-exporting them, so it moves answers, not wholesale copies of your database.

For example, a bank running iDBQuery air-gapped can let analysts ask questions of core banking data with full confidence that neither the data nor even the questions traverse the internet. This is the heart of iDBQuery's design philosophy: rather than asking you to trust a policy, the architecture lets you place data processing wherever your rules require. Answers remain cited to their exact source rows, so verification never depends on an external system either. If your requirement is that data physically cannot leave, choose the air-gapped or on-prem path. Contact us to match a deployment to your data-handling rules.