Security

Available today

Role-based access control. Every workspace member has a role — workspace admin, member, or viewer — governing what they can do across connections, datasets, saved queries, storage, and workspace settings. A separate system admin role exists for cross-workspace administration. See Roles & Permissions for the full breakdown.

Encrypted connection credentials. PostgreSQL connection credentials are encrypted at rest (AES-256-CBC) before being stored.

Local authentication. Sessions use JWT access tokens with an httpOnly refresh-token cookie. Authentication is local email and password today.

Data residency for live connections. When a workflow queries a live PostgreSQL connection, DataQloo does not copy your rows — it queries your database directly. Data is only persisted into DataQloo's own storage when you explicitly save a workflow's results (via an Output node) or upload a file through the Import Wizard.

Not built yet

Two things most enterprise buyers ask about are not available today, and we're not going to imply otherwise:

• SSO and LDAP/Active Directory group sync — not implemented. Planned under Admin → User Groups, which is itself marked "Coming Soon" in the product.
• Activity & Audit Log — not implemented. No activity history is recorded today. Planned scope includes a real-time activity feed, filtering, export, and alerting.

Compliance certifications. DataQloo does not currently hold SOC 2 or any other third-party compliance certification.

Why this page is written this way

Security claims are the easiest place for a product page to overstate reality, and the costliest place to be wrong. Everything above is either true today or explicitly marked as not yet built — nothing here is aspirational language dressed up as a current feature.