Security & Compliance

Dataira should be connected with the least access needed to answer questions.

Safety checklist

Use a database user that cannot write, migrate, or drop data.
Prefer Tunnel for private databases and local development.
Only activate tables that users are allowed to query.
Exclude sensitive columns where possible.
Create scoped MCP tokens instead of sharing broad credentials.
For embedded users, derive identity and customer attributes on your backend, assign a deny-by-default governed policy, and run the two-user isolation test.
Treat database-native RLS or scoped views as a second boundary. Dataira does not install those policies in a partner database during the current preview.

Dataira may show generated SQL and result rows. Do not paste secrets, credentials, or private customer data into chat prompts.