Privacy policy.

This website

wpmcp-pro.com is a marketing and documentation site. We do not ask you to create an account here, and we do not knowingly collect names, email addresses, or other personal details unless you choose to email us or fill out a form we may add in future. If and when we add analytics to this site, we will update this policy first and describe exactly what is collected, the cookies it sets, and how to opt out.

Right now, this site sets no tracking cookies and loads no third-party analytics scripts. It is a static site with self-hosted fonts and images. Demo videos on this site are hosted on YouTube and load only after you click play; until then nothing is requested from YouTube, and once you click, the privacy-enhanced embed is used and YouTube's own privacy policy applies from that point.

The WP MCP plugin, on your WordPress site

WP MCP (the marketing name for the open-source pluginwpmcp) runs entirely inside your own WordPress installation. This section explains what that means for your data. It follows the Privacy and External services sections of the plugin's own readme, which is the authoritative text and is updated with every release.

The core privacy fact: the plugin collects nothing about you and sends nothing to us. WP MCP does not operate a separate server that stores a copy of your site. Every snapshot, every log, and every piece of content the plugin touches lives in your own WordPress database, on your own hosting, under your own control. Its only scheduled task is a daily local cleanup of expired OAuth tokens; nothing on the schedule ever makes a network request, and neither does activation.

What the plugin stores, and where

WP MCP keeps copies of site data it needs to work. All of it stays on your site:

• Undo snapshots of what an agent changed, saved before every write. These can include users, comments, orders and form entries, because those are the things agents edit. They power one-click rollback.
• The request and governance audit logs: which tool ran, on which object, in which session, when, where the call came from, and every governance decision.
• Agent memory entries (proposed by agents, live only once an administrator approves them) and thecontent search index.
• Your chat conversations with the in-admin AI chat, on Pro.

All of these take part in WordPress's own personal data tools.Tools > Export Personal Data lists a person's records from each store, and Tools > Erase Personal Data redacts them from undo snapshots (a redacted snapshot can no longer be rolled back, and says so), anonymizes them in the logs, and deletes the memory and index entries that hold them and their chat conversations. WP MCP's erasure runs after your other plugins' own, so their copies in WP MCP's snapshots are covered too. Site backup archives made by WP MCP are full database copies and are left unchanged; the erasure says so when any exist.

Licensing: the Freemius opt-in

Licensing through Freemius is opt-in and inactive until you connect it. On activation Freemius shows its stock opt-in screen, which defaults to off and carries a Skip link. Skip or decline it and no connection is made, no licence data is exchanged, and the plugin keeps working. Once you have opted in, there or later from the WP MCP > Account page, the Freemius SDK talks to api.freemius.com during admin page loads and its own periodic sync. One path is independent of that choice: the optional deactivation feedback form on the Plugins screen. If you submit it, the reason you enter is stored locally and sent to Freemius when the plugin is deleted; if you also untick "anonymous feedback" on that form, your display name and email are sent as well. We do not collect usage analytics from your site unless you explicitly opt in to something that says so.

Every external service the plugin can reach

Each request below happens only while you or your agent are running the ability that needs it, with two exceptions, both noted. Nothing is sent to us.

