BuildersAlpha is built for organisations whose people work with sensitive information. This page summarises how we protect your data today, and what is on our security roadmap.
United States or European Union
AES-256 at rest, TLS 1.2+ in transit
Each workspace session runs in its own isolated environment
Enterprise identity and role-based access
Tools are built and tested on sample data
Data-subject rights supported
Records of access and administrative actions
We never monitor anyone's everyday tools
BuildersAlpha provides an AI-native workforce platform where employees learn with AI and turn their ideas into working tools for their team. Security and privacy are designed into the platform rather than added afterward: encryption in transit and at rest, isolated sessions, SSO and role-based access, and audit logs. To send us a security questionnaire, contact our team.
Our privacy commitments include:
Workspaces and published tools are hosted in the customer's region: the United States or the European Union. The platform runs on enterprise cloud infrastructure with managed components, isolated from our corporate systems.
| Layer | How it's protected |
|---|---|
| Application | Managed compute behind a load balancer |
| Workspace sessions | Each session runs in its own isolated environment, with no access to your internal systems or to other people's sessions |
| Live tools | Run in a safe frame on sample data; only the customer's signed-in people can open them |
| Data | Encrypted at rest and in transit |
Tools that an executive has approved stay live in Team tools for the whole team. They run in a safe frame, use sample data only, and only the customer's signed-in people can open them. Nothing is deployed into the customer's own systems. Uploads have names and customer details removed.
All data is encrypted in transit using TLS 1.2 or higher on every client-facing endpoint, and at rest using AES-256 managed encryption across data stores and backups. Secrets and keys are stored in a managed key-management service with restricted access.
Customer access supports SSO via SAML 2.0 and SCIM provisioning, with role-based access control mapping admins, team leads, and executives to the permissions their role needs. Internally, access to customer data is limited to those who need it and is logged.
Each workspace session runs in its own isolated environment with no access to your internal systems or to other people's sessions. Tools are built and tested on sample data. Employee work is processed to produce progress and certification records; people are never ranked against colleagues, and we never monitor anyone's everyday tools. Data is retained and deleted according to customer configuration.
| Data | Method | Retention |
|---|---|---|
| Customer & workspace data | Automated backups | Per customer configuration |
| Employee work | Encrypted storage | Per customer configuration |
| Application configuration | Version controlled | Indefinite |
All backups are encrypted at rest. Customers can request deletion of employee data in accordance with their agreement.
Report any suspected vulnerability to info@buildersalpha.com. We track every report to resolution.
These are planned and in progress. They are not in place yet, and we will update this page as each one is completed.
For our subprocessor list or a completed security questionnaire, contact info@buildersalpha.com or reach out through our contact form. See also our Subprocessors and Privacy Policy pages.
We'll answer it and walk your team through how BuildersAlpha protects your data.