Is my data shared with other iDBQuery customers?

Keeping your data separate from every other customer's is a baseline expectation, and iDBQuery is built to meet it in several ways.

• Isolated by account. Your connected sources and the answers derived from them are private to your organisation and never exposed to another customer.
• Not pooled for training. Your data is not used to train shared or public AI models, so it cannot leak into anyone else's results.
• Deploy for full separation. For the strongest guarantee, run iDBQuery in your own VPC, on your own hardware, or fully air-gapped — then your data physically never sits in shared infrastructure at all.
• Governed access inside your org. Role-based, row-level and column-level permissions control who even within your own company can see what.

This matters most for sensitive contexts — a bank's financials, a hospital's operations, a school's student records — where mixing data across tenants would be unacceptable. iDBQuery's honest position here is architectural rather than a certification claim: you choose a deployment model, up to a fully isolated one, and your data stays within that boundary. For example, a regulated organisation can run iDBQuery entirely inside its own environment so there is no shared surface to worry about. Your data works for you and only you.