Security and privacy
Masking and hashing of personal data, per-workspace storage, encrypted secrets, roles and 2FA, encrypted backups, the OWASP ASVS level 1 target, export and deletion.
A technical summary. Binding terms are in the privacy policy and the data processing agreement.
Personal data
- Columns marked as personal data are masked before they reach Si's prompt.
- Values are hashed (SHA-256 with a per-workspace salt) as soon as they are loaded; the published warehouse never contains the salt. Keeping original values is an opt-in, off by default.
- No API, Si answer or MCP tool returns buyers' personal data.
- Si only reads a masked sample of up to 1,000 rows, and only with your consent.
Per-workspace isolation
- Each workspace has its own warehouse: Parquet files under their own storage prefix, its own table catalogue and its own storage keys, which can only read that workspace's prefix.
- Dashboards, Si and MCP read only the published copy of the right workspace; every request checks the caller's access to it.
Secrets and passwords
- Source passwords, service account keys, Slack tokens and 2FA secrets are encrypted at rest and never shown again; the encryption key can be rotated.
- Login passwords are hashed with Argon2id.
- MCP tokens are stored only as hashes, expire and can be revoked.
Access
- Four roles per workspace: Owner, Admin, Analyst, Viewer.
- Two-factor authentication with an authenticator app (TOTP) and 10 recovery codes; the Owner can require 2FA for Owners and Admins.
- Short sessions (15-minute access tokens), sign out one device or all; login is locked for 15 minutes after 5 failures.
- A security log per workspace; every Si and MCP tool call is recorded.
Web application
- Security headers: a per-request Content Security Policy, no framing, HSTS in production.
- Rate limits on login, questions to Si and MCP.
- Controls target OWASP ASVS 4.0.3 level 1; the checklist is tracked internally and some items (such as production TLS configuration) are still being completed. This is a target, not a certification.
Backups
- Automatic daily backups, keeping 7 daily, 4 weekly and 6 monthly copies.
- Backups are encrypted before they leave the server (AES-256-GCM) with a separate key, then stored on object storage with encryption, versioning and object lock.
- Targets: at most 24 hours of data loss, recovery within 4 hours.
Export and deletion
You can export all of a workspace's data (Parquet, CSV for tables up to 100,000 rows, definitions as JSON), download your personal data, delete a workspace (restorable for 7 days) or delete your account at any time. Backups expire after at most 6 months.
Reporting a vulnerability
Email security@dataxland.com.
Related
Architecture
How data flows from your sources through three layers into each workspace's own warehouse; build, check and publish; and how dashboards, Si and MCP read numbers through one metric gateway.
Self-hosting (Enterprise plan)
Run DataxLand in your own Kubernetes infrastructure with a Helm chart, an offline license and an air-gapped mode; when to choose it, what it includes, how it differs from the cloud and its known limits.