Harmonize keeps each client's data separate at several layers.
-
Sign-in: Each login belongs to one organization. The access token issued at sign-in carries your organization's ID.
-
Token checks: Before running a query, Harmonize MCP verifies the token's signature, issuer and audience with Auth0. Requests without a valid token are rejected.
-
Request handling: Harmonize takes your organization from the verified token, not from the AI assistant's request. The AI assistant can't name or request another client.
-
Query construction: Each query is built on our servers from the governed catalog and limited to your organization's data.
-
Execution and database access: Queries are checked again before they run, and database access controls add a further layer.
We also don't use a client's identifiable data for the benefit of other clients without that client's consent.