Does iDBQuery respect my own database login and its permissions?

iDBQuery's access to a source is never broader than the credentials you hand it, which gives you a familiar, database-level lever for control.

• Your credentials, your limits. Connect with a database user, and iDBQuery can only reach what that user can reach. If the account can't see a schema or a table, neither can iDBQuery.
• Least privilege by design. Best practice is a read-only account scoped to just the data you want analysed — a read replica, a reporting schema, a subset of tables — which caps iDBQuery's footprint at the source.
• Layered with app controls. On top of the database permissions, iDBQuery adds its own role-based access and row/column security, so you can further differentiate what individual users see within what the connection allows.

This two-layer model — your database's own permission system plus iDBQuery's — is reassuring when pointing an AI tool at real systems. It means you can reason about access using tools you already trust, and it complements deployment choices like VPC, Desktop, or air-gapped. Every query iDBQuery runs is visible and cited, so you can also confirm it only ever read within the boundaries its login permits.