Security and data

• Connection credentials and channel configuration: AES-GCM at rest.
• User passwords: bcrypt at work factor 12. Never in plaintext, never reversible.
• Traffic: TLS between you and the service, and between the service and your database when the server offers it.
• Business workspaces can point at their own key (KMS) instead of using the service key.

• Password, passkey, or social sign-in.
• SAML SSO and SCIM provisioning on the Business plan.
• Roles with per-resource permissions; a workspace can adjust what each role reaches.
• Scoped per-workspace API keys for automation and for the command line. The scope narrows on top of the role of whoever created the key, and a key never grants platform-wide powers. Not available on the free plan.
• Sessions are visible and revocable one by one.

The audit log records who did what and when, and can be exported on a schedule to a workspace destination. Column policies let you mask sensitive fields in query results for roles that should not see them.

Masking matches on the source schema, table and column — not on the alias the query gave the field. On Trino, Presto and Athena the protocol does not report which table each result column came from, so a policy on those sources is stored and never applied. The screen says so at the moment you create the policy; to mask for real on those sources, do it in the view or table itself.

• Export: download your personal data in a machine-readable format, straight from the console.
• Deletion: the account enters a grace period before permanent removal, and you can cancel within it.
• Retention: run data follows the plan’s retention and is deleted by a routine, not on request.

Security issues: write to security@datarunner.app. We acknowledge receipt and keep you posted until the fix ships.