The DataMind family

Your move.

Tell us who you are. Sales gets back to you to set it up.

Security

Your data. Your rules. In the database.

Where your data lives, what leaves your servers, and how DataMind OS handles sign-in, access, AI privacy and audit. With the limits stated plainly.

01Data

Where your data lives.

DataMind OS runs on Linux servers you control. This is what stays there and what does not.

What DataMind OS keeps on your servers and what leaves them
What Where it lives Leaves your servers
Source data, lake and warehouse tables ClickHouse on your servers No
Queries, reports and semantic models Your servers No
The AI audit trail and the request audit log Your DataMind OS database No
PII Shield, the detection model Your servers No
What a Mind sends to answer: your question, the query results it reads, training cards, and its replies DataMind's AI gateway, then zero-data-retention model endpoints Yes. Columns marked as personal data travel as tokens.
Web searches and page reads that a Mind makes DataMind's AI gateway and global search services Yes
Voice input in Minds chats Your browser vendor's speech service, not DataMind Yes, when someone uses the microphone
Report and deck subscriptions, data alerts and workflow alerts Your email server and the Slack, Discord or Google Chat channels you configure Yes, to the recipients you choose
Installation, updates and maps A handful of DataMind domains Outbound requests from the host

DataMind's AI gateway stores the request and response bodies of model calls in its own log; turn on Prohibit PII transmission to keep them out of it.

02Identity

Sign-in.

  • OpenID Connect with Microsoft Entra ID, Google Workspace or any OIDC provider.
  • Authenticator-app two-factor authentication, which admins can require for everyone or for chosen users.
  • SSO-only mode: everyone signs in to DataMind OS through your identity provider, and users with the built-in Admin role keep a password fallback. Turning it on ends all existing sessions.
  • New colleagues get an account on their first SSO sign-in, for email domains on your allowed list. There is no SCIM and no deprovisioning sync.
  • SQL and BI tools that connect to ClickHouse directly, such as DataGrip, DBeaver, Power BI and Excel, sign in with the user's email and DataMind password, not through SSO, and two-factor authentication does not apply to them.

03Access

Access rules.

  • Object, column and row rules are enforced in the database through per-role views, so they hold in the SQL editor, BI, Minds and external tools.
  • View as user: an admin with the Impersonate User permission sees DataMind OS exactly as another user does, and every request is logged with both people.
  • Personal access tokens are stored as hashes, confined to their scope and revocable by admins.
Permission matrix for the role Store_managers in DataMind OS: DataPrism permissions grouped as high-level presets, standard sets and granular permissions, with Reports Viewer and View DataPrism Reports selected.
Role permissions

04AI

AI privacy.

  • Model calls go through DataMind's AI gateway, which routes only to zero-data-retention model endpoints and disables any model that loses its zero-data-retention endpoint on an hourly check.
  • PII Shield, an on-premise detection model, checks what people send to Minds and persistent training cards.
  • Columns marked as personal data reach models as tokens. People in the chat see the real values.
  • Prohibit PII transmission: when it is on, DataMind's platform refuses any AI request that contains common personal identifiers before it reaches a provider.
  • A company Region setting sends AI chat traffic to EU-region endpoints. Embeddings and web search use global endpoints.
  • The gateway keeps its own log of model calls; see Where your data lives.
PII Shield playground in DataMind OS: a refund message with a name, email address, phone number, card number and street address highlighted, and 8 matches listed with their confidence.
PII Shield playground

05Audit

Audit.

  • The request audit log records every API request with time, user, the real person when someone is viewing as a user, IP, status and response time, with filters and export.
  • The AI audit trail logs every AI request from DataMind OS with model, agent, user, duration and status, in your own database, exportable as CSV, Excel, JSON or TSV.
  • A ClickHouse activity console and live service health.
Observability System Overview in DataMind OS: every service with its memory use and uptime, 29 of 29 up, and a 24-hour memory chart for datamind-api.
Observability

06Operations

Secrets and operations.

  • Connector, SSO, two-factor and MCP secrets are encrypted at rest with AES-256-GCM.
  • The gateway strips client-supplied identity headers and rejects session tokens issued before a password change.
  • Monthly updates, applied from the browser in Admin > Platform or in the Installer.
  • The Installer updates itself and rolls its own image back once if the new build does not report healthy.

07Limits

Know before you buy.

  • Not air-gapped. The host needs outbound access to a handful of DataMind domains for installation, updates, maps and AI.
  • Sign-in is OpenID Connect. SAML and SCIM are not supported.
  • Direct database connections use passwords. External SQL and BI tools sign in with the user's email and DataMind password, without SSO or two-factor authentication.
  • DataMind does not host DataMind OS for you today. It runs on infrastructure you control.
  • Model calls leave your servers through DataMind's AI gateway. DataMind's AI gateway stores the request and response bodies of model calls in its own log; turn on Prohibit PII transmission to keep them out of it.

Send us your questionnaire.

Use the form to tell us what your security review needs, and sales gets back to you with answers.