← MCP home
PRIVACY

Privacy and the PartnerStack MCP.

How the PartnerStack MCP server handles your data when you connect an AI assistant. This page supplements the PartnerStack Privacy Policy.

What the server accesses

The MCP server reads and writes PartnerStack data on your behalf, only when your AI assistant calls a tool. Access is limited to the PartnerStack instance you chose at sign-in and follows your normal PartnerStack permissions.

Authentication

You sign in with your normal PartnerStack login through OAuth. Your AI assistant receives an access token, never your password. You can stop access at any time by disconnecting PartnerStack in your assistant.

Storage

The MCP server does not store your program data. Data stays in PartnerStack. Each request runs under the OAuth token you approved, and all traffic is encrypted over HTTPS/TLS.

Safety scanning

To protect against prompt injection and sensitive-data leaks, tool inputs and results are scanned by Google Cloud Model Armor before they are passed along.

Your AI provider

Data returned by a tool is sent to the AI assistant you connected, such as Claude, ChatGPT or Gemini. How that provider processes and retains conversations is governed by their own privacy policy and your account settings with them.