Security
Effective from: 2026-11-16 · Last updated: 2026-11-16
Data
- One warehouse per workspace: Parquet files on object storage with a storage key unique to the workspace; a compute session only receives the key of that workspace.
- Personal data: hashed on load with a dedicated salt; the salt never enters the published warehouse, environment variables or logs; masked before anything is sent to an AI model.
- Connection secrets are encrypted at rest; backups are automatic and encrypted, and restoring from backups is rehearsed regularly.
- Location: the warehouse and backups of customers in Vietnam are located in Vietnam. The list of sub-processors is in the Data Processing Agreement.
Access
- Owner, Admin, Analyst, Viewer and custom roles; a workspace can require two-factor authentication.
- Enterprise plan: single sign-on via SAML or OIDC, row-level permissions, audit log export.
- Sign-in and security activity logs are kept for 2 years.
- MCP tokens are stored only as hashes, expire and can be revoked, or are issued via OAuth; every call is logged.
Si
Si reads metrics through the semantic layer; answers with figures always use approved metric definitions. When investigating data, Si runs read-only queries in an isolated environment, on samples with personal data masked, within limits on the number and cost of queries.
Web application
Strict Content Security Policy, framing blocked outside an allow-list, HSTS over HTTPS, no advertising cookies. Security controls are checked against OWASP ASVS level 1.
Personal data incidents
DataxLand has an incident response process: detect, contain, fix, record and learn. When an incident affects personal data, DataxLand notifies the workspace owner without undue delay and no later than 72 hours after detection, and notifies the personal data protection authority within the time limits set by law for data DataxLand controls. Details are in the Privacy Policy and the Data Processing Agreement.
DataxLand's personal data protection team handles questions about personal data at security@dataxland.com.
Export and deletion
You can export all data in open formats and delete a workspace or account at any time. See the Privacy Policy.
Vulnerability disclosure policy
DataxLand welcomes good-faith security research and is committed to coordinated, responsible disclosure.
How to report. Email security@dataxland.com with a description of the vulnerability, steps to reproduce, the possible impact and how to reach you. In scope: dataxland.com, app.dataxland.com, api.dataxland.com, the MCP server and DataxLand's official bots.
Our commitments.
- Acknowledge your report within 3 business days and share an initial assessment.
- Keep you updated on progress and tell you when the fix is out.
- Credit your contribution if you wish. DataxLand does not currently pay monetary rewards for vulnerability reports.
Safe harbour for good-faith research. DataxLand will not take legal action or ask authorities to act against researchers who follow this policy, and considers such research authorised. You must:
- only use your own accounts and workspaces; stop and report as soon as you reach someone else's data, and do not copy, keep or disclose it;
- not disrupt the service (no denial of service, no spam, no high-rate automated scanning);
- not use social engineering against staff or customers, and not attempt physical access;
- not exploit a vulnerability further than needed to demonstrate it.
Disclosure. Please keep vulnerability details confidential until DataxLand has fixed it, or for at most 90 days from your report, whichever comes first. If more time is needed, DataxLand will discuss it with you before the deadline.