Security
What stays in your cloud, and what leaves.
Read-only ERP access. Fixed tools, no free SQL. Every call logged. Six named flows leave your account, and nothing else.
- Read-only ERP userNo tool can post, edit or delete in your ERP.
- Runs in your cloudAWS, Azure or GCP, in the region you choose.
- Six named flows leave itEach one named, three off until you switch them on.
- Roles and audit log, tested in LeadsEach new workflow uses the same model.
- Logged support accessTime-limited, only with your ticket or approval.
- Certifications plannedSOC 2 report and penetration test: planned, not held.
Data flows, all of them
What leaves your cloud account: six named flows, and nothing else.
- Assistant questions. The answer to each question a user asks goes to the assistant you connect: OpenAI (ChatGPT) or Anthropic (Claude), or another provider named in your statement of work, under your organisation's agreement with them.
- In-app AI (optional, off until you turn it on). Prompts and the data they need go to the model provider and region you choose, under your account.
- Chat channels (optional, off until you turn them on). If you use a chatbot, each message and its answer pass through that channel's provider, for example Meta (WhatsApp), Microsoft (Teams), Slack or Telegram. We name each one in your statement of work before it is switched on.
- Support access. Our engineers in India, through a logged, time-limited role, only with your ticket or approval.
- Error monitoring. Error messages and technical context, without record content.
- Email notifications (optional). Recipient address and message, only if you use digests or reminders.
Assistant field policy. ERP tools never return contact names, phone numbers, emails, tax IDs or bank details. Leads and CRM tools return only the fields the user's role can see in the app, with phone numbers masked as on screen, and never return tax IDs or bank details.
What the film shows
Security film: your ERP and our deployment inside your cloud account; six named flows leave it, drawn one by one: assistant questions; in-app AI, optional; chat channels, optional; support access by our engineers in India, logged and time-limited; error monitoring without record content; email notifications, optional. What leaves your cloud account: six named flows, and nothing else.
Where your data lives. ERP Intelligence: your AWS, Azure or GCP account, in the region you choose. CRM functions: your cloud account, or hosted by us. A DPA is provided with the statement of work. Leads: hosted by us, one deployment per client, or your cloud account. We name the hosting region before you sign.
Cross-border transfers. Support from India is an international transfer for UK and EU clients. Ask us for the safeguards that apply to your contract.
AI training. We do not train models on your data. Model providers act under your account and their data terms.
Assistant tools: fixed, read-only, logged
The assistant does not write its own queries. It calls a fixed list of tools, each declared as read-only or write. Each user signs in once, and the assistant gets only the tools that user's role allows. Status: in build for ERP Intelligence; demo in Leads.
- ERP tools have no write access. No tool can post, edit or delete anything in your ERP.
- Lead and CRM write tools are separate, off by default, and limited to what the user's role allows in the app.
- Every assistant call writes a log row: user, tool, row count, result. The log holds no record content.
- Your admin can switch off AI access for one user, one tool or the whole company.
Roles and audit log are built and tested in the Leads accelerator. Each new workflow uses the same model.
Status of our security programme
Status as of 27 October 2026.
| Item | Status |
|---|---|
| Read-only ERP access; one deployment per client | In place by design |
| Role-based field masking; audit row on every Leads change | In place in the Leads base |
| SOC 2 report, penetration test | Planned Not held today |
| Multi-factor authentication, single sign-on, insurance | Planned |
| Data processing agreement | A DPA is provided with the statement of work. |
| Responsible disclosure | Report issues to hello@buildmysaas.ai |
For procurement
- Security pack: on request.
- DPA: on request. A DPA is provided with the statement of work.
- Contract set (master services agreement and statement of work): on request.
If we stop working together
In your cloud: code, infrastructure-as-code and runbook are already in your account. We remove our access.
Hosted by us: we export your data, then delete the deployment, the stored files and the backups within the period agreed in your contract, and confirm in writing.