Privacy Policy
This policy explains what data the theMarketer MCP Server (https://mcp.themarketer.com/mcp) processes when you connect it to an AI assistant such as Claude, ChatGPT or OpenClaw. It supplements the general theMarketer Privacy Policy, which continues to apply to your theMarketer account and the data stored in it.
1. What the MCP Server does
The MCP Server is a gateway between your AI assistant and your existing theMarketer account. It exposes theMarketer features (subscribers, campaigns, e-commerce data, reports, transactional messaging and others) as tools that the assistant can call on your behalf. It does not create a new copy of your theMarketer data and it does not train or operate any AI model itself.
2. Authentication
Access is granted through OAuth 2.1. When you connect, you sign in with your theMarketer ID on theMarketer's own authentication service and approve the requested scopes. The MCP Server never sees your password. It receives access and refresh tokens, which it stores encrypted at rest and uses only to call the theMarketer API on your behalf. You can revoke access at any time by disconnecting the connector in your AI assistant.
3. Data we process
| Data | Purpose | Stored by the MCP Server? |
|---|---|---|
| Your theMarketer user ID and the domain(s) you act on | Authorization, scoping every request to your account | Yes, in request logs |
| OAuth client registrations, access and refresh tokens | Keeping your connection alive | Yes, encrypted |
| Tool name and arguments needed for your requested marketing action (such as contact email, phone, name, consent, birthday, campaign content, order amounts and ordinary marketing custom fields) | Executing the action you request | Argument values are not stored in tool-call logs; logs retain only a redaction marker and argument count |
| Tool results returned from theMarketer | Answering the request | No, passed through only |
| Tool name, outcome, error class, argument count, duration, trace and session identifiers, client user agent | Reliability monitoring and support | Yes, in request logs |
| Your conversation with the assistant | - | No, never received |
The MCP Server only receives the specific tool calls the assistant makes. It has no access to the rest of your conversation, the assistant's memory or your files.
Depending on the action, results may include existing contact profiles (including location, gender or birthday), marketing consent, engagement and purchase history, loyalty data, product reviews, campaign content and aggregate reports. These are used only to answer your request or perform the marketing action you authorize. Contact-detail sections can be requested individually to limit disclosure.
Restricted data: Do not provide medical or biometric data, government identifiers, payment-card information, passwords, API credentials or authentication codes through this connector, including custom fields, tags, message bodies or attachments. Such data is outside this connector's supported purpose. Authenticate through OAuth and configure integration credentials in the authenticated theMarketer web app. The connector does not offer fields for API keys or passwords, and its billing tool returns plan and usage totals rather than billing identity or payment details.
The connector does not accept raw residence/location fields when creating, updating, listing or importing contacts. Manage residence data in the authenticated theMarketer web app; select existing segments for geographic audiences. You must be authorized to use the contact data and have the necessary marketing consent before subscribing contacts or sending messages.
4. Your AI assistant provider
Tool calls and their results travel through the AI assistant you use (for example Anthropic for Claude, or OpenAI for ChatGPT). How that provider handles the data is governed by its own privacy policy and your agreement with it. We recommend reviewing those terms, in particular regarding data retention and model training.
5. Third-party sharing
Tool inputs and results are exchanged with theMarketer systems and your chosen AI assistant provider. When you request a send or trigger a messaging automation, message content and recipient details are also processed by the configured delivery providers and delivered to the intended recipients. Feed tools instruct theMarketer to access the feed URLs you supply. Infrastructure providers hosting the MCP Server act as processors under contract; the MCP Server does not sell your data.
6. Retention
- Request logs are kept for 90 days and then deleted. Older records created before this policy revision may contain tool arguments under the previous logging behavior; the new redaction does not rewrite existing records.
- OAuth tokens are kept until they expire or until you disconnect the connector, whichever comes first.
- Data held in your theMarketer account follows the retention rules of the general theMarketer Privacy Policy.
7. Security
All traffic is encrypted in transit (HTTPS). Tokens are encrypted at rest. Access to request logs is restricted to authorized theMarketer staff for support and security purposes.
8. Your rights
Depending on where you live you may have the right to access, correct, delete or export your personal data, and to object to or restrict its processing. Requests regarding the MCP Server can be sent to the contact below; requests regarding your theMarketer account follow the general Privacy Policy.
9. Contact
theMarketer · privacy@themarketer.com
10. Changes
We may update this policy as the MCP Server evolves. The date at the top shows the latest revision.