Privacy Policy

Overview

MCP for Adobe Premiere Pro is an open-source, local-first connector. In the recommended setup, the MCP server and Adobe connector run on your computer. Project files, prompts, media, timelines, and exports are not automatically uploaded to us. Your chosen AI assistant and any remote MCP host have their own privacy practices.

MCP operational telemetry

Telemetry is disabled when the server has no POSTHOG_API_KEY. When an operator enables it, the server may send PostHog operational events such as connection attempts, request or tool names, outcomes, status codes, duration, server version, environment, region, transport, and an operator-provided or generated server identifier.

The telemetry implementation excludes authentication tokens, IP-address properties, prompts and MCP arguments, project paths, media names, tool results, and person profiles. Operators of separately hosted instances control their own configuration and retention.

Website analytics

The public website loads Google Analytics and PostHog after the page is interactive and idle. Google Analytics uses IP anonymization. PostHog is configured without autocapture, session replay, or person profiles, and does not include IP-address properties. Both record page views and bounded setup interactions such as the route, selected assistant, download action, or help panel opened. These events are designed not to include prompts, project details, media names, or file paths. Analytics providers may process device, browser, approximate location, and interaction information under their own policies.

When a homepage experiment is enabled, PostHog assigns an anonymous visitor to a page design. After that design is displayed, the website records the variant and a limited set of setup actions, including download clicks and successful copies of the safe connection prompt. The prompt text, your clipboard contents, project data, footage, IP-address properties, and person profiles are not included in these experiment events. Download clicks measure interest in setup; they do not establish that installation or a Premiere connection succeeded.

Cookies and choices

Analytics services may use cookies or similar browser storage. You can block or clear them using your browser controls or content-blocking tools. PostHog is not loaded when the browser sends Do Not Track or Global Privacy Control. Local MCP operators can keep operational telemetry off by leaving POSTHOG_API_KEY unset.

The homepage experiment uses a first-party, signed, HTTP-only cookie named premiere_homepage_v1 to keep an anonymous visitor’s assignment consistent and connect subsequent setup actions to that exposure. It expires after 30 days without renewal. Website analytics and experimentation respect Do Not Track and Global Privacy Control signals. Direct design previews do not enter the experiment.

Retention and sharing

We use collected analytics only to understand reliability, adoption, and setup problems. We do not sell personal information. Analytics providers process data on our behalf under their terms and retention settings. Local project and media data remains subject to the settings of your computer, Adobe software, AI assistant, and any services you choose.

Requests and contact

To ask a privacy question or request access or deletion where applicable, email leancoderk@gmail.com. Because analytics identifiers are not connected to an account, we may need information from you to locate a record and may be unable to identify anonymous data.

Changes

We may update this policy when the product or its data practices change. The date above identifies the current version.