A default install of WellTend Health Monitor sends nothing to any third party. Its only outside-looking requests go from your server to your own site (listed below). It has no telemetry, no analytics, no remote configuration, and loads no remote fonts or images. This page lists everything that can leave your site, and what it stores.
What can leave your site#
| What | Where it goes | When |
|---|---|---|
| Local checks, error log reading, history, the score | Nowhere. It stays in your database. | Always |
| A secure connection to your own site, to read the certificate date | Your own site, not a third party | Daily. Can be switched off. |
| One request to your own site asking for the address of your error log, to see whether anyone could download it. Only the first few bytes are read. | Your own site, not a third party | Daily. Can be switched off per check. |
| WordPress's own loopback, page cache, HTTPS and automatic updates tests, run for you in the background | Your own site, not a third party | Daily |
| The weekly report and the test email | Through your own site's mail setup, to the addresses you entered | Only after you switch the report on or press the button |
| The vulnerability lookup | WPVulnerability, a free public database | Only after you switch it on. Off by default. |
| WordPress's own update checks | WordPress.org | Always, but made by WordPress, not by this plugin |
The plugin also bundles an SDK from Freemius to prepare for an optional paid version. It stays inactive until product credentials exist, and when active it only asks permission first.
The one optional service: WPVulnerability#
WPVulnerability is a free, public database of known WordPress vulnerabilities, released under CC0.
- When: only after you turn on "Look up known security problems". At most once a day, and at most 40 requests per run.
- What is sent: one request per item. The address of the request contains only the slug of a plugin or theme that is listed on WordPress.org, for example
/plugin/akismet/, or your WordPress version, for example/core/7.1/. The request carries a plain User-Agent of the formAllWPCare-SiteHealthMonitor/<version>, no cookies, and no site address, site name, email or other identifier. - What is not sent: plugins and themes that are not on WordPress.org are never looked up.
- What they can see: like any web request, the service can see the IP address of your server.
If a lookup fails, the plugin backs off and never blocks its other checks.
What it stores#
- Settings, in one option. The recipients of the weekly report are the only personal data the plugin stores.
- Results and the score for each run, kept for 90 days by default (you can choose 30 to 365). Daily size measurements are kept for about 400 days. Error log counts are kept for 30 days.
- Up to 200 sample error messages. Samples are redacted before they are stored: email addresses, IP addresses, long tokens, values after
password=,key=ortoken=, and URL query strings are removed, and each sample is shortened. File paths are stored relative to your WordPress folder. - Counts of failed emails per day. No addresses or message bodies.
The error log screen shows raw entries to administrators only, and says so.
What it never does#
- It does not read your whole log file at once. Reading is bounded, incremental and redacted.
- It does not change your site. The only action that changes anything is "Clear the log file", after you confirm.
- It does not run on page loads. An hourly and a daily background task do the work, and a visit to your site makes no database query for this plugin.
Cleaning up#
Deleting the plugin removes its tables, options and scheduled events. Settings can be exported first with WellTend Snapshots, which includes them under health.settings.
The plugin also registers suggested text for your site's privacy policy page in WordPress.