Security and data
Built to your security requirements.
We do not claim certifications we do not hold. What we do is state, plainly, how your data is handled, who can see it, what the system may touch, and what waits for a person. Then we build to your requirements and document every connection.
Readiness
Eight things we are ready to put in writing.
Each one is a practice we already run, not a badge. Ask for any of them on the mapping call.
- 01We sign your NDABefore anything sensitive is shared, on your paper or ours.
- 02A BAA where the work requires itWhen protected health information is in scope, the agreement is in place before the build starts.
- 03Least accessEach connection holds only the access its job needs, scoped per client and revocable in one place.
- 04Every connection documentedWhat it reads, what it writes, and why, in one list your team keeps.
- 05Sensitive data stays in your environmentWe build inside your accounts. Where the work calls for it, the models run in your cloud or on your premises.
- 06High-risk actions wait behind a personMoney, messages to customers, and sensitive decisions sit behind an approval gate. The usual failure is work waiting, not work sent.
- 07No training on your dataWe use model providers whose APIs do not train on your inputs or outputs. Your data runs your system and nothing else.
- 08Every action leaves a recordAn audit trail of what ran, what it touched, and who approved it, open to you at any time.
Where your data goes
Inside your boundary, start to finish.
Unlike a public chatbot, an install runs inside your own accounts, on your tools, with your data. We use model providers whose APIs do not train on inputs or outputs. We keep only the operational metadata needed to run and report on the system, and you own everything it produces.
Where your data goes
Every install- Input: moves over an encrypted connectionEncrypted
- Processing: a provider that does not train on itNo training
- Output: returns to your tools, buffers clearedCleared
- Storage: operational metadata onlyMinimal
- Consequential action: waits for a personHeld
How access is controlled
Eight controls on every install.
- 01
Encryption in transit
Data moves over TLS. Nothing crosses the wire in plain text.
- 02
Encryption at rest
Stored data and backups are encrypted at rest by our infrastructure providers.
- 03
Access per client workspace
Access is enforced at the database row and scoped to each client's own workspace.
- 04
Scoped, revocable credentials
Each connection uses least-access, per-client credentials you can revoke at any time.
- 05
Audit logging
Portal and API actions are logged, so there is a record of what happened and when.
- 06
Isolation per client
Your data, credentials, and configuration share nothing with any other client.
- 07
Role-based access
Every screen and every connection is gated by role, so an approver, an operator, and a viewer see and do different things.
- 08
Security review on every release
Each release is reviewed against the controls above before it reaches your environment. Penetration testing and formal certification are arranged with a licensed third party when your policy requires them.
Paperwork
Send us your questionnaire.
The agreements that govern how we work with your data, and the two things we do before any build starts.
Your first department
Bring the process you still run by hand.
One mapping call. You leave with the system design, the price in writing, and the date it goes live. The first build lands in two weeks.
Responsible AI
How we decide what a system may do on its own.
Review mode first, narrow authority one action at a time, never for money, and a named owner for every decision.
Read the principles