Data Egress Disclosure
What data leaves your organization #
When you use Mandatum tools via MCP or REST, the following data is sent from Mandatum's servers to your AI client (Claude, ChatGPT, or API caller):
Shared corpus tools (statute pool + citation/benchmark tools) #
These tools return data from the shared corpus — statute text and citation and title-match results. Shared corpus data is not organization-specific. It is the same for all organizations.
| Tool | Data returned |
|---|---|
searchStatutes |
Statute section text, titles, jurisdiction codes |
getSection |
Full statute section text by CAP number |
verifyCitation |
Per citation: whether it resolves, the matching statute and section ids, statute title, section heading, jurisdiction, source URL, and a reason code. No section body text. |
checkSourceExists |
Whether a source reference exists; its ID |
parseDocument |
The parsed structure of the document you sent. Nothing is stored. |
scoreConfidence |
A numeric confidence score (0–1); no DB data |
compareLaws |
Statute titles and CAP numbers per jurisdiction |
Org-bound tools #
These tools return data specific to your organization. The data returned is scoped to your organizationId and is not shared with other organizations.
| Tool | Data returned |
|---|---|
identifyGaps |
Gap item IDs, descriptions, and gap analysis IDs for your org |
scoreAlignment |
A numeric alignment score; gap count |
listSkills |
Workflow definition slugs and display names (not org-specific) |
triggerWorkflowRun |
A run ID and workflow slug confirming the trigger |
issueGapReport |
The issued gap report for your workspace: gap items and resolved citations, with its content hash |
What Mandatum logs #
All authenticated requests are logged in audit_log with:
- The user ID and organization ID
- The tool/action called
- The resource ID accessed (if applicable)
- A timestamp
Audit log entries are append-only. Mandatum staff may access audit logs for security investigation purposes in accordance with the Terms of Service.
What is NOT sent to AI clients #
- Database credentials or API keys
- Other organizations' data
- Internal system details (database schema, infrastructure config)
- Full database rows beyond what the tool explicitly returns
Token handling by AI clients #
When you connect Claude.ai or ChatGPT to Mandatum via OAuth, those clients receive an access token. That token is stored by the AI client provider subject to their privacy policy. Mandatum does not control how Claude.ai (Anthropic) or ChatGPT (OpenAI) store or handle tokens.
To revoke access at any time, use the workspace's API keys page in Mandatum and revoke the connected app or key.
Jurisdiction coverage #
The shared corpus currently covers Barbados and related Commonwealth Caribbean jurisdictions. Data accuracy depends on the corpus ingestion pipeline. Mandatum does not guarantee completeness or legal accuracy of shared corpus data.
Matters ("vault") tools — privileged client matter egress #
Confidentiality notice. Enabling the Matters tools allows privileged client matter content to egress from Mandatum to the connected AI provider. Read this section carefully before enabling Matters access for any API key.
The Matters tools (listMatters, getMatter, getMatterDocuments,
getMatterConversations) expose your organisation's most confidential data.
This section describes what egresses, the retention posture, and the opt-in
requirements.
What Matters data leaves your organisation #
| Tool | Data returned |
|---|---|
listMatters |
Matter IDs, titles, descriptions, creation dates for your org |
getMatter |
Full detail row for a single Matter (title, description, storage prefix, dates) |
getMatterDocuments |
Document metadata (filename, content type, storage path) attached to a Matter |
getMatterConversations |
Conversation summaries (id, title, mode, updated_at) — NOT raw message bodies |
Raw chat message bodies are never returned — only conversation-level summaries.
Zero Data Retention (ZDR) / not ZDR-eligible #
Matters content egresses to the connected AI provider (Anthropic/OpenAI). This egress is not covered by Zero Data Retention (ZDR) arrangements. The AI provider handles the data according to their privacy policy and your agreement with them. Mandatum does not control how the AI provider stores or processes matter content after it is transmitted.
If your bar association or jurisdiction requires that privileged client communications not leave a controlled environment, enabling Matters tools may be incompatible with those obligations.
Default OFF — explicit opt-in required #
Matters access is off by default. A newly issued API key never includes
matters:read in its default scopes. You must explicitly enable the Matters
toggle per key in Sharing Controls on that key's row on the API keys page. There is no
batch or automatic enablement.
Audit logging #
Every Matters tool call (via MCP or REST) writes one row to the audit_log
table containing: the key ID, the tool name, the transport (mcp or rest),
the organisation ID, the user ID, and a timestamp. The audit log is
append-only. These entries are available for security investigation and
compliance review.
Recommendation #
Before enabling Matters access for any key, review:
- Your bar association's rules on confidentiality and third-party AI use.
- The AI provider's data processing agreement and ZDR eligibility.
- Whether the connected LLM is authorised to process your clients' privileged matter data.
Mandatum shows this warning in the UI wherever a Matters switch is displayed.
Legal disclaimer #
Mandatum is a research tool. Nothing returned by any tool constitutes legal advice. Users should verify all statute content against official government sources before relying on it for legal purposes.