Is iDBQuery safe for sensitive or confidential data?

For sensitive and confidential data, the trustworthy answer leads with how iDBQuery is built, not with a badge.

• Your data can stay entirely inside your walls. Deploy in the cloud, inside your own VPC, on a single on-premise server, or fully air-gapped. A Desktop app and Embedded SDK keep data local, so confidential records never have to cross your perimeter.
• Query-in-place, not copy-out. iDBQuery builds one live model over your sources and queries them where they live, so it isn't creating another permanent copy of your most sensitive data.
• Access is controlled. Role-based access control limits which sources and workspaces each person can reach, enforced on every query — not just hidden in the interface — and activity is captured in an audit log.
• Encryption protects data in transit (TLS) and the metadata and credentials iDBQuery stores at rest.
• No training on your data. Your data is used only to answer your questions; it never trains an AI model.

A candid note: iDBQuery does not claim a specific compliance certification. What it offers instead is architecture you can actually inspect and control — the air-gapped, on-premise and Desktop options mean the most cautious teams can analyse confidential data in plain language while it never leaves their infrastructure. And because every answer is cited to its exact source rows, you can always see precisely which sensitive records a figure touched. For regulated environments, that combination of containment, control and verifiability is usually what matters most.