Skip to content

Mesh connector for Claude privacy policy

How Lucid Labs handles data when you use Mesh from Claude: what the connector receives, what it keeps, where, for how long, and who else is involved.

Who we are and what this covers

Lucid Labs Pty Ltd (ABN 33 678 306 539) provides Mesh. This policy covers the Mesh connector for Claude, the remote MCP servers at mcp.lucidlabs.com.au/claude/mcp and, for managed service providers, mcp.lucidlabs.com.au/claude/msp/mcp. It adds to the Lucid Labs privacy policy, which covers everything else, including your rights and how to complain. Setup and usage are described on the connector documentation page.

Mesh works on data that belongs to your organisation. For that data your organisation is in control, and Lucid Labs processes it on your organisation's behalf under its Mesh agreement.

What the connector receives

  • Your sign-in. Microsoft Entra ID tells Mesh who you are (your name, work email address, user ID and organisation ID) and issues a delegated access token for your account. Access tokens are held in memory only and are not saved.
  • Each tool call Claude makes: the name of the tool and the arguments Claude sends with it, such as a search term, a date range, a ticket number or the text of a draft.
  • The data a tool reads to answer that call, from Microsoft 365, Dynamics 365 and Dataverse, or a service your organisation has connected. Mesh reads it with your permissions and returns it to Claude.
  • Technical details of the connection: the client name and version Claude reports, the MCP session ID, your IP address and the time of each request.

Mesh does not receive your Claude conversation, only the tool calls Claude chooses to make. It has no access to your Claude chat history or Claude's memory, and does not ask for them.

How it is used

Lucid Labs uses this data only to run each tool you or Claude call, to keep a record of the changes made through Mesh, to secure and support the service, and to measure how Mesh is used. We do not sell it, and we do not use it to train AI models.

What is kept, and where

Data a tool reads to answer a call is used in memory and returned to Claude. Mesh does not keep a copy unless you ask a tool to save something. What Mesh does keep:

  • The action log. Every call to a tool that changes something, and every call that fails, writes a record to the action log: the tool name, when it ran and for how long, whether it succeeded, the signed-in user's email address, the arguments Claude sent and a short summary of the result or the error. Passwords, tokens, keys and other credential-like values are removed from the arguments before the record is written. Other content, such as names, email addresses or the text of a draft, is kept as sent. The action log is stored in your organisation's own Dataverse environment.
  • Notes. Notes you ask Mesh to save are stored in Mesh's database, kept separate for each organisation and visible to others in your organisation.
  • Connections. The credentials your organisation sets up for a connected service are kept in Azure Key Vault.
  • Service logs and telemetry. For each tool call: the tool name, duration, outcome and size of the result, your organisation ID and a one-way hash of your user ID. Tool arguments and results are not recorded in telemetry. Connection logs record your organisation ID, user ID, email address, IP address and client name, for security and support.

All of this is hosted in Microsoft Azure in the Australia East region. Your organisation's Dataverse environment is in the region your organisation chose for it.

Third parties

  • Microsoft hosts Mesh (Microsoft Azure), handles sign-in (Microsoft Entra ID), and is where Microsoft 365, Dynamics 365, Dataverse and Partner Center data is read from and written to.
  • Services your organisation has connected to Mesh, such as Autotask, HaloPSA or Pax8. Mesh calls them only when you use one of their tools, and the data goes to wherever that service hosts your organisation’s account, under your organisation’s agreement with it.
  • Anthropic. Tool results are returned to Claude, and Anthropic handles them under its own terms and privacy policy.

We do not share connector data with anyone else, except where the law requires it.

How long it is kept

  • Action log: kept in your organisation’s Dataverse for as long as your organisation decides. Your administrators can review and delete it there.
  • Notes: until you or a colleague delete them, or until your organisation’s Mesh data is deleted.
  • Service and connection logs: 90 days.
  • Usage measurements (organisation ID and hashed user ID): up to two years.
  • When your organisation leaves Mesh, the data Mesh holds for it is deleted 21 days later, unless a legal hold applies, and backups roll off within a further 7 days.

Your choices

You can disconnect the connector in Claude at any time, and your administrator can revoke the Mesh apps' consent in Microsoft Entra ID. To ask for access to, correction of or deletion of data Mesh holds about you, contact your organisation's administrator or us.

Contact

Privacy questions: privacy@lucidlabs.com.au. Product support: contact@lucidlabs.com.au. If this policy changes we will update this page.

Last updated: 10 November 2026.