# WordPress security plugin data: what it keeps about people

See what BetterShield keeps about people, how long each record lasts and what an erasure request removes, using Site Health and WordPress’s own tools.

By M Asif Rahman, Nov 22, 2026.

To see what a WordPress security plugin keeps about the people on your site, open **Tools › Site Health › Info** and expand **BetterShield: what it keeps about people**. It lists each kind of record **BetterShield** holds about a person, how long the record is kept, and whether an erasure request removes it. It describes the records only, so nobody’s own data appears in it.

Our guide to [what a WordPress security plugin sends off your site](/blog/what-wordpress-security-plugins-send/) covers the outside services. This post covers the other half of the privacy question: what stays on your own server, for how long, and what happens when someone asks to be erased.

## Quick summary

- The **Site Health** section is added while BetterShield is active. There is nothing to set up, and opening or copying it changes nothing.
- BetterShield never stores a whole IP address. It keeps the network: the first three groups of an IPv4 address, or the first four of an IPv6 address.
- Sign-in attempts are kept for two days. Activity log rows are kept for 30 days, or 90 days with BetterShield Ultra.
- WordPress’s **Export Personal Data** and **Erase Personal Data** tools include BetterShield’s records, and the erasure result says what was kept and why.
- **Share usage data** is the one optional report to WPDeveloper. It is off by default, and turning it off stops later reports.

## Why it matters

