← All guides

WordPress: Data protection self-test with WP-CLI

Requirement

Use WP-CLI with read access to the WordPress installation in question.

Record active plugins and in particular identify analytics, security, form, CAPTCHA, newsletter and cache/proxy extensions. Then don't make a general judgment based on the plugin name, but instead check the respective configuration with the appropriate instructions.

The specific read-only commands are collected under Check the website yourself.

Rate result

A single hit is a technical finding. Then check the purpose, actual storage, transfer and retention period of the affected level separately.

Classify in the overall check

This individual test only covers one level. Then systematically check the remaining levels using the checklist for unnecessary visitor data .

Related guides

• WordPress: Configure WP Statistics to save as much data as possible
• WordPress: Configure Burst Statistics to save data
• WordPress: Classify independent analytics in a data protection-conscious manner
• WordPress: use Antispam Bee with data minimisation

Sources and verification

This guide is based on multiple current sources. Vendor documentation is not treated as proof that every concrete installation automatically follows the same privacy characteristics.

• Self-test
• Inspection checklist

Important: IP processing is not IP storage

An IP address has to be processed to establish and deliver a network connection. Hosting providers, firewalls or DDoS protection may also process or retain it for a limited time for security purposes. No Logging distinguishes this security layer from unnecessary persistent visitor logging by the website, application and ordinary access logs.