Encryption at Rest
Databases, backups and uploaded files are encrypted at rest (AES-256) by our hosting provider. Credentials for an institution's own database are kept in AWS KMS-backed secrets, never in the application.
Encryption in Transit
Every connection to XData Studio, from the browser, the mobile app or the API, uses HTTPS. Plain HTTP is redirected or refused.
Database Isolation
On Enterprise, an institution can have a database of its own. On every other plan workspaces share a database, and every query is scoped to the workspace making it.
AI Data Handling
For statistical analysis the AI sees column names, types and summary statistics, not your rows, and the analysis runs on our servers. Qualitative coding is different: the passages you ask it to code are sent to the model. Models run on AWS Bedrock, which does not train on your data, or on your own provider key.
Access Controls
Roles and permissions are set per workspace. Two-factor sign-in is available on every account, API keys can be revoked at any time, and idle sessions expire.
Audit Logging
Sign-ins and changes to forms, projects and settings are logged with the time, the user and their IP address, so admins can see who did what.
Where we stand
What has been audited, and what has not yet.
Responsible Disclosure
Found a security vulnerability? We appreciate your help keeping XData Studio safe. Please report security issues responsibly so we can address them before they affect users.
Report a vulnerabilityQuestions about security?
Our team is happy to discuss your specific security and compliance requirements.
Talk to our team