# Privacy Policy The CorralData MCP Server integration is governed by the [CorralData Privacy Policy](https://corraldata.com/privacy). ### How your data is handled When you use CorralData through Claude, here's what happens with your data: * **Authentication tokens** are used to verify your identity and permissions. Tokens are validated server-side and are never stored persistently. * **Queries and tool calls** are processed in real time and forwarded to the CorralData API on your behalf. The MCP server does not store query history or results. * **Query results** are returned directly to your Claude conversation. They are not logged or retained by the MCP server. * **The server is stateless** — no user data, session data, or conversation history is stored between requests. ### What data does Claude see? When you use CorralData tools through Claude, the tool responses (schema metadata, query results, board/widget details) become part of your conversation with Claude. This data is subject to [Anthropic's usage policy](https://www.anthropic.com/legal/consumer-terms). ### Third-party services The MCP server connects to: * **CorralData API** — to execute tools on your behalf * **Keycloak** (your organization's instance) — for authentication and token validation No data is shared with any other third-party services. ### Questions? For privacy-related questions, refer to the full [CorralData Privacy Policy](https://corraldata.com/privacy) or contact your organization's CorralData administrator. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.corraldata.com/kb/mcp/privacy-policy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.