WhoKnew Shield™ helps you protect contact information on your site from scrapers; it also includes features (especially in Pro) that process visitor data for security. This article summarizes what the plugin stores, where it’s used, and how that may relate to privacy and GDPR so you can inform your privacy policy and answer “what does Shield do with visitor data?” without opening a ticket.
Contact Protection (Obfuscation)
Shield’s contact obfuscation transforms your emails, phone numbers, and addresses in the HTML before the page is sent to the browser. That processing happens on your server using your content (stored in WordPress). The plugin does not send visitor data to a third party for this feature—it doesn’t collect or store visitors’ personal data for the purpose of obfuscation. So from a visitor’s perspective, simply viewing a page with protected contact info does not mean Shield is “collecting” their data for that feature. Your contact data remains under your control in your database; Shield only changes how it is output. You don’t need visitor consent for the obfuscation itself. If your privacy policy already describes how you use WordPress and what data your site collects, the addition of Shield for contact protection doesn’t typically require a new consent mechanism for that feature alone.
What Shield Stores (Server-Side)
Shield and Shield Pro store the following on your server (in your WordPress database and options):
- Your settings — Protection toggles, auto-detection options, Scraper Trap configuration, block duration, whitelist, custom block message, and (in Pro) license key and status. These are administrative data, not visitor personal data.
- Scraper Trap™ (Pro) — When the honeypot is triggered or an IP is blocked, the plugin can store IP address and related request information (e.g. user agent, referrer, time of hit, which trap was triggered). This is used to block abusive traffic, show you blocked IPs and trap stats in the dashboard, and send recovery emails to admins when a blocked user requests unblock. Retention is under your control: blocked IPs and hit logs stay in your database until you unblock, they expire (for temporary blocks), or you remove the data (e.g. via plugin uninstall or your own cleanup).
- Recovery flow (Pro) — When a blocked user requests a recovery link, the plugin stores a temporary token (linked to the IP) so the recovery link can be validated. That data is short-lived (e.g. about one hour). Admin email addresses are used to send the recovery link; they are not shared with third parties by the plugin.
- IP whitelist — IPs you add so they are never blocked. You decide which IPs to whitelist (e.g. your own, your team’s).
Shield does not send this data to WhoKnew’s™ servers for analytics or profiling. License activation and update checks communicate with the license server (license key, site URL, plugin version); that is account/license related, not visitor profiling.
Cookies
The plugin may set cookies in the admin area only (e.g. to remember that you dismissed an upsell or review notice). These are not used for visitor tracking or for identifying site visitors on the front end. If your privacy policy already covers WordPress admin cookies, you can treat these as part of that. The plugin does not set cookies on the front end for contact protection or for Scraper Trap blocking.
Privacy Policy and Consent
Under GDPR and similar laws, you are the data controller for the data your site collects and processes. Shield is a tool you use on your server; the data it stores (settings, IP blocks, trap hits, recovery tokens) is in your database. You decide what to tell users in your privacy policy. Many sites that use security or anti-abuse measures (such as IP blocking and request logging) describe this in their policy and rely on legitimate interest for the processing, without separate consent, because it is necessary for the security of the site. If you use Scraper Trap (Pro), consider adding a short note that you use a security feature that may log IP addresses and related request data to block abusive traffic and that this data is stored on your server. For contact protection, you typically don’t need to mention visitor consent, since the plugin isn’t collecting visitor data for that feature. If in doubt, consult your legal or privacy advisor.
Heads up: You are the data controller. Shield does not send visitor or block data to WhoKnew for analytics or advertising. If you use Scraper Trap, a brief note in your privacy policy that you log IP and request data for security and blocking abusive traffic is a good practice. For legal certainty in your jurisdiction, consult your privacy or legal advisor.
Need Help?
For what Scraper Trap stores and how blocking works: Getting Started with Scraper Trap, IP Blocking, and Blocked IPs Dashboard (Pro). For recovery and whitelist: Shield Recovery: Link Expired or Not Working and IP Whitelist (Pro). For license data: License Tab (Pro): What You See and What to Do.