SECURITY & DATA HANDLING
Your data is the asset. We treat it that way.
We document where your data runs, which systems can access it, and what happens when an engagement ends. Your IT team can review the architecture and send follow-up questions in writing.
01
Your data stays in your house.
Wherever possible, systems run inside your Microsoft 365 or cloud tenant, or on hardware you own. We build in your environment, not ours.
02
Least-privilege, scoped, revocable.
Connectors get read access to exactly the systems a workflow needs, nothing else. You can see the scope list and revoke it at any time.
03
Your data trains nothing.
Client data is never used to train models, ours or anyone's. Model providers we route to are configured for zero retention where the provider supports it.
04
Humans approve, systems record.
Every consequential action an AI employee takes requires human approval and lands in an audit trail you own.
05
Keep the system portable.
Vector stores, knowledge graphs, skills, and code live in your repositories in open formats from day one. Ending our access requires a permissions change, without a separate migration project.
WHERE YOUR DATA LIVES
IN YOUR TENANT
Documents, mailboxes, chat history, and the knowledge systems we build from them.
IN TRANSIT, ENCRYPTED
Calls to model APIs when a task routes to a frontier model, under the retention terms above. TLS everywhere.
ON YOUR HARDWARE
For local deployments: models, weights, and inference logs never leave the building.
PLAIN ANSWERS
What buyers ask before kickoff.
Paperwork
We sign your NDA and DPA, and we'll complete your security questionnaire.
Subprocessors
Disclosed in writing before the engagement starts, updated if they change.
Certifications
We do not currently hold SOC 2 certification. Our diligence pack maps current controls to common security-questionnaire fields, lists subprocessors and retention terms, and documents exit paths. Each artifact has a current public status. If SOC 2 is mandatory for your procurement process, tell us early so we can confirm whether the requirement rules us out.SEE THE DILIGENCE PACK >
Incidents
A named contact, a notification commitment in your contract, and a written post-incident report.