A security plugin has to remember some things about people in order to protect them. It needs to know who signed in, from which network, and what changed. That is personal data in the ordinary sense of the term, as the definition of [personal data](https://en.wikipedia.org/wiki/Personal_data) puts it: information about an identifiable person.

The useful question is not whether a plugin keeps any of it, but whether it tells you plainly what, for how long, and what you can remove. Someone preparing a privacy review, answering a request from a customer or filling in a client questionnaire needs a page they can read, not a promise. WordPress documents how plugins are expected to contribute to that in its [plugin privacy handbook](https://developer.wordpress.org/plugins/privacy/), and the Site Health section is BetterShield’s place in it.

## What the Site Health section shows

Open **Tools › Site Health › Info** and expand **BetterShield: what it keeps about people**. For each kind of record it gives three things: what is kept, how long, and whether an erasure request removes it. **How long the activity log is kept** states the current retention period for your site, so it tells you whether you are on the 30-day or the 90-day setting.

The section describes the data model. It does not list activity rows, account details, networks or anyone’s values. That makes it safe to copy into a ticket, a privacy review or a diagnostic note, and we recommend copying only what the purpose needs. The full reference is [the Site Health data details guide](/docs/site-health-privacy-info/).

### Set it up

There is nothing to switch on. To read it:

1. Open **Tools › Site Health** in your WordPress admin.
2. Select the **Info** tab.
3. Expand **BetterShield: what it keeps about people**.
4. Compare **How long the activity log is kept** with the retention shown on **BetterShield › Activity › Site activity**. They should match.

## What is kept about people

This table is the shape of that section, taken from BetterShield’s personal data reference. IP addresses are always stored as a network, never whole.

| Record | How long it is kept | On an erasure request |
|---|---|---|
| Sign-in attempts under the account’s username: when, how, the outcome, the network | Two days | Removed |
| Activity log rows where the account acted, or that are about it | 30 days, or 90 with Ultra | Kept, with the person’s name and network taken out |
| Two-factor: the secret behind the app’s codes, and hashes of the backup codes | Until two-factor is turned off | Removed, which turns two-factor off |
| Passkeys: the device name, when added and last used, and the public half of the key | Until the passkey or the account is removed | Removed |
| The network each open session started from | Until the session ends | Kept; WordPress removes it with the account |
| The date the account last signed in | Until the account is deleted | Kept |
| Incident evidence naming the account by number, never by name | While the incident is open; once handled, 30 days, or 180 with Ultra | Kept |
| Small marks, such as a recent password confirmation or a dismissed notice | Varies | Removed |

The reference page adds a few more rows, such as lockout records and assistant connections, and the Site Health section lists every one on your own install. A file-editor row keeps the plugin or theme name and the file’s path, never the contents.

If you turn on **Save old values so I can undo changes**, the earlier values it saves can include an email address. They stay until BetterShield is uninstalled with its records removed. If you use that feature, [our guide to undoing setting changes](/blog/wordpress-record-previous-values/) explains what it saves.

## What an erasure request does

In **Tools › Erase Personal Data**, BetterShield removes what belongs to the person and keeps what belongs to the site’s security record, taking the person out of that record where it can.

- **Removed:** passkeys, sign-in attempts, two-factor (the person sets it up again if they keep the account) and the small marks above.
- **Kept, with the person taken out:** activity rows lose the name and network but still say what happened.
- **Kept as they are:** the last sign-in date, lockout records, incident evidence and the other records marked kept in the table.

The answer WordPress shows for the request says what was kept, and why. The reasoning is simple: a security log that could be emptied on request is one an intruder holding that account could empty. Because rewriting activity rows would break their daily seals, BetterShield seals those days again and the log still reads as intact. How the seals work is in our [WordPress activity log guide](/blog/wordpress-activity-log/).

## Export a person’s data

In **Tools › Export Personal Data**, the file WordPress builds includes BetterShield’s records for that person, in groups named **BetterShield activity**, **BetterShield account**, **BetterShield sessions**, **BetterShield passkeys**, **BetterShield sign-in attempts** and **BetterShield incident evidence**. A last group, **What BetterShield keeps about you**, lists each kind of record held about that account, why it is kept, how long, and what an erasure would do. Times are in UTC, and networks are labeled as networks so nobody reads them as an address.

## The one optional report: Share usage data

Everything above stays on your server unless you connect BetterShield Hub. The one thing you can choose to send to WPDeveloper is the daily usage report. It is under **BetterShield › Settings › General › Privacy & sharing › Share usage data**, and it is off by default.

When it is on, BetterShield sends a short report at most once a day, and once on deactivation. It includes the site address and title, the administration email, software versions, language, installed plugins and the theme. It does not include visitors, users, passwords, security events or file contents. **What we collect** lists the fields, so review it before you decide. The row shows when the last report was sent or why one failed, and a failed report is tried again on the next daily run. The details are in [the Share usage data guide](/docs/share-usage-data/).

Turning the switch off stops later reports but cannot recall one already sent. On multisite, the report describes the network and only a super administrator can change the answer.

## What it can break, and how to undo

Reading the Site Health section, exporting a person’s data and choosing the usage setting change nothing about how your site behaves. The things that do change something are the ones you choose to do:

- **An erasure request** removes what the table marks as removed. Two-factor for that account is turned off, so the person sets it up again if they keep the account. Removed records are not restored by BetterShield.
- **Share usage data** can be switched off at any time, though a report already sent stays sent.
- **Deactivating BetterShield** removes the Site Health section but does not itself erase stored plugin data. What deletion leaves behind is a separate choice, covered in [Choose what plugin deletion leaves behind](/docs/deletion-data-choice/).

## Check it is working

- **The section opens.** Expand **BetterShield: what it keeps about people** on the **Info** tab and confirm it lists the record types.
- **Retention matches.** The value under **How long the activity log is kept** should match **BetterShield › Activity › Site activity**.
- **The export names BetterShield.** Run **Export Personal Data** for a test account and look for the **What BetterShield keeps about you** group.
- **The policy text is current.** WordPress’s **Policy Guide** carries BetterShield’s suggested text under **BetterShield**. Your published policy does not change by itself, so copy the text again after you change what the site contacts.

## Recommended settings

| Situation | What we recommend |
|---|---|
| Preparing a privacy review | Copy only the lines you need from the Site Health section |
| A site with a strict privacy policy | Leave **Share usage data** off, and review **What we collect** before ever turning it on |
| Answering a person’s request | Run **Export Personal Data** and **Erase Personal Data** and keep the result WordPress shows you |
| A site on Ultra | Remember the log is kept 90 days and incident evidence 180, and say so in your policy |

We are describing how the plugin behaves, not giving legal advice. Check your own obligations with whoever advises you on them.

## Frequently asked questions

### Does a security plugin have to keep personal data?

To protect a site it records some: who signed in, from which network, and what changed. What matters is that it says plainly what, for how long, and what you can remove.

### Does BetterShield store full IP addresses?

No. It keeps the network instead: the first three groups of an IPv4 address, or the first four of an IPv6 address.

### How long does BetterShield keep the activity log?

30 days, or 90 days with BetterShield Ultra. The Site Health section states the current period under **How long the activity log is kept**.

### What does an erasure request remove?

Passkeys, sign-in attempts, two-factor and small marks such as a dismissed notice. Activity rows stay, with the person’s name and network taken out, and a few security records are kept on purpose. The result WordPress shows says which.

### Is anything sent to WPDeveloper by default?

The daily usage report is off until you choose it. For everything the plugin contacts out of the box, see [What BetterShield contacts](/docs/what-bettershield-contacts/).

## Conclusion

BetterShield keeps what it needs to protect a site, tells you what that is in one place, and answers to WordPress’s own export and erase tools. Open **Tools › Site Health › Info** once, read the section against your privacy policy, and decide whether **Share usage data** should stay off. BetterShield is free on [WordPress.org](https://wordpress.org/plugins/bettershield/), and the full reference is [Privacy and personal data](/docs/privacy-and-personal-data/).
