Security, in plain words.
What the product enforces today, and what it does not have yet.
Enforced today
You choose which AI models may touch your data
Switch models off by the country that made them or by where they are hosted, for the whole company. A team or a bot cannot switch them back on. Or allow open models only, or only your own.
Every consequential step passes a gate
No write to your data happens without a policy check and an entry in the record. Autonomy is set by a policy you can read, not by code.
Money actions wait for a person
Issuing an invoice or proposing a contract can never run automatically.
A record that cannot be rewritten
The record of who asked, who approved and what it cost can only be added to, and a changed entry shows.
Workspaces are separate
One company's workspace never reads another's rows; the database enforces it.
Masking by clearance
A field someone may not see is shown masked, before the model and before the caller.
Budgets slow before they stop
When a budget runs low, the assistant slows down or asks for help before it blocks.
A published data processing agreement
On the European Commission's standard clauses, at massrelay.ai/dpa. A signed copy on request.
Tool results are data
Anything a tool returns is scanned for secrets and injected instructions, and never treated as an instruction.
Not yet
Certification
Not SOC 2 or ISO certified yet.
Data residency
Planned on the Business plan.
Security questions or a questionnaire: [email protected]
Talk to us.
Your company, its size and the first job you would hand to an assistant. We answer by email, nothing else.
Tell us your company, its size and the first job you would hand over. A person answers.