GoBuildWP refund policy and purchase support.

What a GoBuildWP Pro refund changes on your WordPress site

The GoBuildWP refund policy above covers money. This part covers the site, because a refund or a cancelled licence has a visible effect in wp-admin and it is better to know it in advance than to discover it mid-task.

GoBuildWP Pro does not decide for itself whether it may run. At the top of the plugin it asks the bundled Freemius SDK whether this site may use the paid code. Freemius answers from the licence record stored on the site, which it re-syncs in the background and whenever you press "Sync licence": yes for an active paid licence or a trial, no once the licence is cancelled or deactivated on the site, and, after the expiry date stored for a yearly licence passes, the answer Freemius gives for that licence. GoBuildWP sets no grace period of its own. When the answer is no, Pro returns before loading its abilities, admin screens or memory store, so nothing paid is left for an AI agent to reach.

Two cases are easy to confuse. A missing or broken Freemius SDK, or a Pro build without its licensing identifiers, is treated as unlicensed straight away. A site that simply cannot reach Freemius is not switched off by that alone, because the stored licence is what gets checked; it cannot activate a key or pick up a renewal, refund or cancellation until it can reach Freemius again.

What stays is the free plugin. GoBuildWP Free does not depend on Pro, so its abilities, its safety profile, its change ledger and its connection settings carry on exactly as before. Two things are worth checking on a site that relied on Pro features:

• If "Require approval for writes" was switched on, the approval queue is a Pro feature. With the licence inactive, agent writes that would have been held are refused rather than waved through, and read-only abilities keep working. Turn the requirement off or renew before expecting agent writes to succeed.
• If the fresh-backup gate was switched on, destructive and critical agent calls keep being refused until a supported backup plugin reports a recent successful backup, licensed or not. Switch the gate off in Pro's settings while the licence is active, or keep backups current.
• Pro's own records, such as agent memory and approval policy, stay in the database while Pro is merely inactive, so a later renewal picks them up again.
• Deleting Pro from the Plugins screen runs its cleanup, which removes the options and records Pro wrote under its own names. It never touches data that belongs to Elementor, WooCommerce, an SEO plugin or any other integrated plugin: pages and products Pro edited on your behalf remain yours and remain in place.

GoBuildWP Cloud when a linked licence is no longer active

GoBuildWP Cloud has no price of its own, so there is nothing in Cloud to refund. A Pro licence linked to your account at app.gobuildwp.com raises the number of sites Cloud will route to and adds bulk actions; without an active licence the account returns to the free allowance of 3 connected sites.

Cloud does not delete anything when that happens. Sites beyond the allowance, starting with the most recently connected, are marked "Over plan limit" on the dashboard and calls to them are refused with a message saying the site is over the plan's site limit and asking you to disconnect a site or link a Pro licence. They come back as soon as the allowance covers them again, and each one is re-checked at that moment so a site that went down or had its key revoked in the meantime is reported accurately. A direct connection between an AI client and a site never passed through Cloud, so it is unaffected by any of this.

Annual, lifetime and tier changes: what the checkout records

Every Pro tier is sold in two billing cycles, yearly and lifetime, and each tier unlocks the same Pro plugin features for a different number of site activations. The checkout link on the pricing page fixes the site count to the tier you chose, so the allowance on the receipt is the allowance you selected, and it asks Freemius to show the renewal amount alongside the first payment. That is deliberate: the renewal figure is part of what you are agreeing to, and it should be on screen before you pay rather than in an email a year later.

A lifetime licence has no renewal to cancel. A yearly licence renews until you cancel it in the Freemius customer portal, and cancelling stops the next charge without shortening the period already paid for. When a licence changes in any of these ways, press "Sync licence" on GoBuildWP > Licence so the site reads the new state at once instead of at its next scheduled check.

A pre-purchase check that can save a refund request

A purchase review is often about fit rather than a defect: the companion plugin was older than Pro supports, the AI client could not reach the site, or the workflow needed something GoBuildWP does not do. Those three can be checked before any money changes hands, on the free plugin and a staging copy of the site. Free cannot show you Pro's own abilities at work, so for the Pro-only part of a workflow the check is the edition label and requirements, not a trial run.

• Install GoBuildWP Free, open GoBuildWP > Diagnostics and run it with the sign-in method your client will use. Then connect the real client and have it complete one read, which proves the transport works from your network rather than only from the server.
• Look up each plugin you expect Pro to drive on its integration page. Pro enforces minimum versions for several of them, and an integration below its floor is skipped by design rather than half-loaded.
• Read the edition labels in the ability reference. If the task you are buying Pro for needs a specific ability, confirm it exists and which edition it belongs to.
• Ask before paying if a boundary matters to the decision. A question sent through contact costs nothing; a refund depends on terms GoBuildWP does not set.

What GoBuildWP can and cannot do with a refund request

GoBuildWP reviews the technical side of a request and can say whether a problem is a product defect, a fix that is already in a newer release, or something outside the plugin. The financial decision and the refund itself go through Freemius under the terms recorded with your transaction, because Freemius is the merchant of record and holds the payment. GoBuildWP never sees or stores your card details, and cannot move money outside that platform.

When the review finds a genuine defect, the usual outcome is a fix rather than an argument about eligibility. Neither plugin is distributed through WordPress.org: both check the GoBuildWP website for new versions, so a corrected build is offered on the normal WordPress updates screen of every licensed site, and the changelog records what changed. If waiting for that release is not acceptable to you, say so in the same thread; the request is still assessed under the transaction's own terms.

To identify the purchase without exposing anything, use the licence number shown after the # sign on Licences in your GoBuildWP account, or the masked key from GoBuildWP > Licence on the site. Either is enough for the licence to be found; the full key is never needed and should not be sent.