Black Friday Sale is Live: Get up to 30% OFF RankReady Pro - the WordPress AI SEO pluginBlack Friday Sale is Live: Up to 30% OFF Get Deal
Getting Started

How to Uninstall Hatch Connect Cleanly

Remove Hatch Connect from WordPress without leftovers: what deleting the plugin always removes, the Remove all data option, and what stays in Cloudflare.

Last updated October 30, 2026

By the end of this guide you will have removed Hatch Connect from WordPress and know exactly what was deleted, what you can choose to keep, and what you must clean up yourself.

Deactivate or delete?

Hatch’s uninstall routine runs only when you delete the plugin from Plugins, Installed Plugins. Deactivating or updating it removes nothing.

What is always removed

Credentials and live connections never outlive the plugin. Deleting Hatch always removes:

  • The encrypted deploy token and every stored secret (webhook, revalidate, JWT, AI key), plus the Turnstile secret key.
  • Cloudflare deploy state, connection and heartbeat state, and legacy options.
  • Every hatch_* transient, every scheduled Hatch cron event and the Hatch block in uploads/.htaccess.
  • The user name and encrypted Application Password the frontend used.
  • The leftover Hatch Reader role and its settings, if you ran an earlier build that added them. Hatch Connect 1.0.0 does not create a Reader user. Any user that still has the old role is kept, without a role, for you to delete.
  • The optional URL rewriter mu-plugin (hatch-url-rewrite.php), but only a copy Hatch wrote. A file anyone else wrote is kept.

What is removed only if you ask

If you tick Remove all data on uninstall before deleting, Hatch also removes every remaining hatch_* option (settings, design, SEO and form settings), the form submissions table, stored submission posts and Hatch user meta.

Uninstall step by step

  1. Optional: open Hatch, Connection and press Disconnect first, so the redirect stops. See disconnect Hatch.
  2. If you want no settings left behind, tick Remove all data on uninstall and save.
  3. Go to Plugins, Installed Plugins, deactivate Hatch Connect, then click Delete.
  4. Go to Users, Profile for the frontend’s account and revoke its Application Password. Hatch never created it, so it does not delete it.
  5. Delete the Worker in your Cloudflare account under Workers & Pages. Hatch does not touch it.
  6. Revoke the Cloudflare API token in your Cloudflare profile if you no longer need it.
Hatch Connection tab
After a deploy, Disconnect is on the Connection tab (shown here before setup).

What to do next