Legal

Privacy Policy

Last updated 2 November 2026 · Version 1.9

This Privacy Policy explains how WPTerminal ("WPTerminal", "we", "us", or "our"), the data controller for the Service, collects, uses, discloses, retains, and protects information when you use the WPTerminal website, the WPTerminal Model Context Protocol (MCP) server, the WPTerminal WordPress connector plugin, and associated services (collectively, the "Service").

WPTerminal connects frontier AI models (such as Claude Desktop, ChatGPT, Cursor, Windsurf, Cline, and autonomous agents) to self-hosted WordPress websites that you authorize. Because WPTerminal enables AI assistants to inspect, analyze, and manage WordPress content, settings, and code at your explicit instruction, this policy describes both your WPTerminal account data and the WordPress metadata and tool results that pass through our platform.

Key Principles

  • Zero AI Model Training: We never sell personal information, and we never use your WordPress site content, files, orders, or database data to train AI models.
  • Stateless Passthrough Bridge: WPTerminal acts as a secure, authenticated bridge. We process WordPress content and tool parameters only as required to execute the actions you or your AI agent request.
  • Envelope Encryption at Rest: WordPress Application Passwords and site credentials are encrypted at rest with versioned AES-256-GCM envelope encryption cryptographically bound to your organization and site identity.
  • Human Governance & Approvals: Potentially destructive or sensitive actions (such as publishing posts live, running WP-CLI commands that change the site, trashing posts, or installing plugins) require approval by an authorized member of your organization, either for that one action or, for routine kinds of action, for up to 30 days on one site. The most sensitive actions are approved one at a time.
  • Complete Control & Deletion: You can disconnect sites, revoke access tokens and approvals, manage team members, or ask us to delete your account at any time. Audit records are append-only and are deleted automatically after 6 months on the Free plan and 12 months on paid plans.

1. Information We Collect and Process

A. Account and Team Information

When you register for WPTerminal, we collect your email address for passwordless sign-in with one-time email codes. When you create or join an organization, we store organization names, membership roles (Owner, Admin, Operator, Editor, Viewer), and team invitation records. Team invitations may include scoped site access specifying which WordPress sites an invited team member is authorized to manage.

B. WordPress Site Connection Credentials

When you connect a WordPress site, you approve the connection on WordPress's own Authorize Application screen, and WordPress issues an Application Password named WPTerminal on your own WordPress account. No WordPress user is created, and we never see your WordPress login password. We store your site URL, friendly site name, connector version, and the encrypted Application Password. All credentials are encrypted using AES-256-GCM authenticated encryption with tenant context binding, ensuring ciphertext cannot be decrypted across organizations or sites. The Cmdlane Agent Link plugin keeps a receipt of each signed change for 7 days and, for changes that can be undone, a snapshot of the earlier content for 30 days. Both stay in your own WordPress database and are not sent to WPTerminal.

C. OAuth Authorizations & Access Controls

When you connect AI assistants (such as ChatGPT, Claude Desktop, Cursor, or Windsurf), authorizations are granted through standard OAuth 2.1 with PKCE, without exposing account passwords. Where access credentials are stored, we store only deterministic cryptographic SHA-256 digests or AES-256-GCM encrypted secrets bound to tenant context.

D. Audit Logs and Operation Summaries

To maintain accountability and security, WPTerminal records an append-only audit trail of actions executed through the platform. Logs record the tool name (such as get_post, flush_cache, or propose_action), timestamps, execution duration, success/failure status, and a redacted input/output summary. Sensitive values, passwords, and tokens are automatically scrubbed before persistence. If a connected WordPress site is later deleted, historical audit entries preserve the historical site URL to keep activity logs coherent without retaining orphaned site records. Audit entries are kept for 6 months on the Free plan and 12 months on paid plans, and are then deleted automatically. A small number of authorized WPTerminal staff can see account, organization, site and usage information (not your site content or credentials) to operate, secure and support the Service. Every such access is recorded in an internal audit log. When you request a sign-in code we record your email address and when you asked, so we can see sign-ups that were not completed; if you never sign in, this record is deleted after 12 months. We send product updates only if you opt in on the sign-in page or in Settings, and every such email includes an unsubscribe link.

E. Billing and Payment Information

Paid subscriptions are sold and processed by Freemius, our reseller and merchant of record. Freemius collects your payment details, billing address and tax information under its own privacy policy. WPTerminal does not collect or store card numbers or banking details; we receive only your email address, license and subscription identifiers, plan, renewal dates and billing status from Freemius.

F. Skills, Preferences, Inquiries and Background Jobs

We store the following so the features that use them work:

  • Saved skills: the instructions your organization saves for its AI agents (title, name, text, who created or last changed them). Do not put passwords or keys in a skill: connected AI assistants read its text. Skills are kept until you delete them or your organization.
  • Preferences: your chosen time zone for dates in the dashboard, and whether you receive product updates.
  • Contact form inquiries: your name, email, company, plan of interest, number of sites, message and, if you answer it, how you heard about us. We use them to reply and to understand where inquiries come from.
  • Background multi-site jobs: the action and its arguments, the sites it runs on and each site's result. To run a job after your chat closes, we keep the ID of the access token that started it (never the token itself) and re-check that it is still valid before every step. Finished jobs are deleted automatically after 12 months, or earlier with your organization.

