Security and data
What the API, webhooks and the MCP server never send, how keys and signatures protect a workspace, and who is responsible once data reaches an AI client.
fx_live_… → SHA-256 · whsec_… → AES-GCM
Data that never leaves through the API, webhooks or MCP
- payroll.paid carries payroll totals only, never an individual salary
- hr_letter.issued says that a letter was issued, never the letter's text
- Support events carry public messages only; internal ticket notes are never sent
- Clinical records (counselling, rehab, physiotherapy) have no API route, webhook event or MCP tool, and their text is stored encrypted (AES-256-GCM)
- Lists of webhook endpoints never include their signing secrets; a key or secret is shown only once
- Through MCP, e-mail addresses and phone numbers stay out of record details unless the workspace switches them on
API keys
- Only the SHA-256 hash of a key is stored; the key itself is shown once
- A key reaches only the areas and branches its creator may open
- A key stops when its creator is deactivated or deleted, and can be revoked at any time
- Every request is written to the request log
Webhooks
- Every delivery is signed with HMAC-SHA256 over the timestamp and the body
- The endpoint's signing secret is stored encrypted (AES-GCM)
- On the hosted platform, deliveries are never sent to private network addresses
MCP server
- Off until the workspace switches it on
- By default only people with Integrations & API rights may connect
- Each connection acts as one person, with that person's permissions and branches
- The write scope can only create drafts, which a person reviews and sends
- Names can be replaced by tokens and salaries hidden (masking)
- The log of each call keeps counts, never the contents of the answer
When data goes to an AI client
What an AI client reads through MCP leaves zmle and is processed by that client and its AI provider under your agreement with them. Connect only clients your business has approved, give each connection the narrowest access, use masking where you can, and end connections you no longer use.
More about security and data protection
Next: API v1 reference
Every endpoint of the REST API with its method, path and required scope, generated from the same OpenAPI document the API serves.