• api.wordpress.org and downloads.wordpress.org.Core checksums for the security scan; the plugin directory's "closed plugin" check; plugin and theme directory search, install and update (directory slugs only, never an arbitrary zip URL); core language packs when you select a locale that is not installed; the official WordPress package for a core update or for a core-file reinstall during incident response.
• www.wpvulnerability.net. Only when the security scan is run with vulnerabilities on: it looks up core, each plugin and each theme in this free, public database, sending the WordPress version and slugs, never your versions or site address. Answers are cached for a day.
• Openverse (api.openverse.org). The default stock image provider for search-stock-images. It needs no key, so it is not opt-in: running the search is what sends your search terms and paging.
• Pexels and Unsplash. Only when you have saved your own key for that provider and search it; the search terms, paging and your key are sent.
• api.freemius.com. Licensing, as described above. The one entry not tied to a tool.
• api.anthropic.com (Pro). The in-admin AI chat, opt-in and bring-your-own-key. Nothing is sent until an administrator saves their own Anthropic API key and sends a message; there is no shared or built-in key. Each chat step sends that key, a system prompt carrying the site name, site URL, their username and the names and schemas of the tools the chat may use, and the conversation so far, including the results of tools it ran, which can include site content. The key is stored encrypted per user and never sent to the browser.
• api.dataforseo.com (Pro). Keyword and backlink data for analyze-seo, opt-in and bring-your-own-key. Nothing is sent until an administrator saves their own DataForSEO login; then the keywords, location and language codes you ask about, or the domain or URL you name, go out with your credentials. Answers are cached for a day; the credentials are stored encrypted and never returned by any tool.
• The WordPress.org Pattern Directory (Pro). Only when a block-suite pattern browse or import names the "directory" source: search terms, category, paging and locale are sent, your site address is not, and pattern images are downloaded from WordPress.org's image hosts. Cached for an hour.
• Spectra's pattern library at websitedemos.net (Pro).Only when a pattern browse or import names the "spectra" source while Spectra is active: search terms, category and paging are sent, with no licence key, purchase key or site address. Cached for a day.
• WP MCP Cloud (the cloud URL you configure).Nothing is sent until you run cloud-connect with a cloud URL and API key you supply. After that, requests go only to that URL: the widget and block specs you push or pull, the governance, exposure, skills settings and identity scopes you sync (never passwords, keys or tokens), and marketplace listings you browse or install.Exception one: once connected, the announcements feed fetches notices (no site content) when an administrator opens a WP MCP screen, at most once a day.
• Your own migration target. push-site-archive sends a site-backup archive (the full database, including password hashes, and wp-content if included) to the target URL you supply, and only after you have allowed outgoing migrations with a constant. The receiving site's owner's terms and privacy policy apply.
• Allowlisted media hosts. import-stock-image and upload-svg download the file you picked from images.pexels.com, images.unsplash.com, plus.unsplash.com, upload.wikimedia.org and staticflickr.com, a list the site owner can change with a filter.
• Any host you name yourself. sideload-image passes the URL you supply to WordPress core's sideloader; upload-media with a URL downloads that one https file (private addresses and redirects refused); analyze-performance fetches the URL you measure. Disable the ability if you do not want that reach.
• The AI provider the site owner configured.sideload-image with a prompt generates the image through WordPress core's AI client (WordPress 7.0+) using whichever provider an administrator connected under Settings > Connectors. This plugin holds no AI key and adds no provider.
• MCP client metadata documents.Exception two: only when OAuth is switched on (it is off by default) and a client signs in with an https URL as its client ID, this site fetches that one URL, while a signed-in user authorizes the client, to read the client's name and allowed redirect addresses. Nothing about your site or its users is sent.
• This site itself. The connection self-test, the security scan's header check, the rendered-HTML reader and the analytics abilities call your own site's URL. These are loopback requests to your own server.

What connects to what

The plugin exposes your site's content and store data to whichever AI client you connect, over the Model Context Protocol. A client authenticates with OAuth 2.1 (PKCE), where you choose full or read-only access, or a scoped identity, when you approve it, or with a WordPress application password that you generate and can revoke at any time. OAuth is off by default and switched on by the site owner. That connection is between your WordPress site and the AI client you chose (for example Claude or Cursor); we are not a party to it, and we do not see the traffic. What that AI provider does with the data you send it is governed by that provider's own privacy policy, not this one.

Your responsibilities

Because WP MCP is self-hosted, you are the data controller for your own WordPress site. Which clients you approve, what access level they get, which application passwords exist, and what the AI is allowed to touch, are choices you make and control. We recommend approving each client with the narrowest access that does the job, using a dedicated user for agent access, and revoking a connection when it is no longer needed.

Emails you send us

If you email info@fahdmurtaza.com, we keep that correspondence to answer you and, occasionally, to improve documentation based on real questions. We do not add you to a marketing list from a support email, and we do not sell or share your email with anyone.

Third parties

The plugin's Pro tier, when purchased, is billed throughFreemius, our payment processor and merchant of record for that transaction; their own privacy policy governs checkout data. GitHub hosts our source code, releases and issue tracker; using GitHub is subject to GitHub's own privacy policy. YouTube hosts the demo videos described above.

Children

This website and the plugin are not directed at children, and we do not knowingly collect data from anyone under the age of 16.

Changes to this policy

We may update this policy as the site, the plugin, or the law changes. The "last updated" date above reflects the most recent revision. Material changes, such as adding analytics or telemetry, will be reflected here before they take effect.

Contact

Questions about this policy or your data? Emailinfo@fahdmurtaza.com. See also our terms of service, or readhow the safety model actually works under the hood.