2. How We Use Information

We use the information we collect strictly to:

  • Authenticate your account and verify authorization for connected AI clients.
  • Route and execute Model Context Protocol (MCP) tool requests to your WordPress sites.
  • Enforce permission boundaries, human approval requirements, and tenant isolation.
  • Deliver transactional notifications, including sign-in codes and team invitations via Resend.
  • Maintain audit logging and security observability for your organization.
  • Prevent abuse, protect against server-side request forgery (SSRF), and enforce multi-tier rate limits.
  • Manage billing and plan quotas through Freemius.

3. AI Client Data Processing & Third-Party Services

When you connect an AI assistant (such as ChatGPT, Claude, Cursor, Windsurf, or Cline) to WPTerminal, that assistant requests tool executions with specific parameters, and WPTerminal returns formatted data from your WordPress site.

Please note that your use of third-party AI assistants is governed by the respective terms and privacy policies of those AI providers. WPTerminal does not control how third-party AI providers handle the data they receive once returned to them.

We rely on trusted enterprise infrastructure sub-processors to operate WPTerminal:

  • Vercel: Application hosting, edge computing, and MCP server gateway.
  • Supabase (PostgreSQL): Multi-tenant database storage with encrypted secrets.
  • Freemius: Reseller and merchant of record for paid subscriptions: payments, tax, invoices and the billing portal.
  • Resend: Transactional email delivery for sign-in codes and invitations.
  • Upstash Redis: High-throughput distributed rate limiting and concurrency enforcement.
  • Sentry: Telemetry and error reporting, configured with strict client-side, server-side, and edge redaction of authorization headers, tokens, and PII.

Some tools call outside services when you or your AI assistant use them. Nothing is sent to these services unless the tool is used:

  • Google PageSpeed Insights (run_lighthouse_audit): the address of the public page being audited is sent to Google, which loads the page and returns a Lighthouse report. Google's Privacy Policy applies to that request. Only pages on your connected sites can be audited.
  • Openverse (search_openverse_images), the WordPress.org project for openly licensed media: the search words are sent to the Openverse API. No account or site information is included.
  • Your own WordPress site (fetch_page_html, read_media_pdf and the checks around multi-site changes): WPTerminal requests public pages and media files from your site the way a visitor would. The page HTML, the PDF text or the check result is returned to your AI assistant and recorded in the audit log only as a summary; the page and the file themselves are not stored.

4. Security Measures

Security is foundational to WPTerminal. We implement robust defense-in-depth controls:

  • SSRF Guard: Outbound requests strictly validate destination URLs, block private network addresses (RFC 1918), loopback, link-local, and cloud metadata IP ranges, and require HTTPS in production.
  • Cryptographic Context Binding: Stored credentials use AES-256-GCM envelope encryption authenticated against organization and site IDs to prevent cross-tenant key re-use.
  • Deterministic Token Hashing: Personal Access Tokens and session secrets are stored as SHA-256 digests; raw tokens cannot be recovered from our database.
  • Multi-Tier Rate Limiting: Enforces quotas per organization, IP address, and site concurrency to prevent abuse.
  • No Code or SQL Execution: The WordPress plugin never edits PHP code, never runs SQL sent by an AI assistant and never starts a process. Plugins and themes are installed only from the WordPress.org directory, and only when administrative tools are on and a person approved it in the dashboard. Options that may hold keys or passwords are never read.

5. Data Retention, Control, and Deletion

You maintain full ownership of your data and can exercise control at any time:

  • Disconnecting Sites: Disconnecting a site from the WordPress plugin or the WPTerminal Dashboard immediately revokes and deletes active site credentials.
  • Audit Logs & Approvals: Activity and approval records are append-only, so they stay a reliable record of what happened. They are deleted automatically after 6 months on the Free plan and 12 months on paid plans, or with your account if you ask us to delete it.
  • Revoking Authorizations: Connected AI assistants and access authorizations can be revoked instantly in Settings.
  • Account Deletion: You may request full account and organization deletion by contacting us at [email protected]. Upon verification, all associated tenant data, credentials, and settings will be permanently removed.

6. Your Rights

Depending on your location (including the European Economic Area under GDPR and California under CCPA/CPRA), you may have statutory rights regarding your personal information, including the right to access, rectify, export, restrict processing of, or delete your personal data. To exercise any of these rights, please contact us at [email protected].

7. Contact & Updates

We may update this Privacy Policy periodically to reflect changes in our practices or legal obligations. We will notify you of material changes by updating the "Last updated" date at the top of this page or via in-app notification.

If you have any questions or concerns regarding this policy, please contact us at:

WPTerminal

Email: [email protected]

Website: wpterminal.com