The gateway keeps a narrow data boundary

The public Gigacatalyst MCP gateway receives bounded setup facts and typed tool arguments needed to prepare a campaign preview. It does not require raw conversation history or model memory. Connection credentials are secrets: they must stay in the user's private MCP configuration and must never be placed in prompts, tool arguments, URLs, logs, repositories, analytics properties, or shared files.

Operational records exclude campaign content

Operational signals may contain opaque request, journey, installation, session, artifact, and correlation identifiers; tool names; timing; warning counts; and safe error codes. They do not include prompts, messages, generated campaign copy, bearer values, raw attribution identifiers, email addresses, or phone numbers. Authentication failures do not reveal whether another user's credential exists.

The main policy still governs the service

This page explains the gateway-specific boundary. Read the full Gigacatalyst privacy policy for company-wide collection, use, retention, legal rights, and contact information. Send privacy questions to support@gigacatalyst.com without including credentials or private customer information.