Skip to main content

Data and retention

What is sent to Wigoh​

Site URL, site name, WordPress version, PHP version, database table prefix, plugin version, the site's public key, the environment verdict with its evidence, and (when you acknowledge a live site or approve a release) your WordPress user ID, display name and email.

During a snapshot: a complete copy of the site's database (including users and options) and wp-content directory.

During a release: the drift report (changed post IDs and titles, option names, plugin slugs) and the health-check result.

The update check sends only the installed plugin version. Every request except the update check is signed with the site's private key.

What Wigoh fetches from your site​

/wp-json/wigoh/v2/challenge/{id} once during verification, and /wp-json/wigoh/v2/wake to prompt the plugin to poll while a release is active.

Where it is stored​

Snapshot and release files are stored in a private Wigoh bucket on Google Cloud Storage. The plugin uploads to, and downloads from, short-lived private addresses that Wigoh creates for your site's own files.

Retention​

  • Snapshot files: deleted 30 days after upload.
  • Release files: deleted 90 days after they are built.
  • On your server: the previous tables and files kept for rollback are removed 7 days after a release goes live or is rolled back. Failed export work directories are removed after 2 days. Old job rows after 30 days.
  • Connection metadata (site URL, versions, public key, environment verdict) and release history stay with your Wigoh account until you delete the project or the account, or ask Wigoh to delete them.

Tracking​

The plugin contains no analytics, tracking pixels or telemetry, and makes no request before you connect other than the update check.

Sign-in​

Signing in to approve a connection happens in your browser on Wigoh's account hub. The plugin itself never contacts it.