Trust
How Quattr handles your data
The platform, the MCP and the plugin all read your first-party search data. This page says what that means: how a connection is authorized, what it can see, what it can change, and what Quattr does not do with it.
Authorization
The MCP connects to Claude, ChatGPT, Cursor, Codex and other plugin-agent-compliant clients over OAuth 2.1 with a read-only scope. No API key needs to be copied into a local configuration file. Revoking the authorization in your Quattr account ends the connection.
Scope
Your Quattr account decides what is visible. An assistant connected through the MCP cannot see more than the person who authorized it can see in Quattr, and every answer carries the scope it was measured at and a link back into the product.
Write boundaries
The analytical connection is read-only. Nothing is written back to your analytics or ads accounts. Actions that change your site, such as GIGA publishing content or internal links, are separately permissioned in the platform and run with your team's review and approval.
Model and data use
Quattr does not use customer data to train models. Analyses run against your own connected data and return results to the client you asked from.
Retention
The retention period for query results and generated artifacts is governed by your agreement with Quattr. For the current terms, ask your Quattr strategist or write to privacy@quattr.com.
Supported clients
Claude, ChatGPT, Cursor, Codex, and clients that implement the plugin-agent protocol.
Attested by Anurag Singhal, September 22, 2026. See also the privacy policy.