Security & data
Your data stays yours. So do the weights.
We were built to work inside banks, insurers and health systems. Security isn’t a page we added later; it decides how every engagement is architected.
Where training runs
Inside your VPC on AWS, Google Cloud, Azure or Oracle Cloud; on your Databricks workspace; or on-premises. Optionally on our single-tenant, dedicated GPU capacity.
Data handling
Encryption in transit and at rest. PII detection and redaction before data reaches training. Least-privilege, time-boxed access for named engineers only.
Isolation
No shared datasets, adapters or checkpoints across clients. Separate storage, keys and compute per engagement.
Retention
Data and intermediate checkpoints in our custody are destroyed at handover, with a written certificate of deletion.
Ownership
You own the trained weights, adapters, code and evaluation assets. No licence fees, no runtime dependency on us.
Model risk
Model cards, data cards, red-team reports and validation evidence formatted for model-risk management and AI governance review.
Contracts
MSA, DPA, NDA and BAA where applicable. We complete standard security questionnaires and support your vendor risk process.
FAQ
Security questions
Do you use our data to train models for other clients?
Never. Your data, labels and resulting weights are used only for your engagement. This is written into our MSA.
Can you work in an air-gapped environment?
Yes. We have delivered training and serving on isolated on-prem clusters, with our engineers working through your bastion and change-control process.
Will you complete our security questionnaire?
Yes — SIG, CAIQ or your own format — and we sign your DPA, BAA where applicable, and NDA before any data is shared.
Talk to us about your constraints.
Bring your security architect to the briefing. We will walk through exactly where data, code and weights live at every step.
Book a technical briefing →