Privacy Policy

AdvisorPPC MCP Connector

Last updated: August 8, 2026

The AdvisorPPC MCP Connector ("the Connector," "we," "us") is an OAuth-secured remote Model Context Protocol (MCP) server that connects your own advertising and analytics accounts to supported AI clients. This policy explains what data the Connector handles, why, where it is stored, how long it is kept, and the rights you keep over it. If anything here is unclear, contact us at support@advisorppc.com.

Claude connector scope. The AdvisorPPC endpoint for Claude exposes the full availability-filtered catalog of more than 600 purpose-built tools. It includes read, reporting, write and management capabilities for supported advertising, analytics, commerce, content and client operations. Generic meta-dispatchers are excluded.

1. What the Connector does

When you authorize an available platform, the Connector can work with that account in the following ways, depending on the product surface you use:

• Authenticate to a platform you own using its official OAuth flow.
• Read performance metrics and account metadata (campaigns, ad groups, keywords, budgets, spend, conversions, audiences, and similar configuration data).
• Change eligible account state when you authorize a write or management action. Write tools are identified in their MCP metadata and remain subject to your provider permissions and AdvisorPPC access controls.

2. Connected platforms

AdvisorPPC is designed to support the following platforms. Actual availability depends on provider approval, account eligibility, product configuration, credentials and the tools enabled in the live catalog.

• Google Ads
• Google Analytics 4 (GA4)
• Google Tag Manager
• Google Search Console
• YouTube
• Google Merchant Center
• Meta (Facebook & Instagram)
• Microsoft (Bing) Ads
• Reddit Ads
• TikTok
• LinkedIn
• Pinterest
• X (formerly Twitter)

You connect only the platforms you choose. The Connector cannot reach any account you have not authorized.

3. Data we collect and handle

• OAuth tokens. When you authorize a platform, that platform issues us access tokens (and, where the platform supports it, refresh tokens) scoped to the permissions you granted. We store these so the Connector can call the platform's API on your behalf without re-prompting on every request. We never receive or store your platform passwords.
• Meta connection records. For a Meta connection, we store the public issuing App ID, the permission names Meta confirms were granted, and an account email only if Meta returns it. We store a keyed digest rather than the raw value of Meta's app-scoped user ID so a signed deletion request can be matched to the correct credential.
• Account metadata. Identifiers and configuration for your connected accounts, such as account IDs and names, campaigns, ad groups, ads, keywords, audiences, budgets, and conversion settings, read as needed to carry out your requests.
• Performance data. Metrics returned by the platforms (impressions, clicks, cost, conversions, and similar reporting figures) for the time ranges you ask about.
• Operational records. Our general tool-call observability telemetry retains only the internal numeric tenant and agent identifiers, tool name, timestamp, success status, elapsed time, and, if a call failed, one generic code from a fixed safe list (for example, rate_limited or permission_denied). This telemetry does not retain tool arguments or argument names, tool results, provider error messages, account IDs or names, prompts, or conversation text.

We collect only what is needed to run the Connector for you. We do not buy, enrich, or combine your data with data from other sources.

4. Why we use your data and the limits we accept

Your data is used for one purpose only: operating the Connector so an authorized client can perform the eligible feature you request. The Claude connector may read authorized data or carry out a write that you approve, within your provider permissions and AdvisorPPC access controls. Beyond that purpose, we make the following commitments:

• We do not sell your data. Not to advertisers, data brokers, or anyone else, in any form.
• We do not share your data across customers. Your tokens, accounts, metadata, and performance figures are isolated to you and are never exposed to, or mixed with, another customer's data.
• We do not use your data to train AI or machine-learning models. This applies to our models and third-party models. Your account data is not contributed to a model-training dataset.
• No advertising or profiling. We do not use your data to target you with ads or build marketing profiles.

We disclose data only to the platforms you connected (in order to fulfill your requests), to the infrastructure providers that host the service under confidentiality obligations, and where we are legally compelled to do so by valid legal process.

5. How your data is stored and protected

• Encrypted in transit. All traffic between you, the Connector, and the connected platforms travels over TLS (HTTPS).
• Protected at rest. Connected-platform OAuth credentials, including Google refresh tokens, are encrypted at the application layer before persistence. Other stored service data is protected by infrastructure access controls and tenant-scoped application controls.
• Access control. Access to stored tokens is restricted to the Connector processes that need them to serve your requests, and is scoped per customer.

No system is perfectly secure, but we apply industry-standard safeguards and keep the amount of data we hold to the minimum the service requires.

6. OAuth scopes granted and revocable by you

Every connection uses the platform's own OAuth consent screen, which shows you the exact scopes being requested before you approve. Authorization is entirely yours to grant and yours to withdraw:

• You can revoke access at any time from the platform's own security or connected-apps settings (for example, your Google Account permissions, Meta Business settings, Microsoft account, or the equivalent page on each platform).
• You can also disconnect a platform from within the Connector.
• Once you revoke, the underlying tokens stop working immediately and the Connector can no longer reach that account.

7. Retention and deletion on disconnect

• Connected-platform credentials are kept only while a connection is active. When you disconnect through AdvisorPPC, we delete the associated stored credentials promptly. If you revoke access at the provider, the provider tokens stop working; use AdvisorPPC disconnect or contact us to remove the local connection record.
• Account and performance data is fetched as needed. Short-lived account caches are cleared on disconnect. If a broader feature stores user-created configuration or derived records, those records remain until they are deleted through that feature or through a deletion request.
• Tool-call telemetry expires automatically. General observability telemetry rows are deleted no later than 30 days after creation. A deployment may configure a shorter period from 1 to 30 days. Purging runs when the service starts and at least hourly while it is running. This limit applies whether or not a platform remains connected.
• Full deletion on request. Email support@advisorppc.com and we will delete the data we hold for you, except where we are required to retain limited records by law.
• Meta deletion requests. When Meta sends its authenticated User Data Deletion callback, we remove the matching Meta credential and return an opaque confirmation code and status URL. The receipt does not contain the raw Meta user ID.

8. Your rights

Depending on where you live, you may have the right to access, correct, export, or delete the personal data we hold, and to withdraw consent. Because the data we hold is tied to accounts you control, you can exercise much of this directly through the connected platforms. For anything held by the Connector, contact us and we will respond within a reasonable time.

9. Changes to this policy

If we make a material change, we will update the "Last updated" date above and, where appropriate, notify connected users. Continued use of the Connector after a change means you accept the revised policy.

10. Contact

Questions, data requests, or deletion requests:

support@advisorppc.com

← Back to overview  ·  Terms of Service

AdvisorPPC MCP Connector. This policy covers the Connector only; data handling inside the connected advertising and analytics platforms is governed by each platform's own privacy policy.