Privacy
GoBuildWP privacy and AI data flow. What stays local, and what may reach your AI provider.
GoBuildWP does not bundle an AI model. A direct connection keeps your MCP tool calls off GoBuildWP's servers; GoBuildWP Cloud, if you choose it, passes them through a hosted gateway. Your AI client, and any provider you configure for Chat, can still receive site content. This page sets out each path.
MCP traffic and in-dashboard Chat
GoBuildWP connects systems you control: WordPress, an MCP client and, optionally, a configured AI provider. The exact processors and retention rules depend on the client, provider, hosting stack and settings chosen by the site owner. This notice explains those boundaries without promising that all content stays on your server.
External MCP client: your client owns model access
Claude, Codex, Cursor, Gemini or another compatible client connects to the GoBuildWP MCP endpoint. The client decides which model and provider handle the conversation; GoBuildWP exposes the allowed WordPress tools and returns tool results.
- Dedicated credentials are recommended.
- WordPress capabilities still apply.
- The safety profile and ability policy are enforced server-side.
- The client's and model provider's privacy terms apply.
WordPress Chat: your configured provider processes the prompt
The in-dashboard Chat sends a request through the provider and model configured in the WordPress AI Client. The request may include conversation context, attachments, system instructions, available tool declarations and tool results.
- Review the configured provider before enabling Chat.
- Avoid secrets and unnecessary personal data.
- Limit attachments to content needed for the task.
- Treat provider retention and training settings as separate controls.
What can be stored on your WordPress site
Exact persistence depends on the enabled feature and site configuration. Administrators should apply normal WordPress backup, access, retention and incident-response practices.
Sessions and settings
Chat sessions, provider and model selections, connection settings and feature configuration can be stored in WordPress so the selected workflow can operate. From GoBuildWP Free 1.18.0, Chat also counts each person's tokens per day, prompt and answer totals only and never their text, in that person's WordPress user data for 62 days, so the usage line and any Pro limits work. The counts stay on the site and are not sent to GoBuildWP.
Change evidence
GoBuildWP can record redacted change metadata and supported rollback evidence. Redaction reduces exposure; it is not a promise that every field is anonymous.
Credentials
Connection and provider credentials should be treated as secrets. Never paste them into prompts, public tickets, screenshots, analytics or support email.
GoBuildWP Cloud
GoBuildWP Cloud, at app.gobuildwp.com, is optional. It is a hosted account and MCP gateway: you connect WordPress sites to it from wp-admin, connect AI apps to it once, and calls from those apps pass through it to the sites. Without Cloud, the free plugin connects your AI client to the site directly and none of the records below exist.
What Cloud stores
- Your account email address and a hashed password.
- For each connected site: its URL, name, GoBuildWP versions and health.
- The key each site created for Cloud, stored encrypted.
- The AI apps you connected, the sites each may reach, and your personal access tokens, stored hashed.
- A log of gateway calls: the tool name, the site, the outcome, the time and any error message. Kept 90 days.
- Bulk runs (Pro), including updates, backups and safety-policy pushes started from Cloud: what ran, its arguments and each site's result. Kept 30 days after the run finishes.
- What each site last reported, from GoBuildWP Free 1.18.0: its pending core, plugin and theme updates with their versions; which backup plugins are active, the time and plugin of its newest successful backup, and whether one is running; and its safety settings, whether its owner lets Cloud manage them, and the Cloud policy it last applied. Each report replaces the last, and a site's last report stays with its record, even after you disconnect it, until your account is deleted.
- Safety policies you save (Pro): their names and settings and the sites each is assigned to, until you delete them.
- The people in your workspace with their roles and, for clients, the sites they may see; and invites: the invited email address, role, chosen sites and expiry date. Invites stay listed with the workspace after they expire, are withdrawn or are accepted, until your account is deleted.
- The SEO report (Pro): for each site, Search Console totals for the last 28 days and its top pages and queries with clicks, impressions, click rate and position, as the site's Google Site Kit returned them. Replaced at each refresh, about once a day, and kept with the site's record until your account is deleted.
- Sign-in sessions (browser name and a hashed IP address), and the callback address of any ChatGPT automation you set up, until it expires or you remove it.
What Cloud does not store
WordPress passwords, and your pages, posts or products: single tool calls and their results pass through the gateway between your AI app and your site without being stored; the log above records that a call happened, not its content. The exceptions are a bulk run, whose per-site results are kept 30 days, and the SEO report, which keeps page addresses and search queries with their figures, both as listed above. Your AI app and its model provider still receive what the tools return, under their own terms.
Cloud never receives backup archives, download links or the credentials of your backup storage: a backup started from Cloud is made by the backup plugin on the site and goes wherever that plugin sends it. Cloud never holds a Google sign-in or token: the SEO report is read by each site through its own Google Site Kit plugin, whose Google connection stays on the site.
Control and deletion
Each site decides the access Cloud has, Read Only or Production Safe, and its safety profile, confirmations and change ledger still apply to every call. Disconnecting a site in Cloud or in wp-admin stops its key working. If a GoBuildWP Pro licence is linked to your Cloud account, the licence email and status are used to set your site limit. Retention jobs are configured for the periods above and require an operating worker. Closing your Cloud account revokes site credentials immediately and schedules the remaining account records for purge after seven days; audit rows containing identifiers can remain (Settings → Delete account, or email support@gobuildwp.com).
Services that process Cloud data
Cloud runs on hosting and database services and sends account email through a transactional email service, of the same kinds listed under website services below. Contact us for the current service inventory.
Content, support and commerce data
Staff edit blog content in the GoBuildWP admin. Your GoBuildWP account at app.gobuildwp.com uses your email address, a password, session cookies and operational records to provide Cloud, licence linking and support. Freemius handles payment and licence issuance; synchronised customer and entitlement metadata can also be held by GoBuildWP.
The support form collects your email, optional name, request category, product, subject and message, plus any site URL or version details you choose to include. Email confirmation helps prevent unsolicited requests. Do not include secrets or customer records.
Website services and what each is used for
These website services are separate from the AI client and model provider you choose for your own WordPress site.
Checkout and licences
Freemius provides checkout, payment processing, invoices, downloads and licence services. GoBuildWP can synchronise purchase email, name, licence status, plan and install metadata to support entitlement and customer requests. We do not ask you to send card details or licence keys in a ticket.
Website delivery and email
Cloudflare provides network and security services. Hosting, database, configured media storage and transactional email services process the requests or records needed to deliver the website, account emails and support replies. Contact us for the current service inventory or a data-processing question.
Optional analytics
If enabled and accepted, Google Analytics measures public pages and evaluation actions. Google receives network and device information as part of those requests. Our event mapping does not include your support text, credentials, licence keys or WordPress content. Essential account cookies are not analytics consent.
Opt-in plugin reports
When an administrator enables plugin reporting, GoBuildWP can receive an install identifier, site URL, software versions and usage and environment details. This is not anonymous simply because no account login is required. The retention job is configured to roll detailed reports into daily totals after 90 days and remove installs silent for 400 days. Scheduled-job operation must be maintained by the deployment operator.
Retention, access and deletion
Support conversations and customer records are retained for operating support, account access and purchase administration, with any necessary dispute, security or record-keeping requirements considered separately. There is no claimed universal deletion deadline for every provider. Email support@gobuildwp.com to request access, correction, deletion or a current retention explanation; we may need to verify ownership. Deleting a website account is separate from deleting your WordPress data or records held by Freemius and your AI provider. If you are unhappy with how we handle your data, you can complain to the UK Information Commissioner's Office (ico.org.uk) or your local data protection authority.
Who we are and how to ask
GoBuildWP, is the controller of the personal data described on this page and handles it under UK data protection law (UK GDPR and the Data Protection Act 2018). For a product privacy or data-flow question, email support@gobuildwp.com. Include the GoBuildWP version, the feature, client and provider involved, but never credentials or private content. Related: security and disclosure, terms of service.
Checked against the plugin source
What the GoBuildWP plugin sends to the GoBuildWP website, and when
The GoBuildWP privacy policy above describes services. This section narrows it to the free plugin running on your site, because that is the part you can inspect yourself. Two kinds of request leave a WordPress site for the GoBuildWP website (gobuildwp.com; plugin builds released before the rename send the same requests to our former domain, which we also operate), and only one of them is optional.
The update check is not optional, because it is how a plugin distributed outside WordPress.org learns that a new release exists. It asks the GoBuildWP website for the current release information and passes the installed GoBuildWP version as its only query parameter. It goes through WordPress's own HTTP functions, which by default identify the request with the WordPress version and the site's home address, as they do for every plugin and theme update check.
Usage reporting is optional and off unless an administrator switches it on under GoBuildWP > Settings, with the toggle labelled "Send anonymous usage data once a day". A fresh install sends no usage report; update requests are separate. When switched on, the daily report contains:
- the site address and a random installation identifier generated on the site, so an install that moves from http to https is not counted twice;
- the GoBuildWP, WordPress and PHP versions and the site locale;
- whether GoBuildWP Pro is active and which safety profile is selected;
- the number of recorded AI-client connections.
Turning reporting off, and what it does not contain
The report contains no usernames, email addresses, post or page content, or record of what an AI client did. Switching the toggle off sends one final message asking for the reports already collected to be deleted, rather than only stopping future reports, and the retention described above applies to anything kept until then. Because the report carries the site address, "anonymous" here means it is not tied to a person's account, not that it cannot identify a site.
Your site's own privacy tools include GoBuildWP
Records GoBuildWP keeps in the WordPress database are covered by the tools WordPress already gives site owners. The plugin adds suggested text to Settings > Privacy > Policy Guide, describing its connection history, change ledger, Chat storage, OAuth records and access tokens, so a site's own privacy notice can be accurate without guesswork. It also registers "GoBuildWP data" with the personal-data export and erase tools under Tools, so a request about a user's data includes the GoBuildWP records linked to that user's email address.
Some values are deliberately kept in a form that cannot be handed back. An access token is stored as a one-way digest with its name, last four characters and timestamps; the token itself is never stored and cannot be exported. OAuth client registrations keep a one-way hash of the registering IP address rather than the address.
Removing GoBuildWP removes what it stored
Deleting the free plugin from the Plugins screen runs its uninstall routine, which drops the plugin's own database tables for chat sessions, connections, tokens, the change ledger and OAuth records, and deletes its options. Two things are left on purpose because they are your work rather than plugin state: PHP files written through the sandbox stay in their folder under wp-content, and saved designs and skills are kept unless the site has opted into deleting them on uninstall. Nothing outside GoBuildWP's own prefixes is touched.
GoBuildWP Pro does the same for its own records when it is deleted, and leaves pages, products and settings belonging to the plugins it edited where they are. Deactivating either plugin, as opposed to deleting it, removes nothing. Data already sent to an AI client or provider, to Freemius or to GoBuildWP Cloud is outside the reach of an uninstall and has to be dealt with at that service.
FAQ
Privacy questions
Does GoBuildWP include or operate an AI model?
No AI model is bundled with the plugin. External MCP clients use their own model connection. GoBuildWP's in-dashboard Chat uses the AI provider and model configured through the WordPress AI Client.
Can Chat content leave my WordPress site?
Yes. When you submit an in-dashboard Chat request, the configured provider may receive the prompt, conversation history, attachments, instructions, available tool declarations, and tool results needed to answer. Review that provider's terms, retention settings, and regional controls before use.
What does GoBuildWP Cloud keep?
Only if you use it: your account email and hashed password, each connected site's URL, name, versions and health, the site keys encrypted, your AI app connections, a log of gateway calls with the tool name, site, outcome and time, and what each site last reported about its pending updates, newest backup and safety settings. With Pro it also keeps your safety policies, bulk and update runs, and each site's Search Console summary. Your team members and invites are kept with the workspace. Gateway logs are kept 90 days and bulk-run results 30 days; the rest until it is replaced or your account is deleted. It does not store WordPress passwords, backup archives, Google tokens, or page content except what a bulk run or the SEO report returns. Without Cloud, none of this exists.
Where are MCP credentials controlled?
Credentials are configured on the WordPress installation and remain subject to WordPress user capabilities, the selected GoBuildWP safety profile, enabled abilities, confirmation rules, and rate limits. Use a dedicated credential with the smallest useful permission set.
Where is customer account and licence data handled?
Freemius processes checkout, payments, invoices and licence issuance. GoBuildWP also operates its own customer account at app.gobuildwp.com, which signs in with your email address and a password and uses emailed links to confirm an address, reset a password or link a licence; it holds Cloud, licence linking and support requests. Its operational database can store customer contact details, licence and install metadata synchronized from Freemius, support conversations, and hashed sign-in/session tokens. This is separate from staff content records; it is not a second store of your Freemius password or payment-card details.
What does the GoBuildWP content database store?
The staff content service stores articles, help documents, release notes, media metadata, redirects, keyword briefs, revisions and editor accounts. Separate operational tables support customer sign-in, support, licence synchronization and opt-in plugin reporting. Access is restricted by the relevant staff or customer permissions.
Does this website use analytics or advertising code?
Optional Google Analytics is loaded only when a measurement ID is configured and you choose Allow analytics. Declining leaves it unloaded. Public-page and evaluation-link events exclude query strings and form contents; private account and support-request routes are not measured by this integration. Your choice is stored in this browser and can be changed using Analytics preferences. Essential hosting/security logs and account cookies operate separately.
How do I ask a privacy or data-flow question?
Email support@gobuildwp.com with the product version, the feature or provider involved, and the question. Do not include passwords, API keys, application passwords, private site content, or other secrets.