Security by architecture.

Exagomatica is a local MCP server. It runs on the user’s own computer and talks to Claude Desktop over stdio. There is no Exagomatica cloud in the data path. Your Power BI queries (and, if you connect change tracking, your Azure DevOps data) are processed locally and are not sent to, or stored on, our servers.

A note on what “local” means: Claude Desktop itself, like any AI assistant, sends your questions, and the results Exagomatica returns, to Anthropic’s API to generate answers. The guarantee here is about Exagomatica: it adds no cloud of its own to your data path. “Local” means your data doesn’t leave through Exagomatica, not that the assistant runs offline.

You sign in once, during setup, with the same Microsoft (Entra ID) account you already use, and multi-factor authentication is fully supported. Exagomatica acts as you: it can only see the data you are already authorised to access, and Power BI applies exactly the access controls it applies to you anywhere else, including row-level security for Viewer-role users. One consequence worth knowing: Microsoft does not apply row-level security to workspace Contributors, so granting a business user Contributor to unlock lineage also widens what they see, in Power BI itself. Our FAQ explains both levels of access.

This describes a standard install. An organisation can instead configure a shared service account for unattended use; queries then run under that account’s permissions rather than yours. Setting this up requires credentials only your IT team can issue.

Exagomatica reads from your data sources to answer questions; it does not modify them. No write operation exists in the product at any role: the only calls it makes to Power BI are queries and definition reads, every query is checked against a read-only rule before it is sent, and an automated check in our build fails if a write operation is ever added. Data-definition and destructive operations (DDL) are blocked, so a question can never turn into a schema change or a delete.

Your Microsoft sign-in tokens are encrypted at rest with Windows DPAPI, in a local store only your own Windows account can read; nothing is kept in plaintext, and no passwords are stored at all. Exagomatica ships with no usage telemetry: it does not phone home with what you ask or what your data contains.

The site is served only over HTTPS and sends HSTS so browsers refuse to downgrade to HTTP. A strict Content Security Policy plus X-Content-Type-Options, a constrained Referrer-Policy, and a Permissions-Policy that denies camera, microphone, and geolocation harden every page against common web attacks.

When you become a customer, sign-in is handled by Clerk and billing by Paddle, our merchant of record, so card data is processed by a PCI-compliant provider and never touches our own systems. See our privacy notice for how we handle personal data.

If you believe you have found a security issue, we want to hear from you. Email hello@exagomatica.com with the details and we will respond promptly. Please give us a reasonable chance to investigate and remediate before any public disclosure.