Privacy: Check that plugins handling personal data call wp_add_privacy_policy_content()

Summary

The WordPress Plugin Handbook requires that every plugin which collects, uses, stores, or passes personal data to a third party should suggest privacy policy text to site administrators using wp_add_privacy_policy_content(). See: https://developer.wordpress.org/plugins/privacy/suggesting-text-for-the-site-privacy-policy/

In practice the vast majority of plugins that handle personal data do not implement this, leaving site administrators without the information they need to write an accurate privacy policy.

What to check

Plugin Check should detect when a plugin appears to handle personal data — indicated by usage of functions or patterns such as:

• wp_remote_post() / wp_remote_get() sending data to external URLs
• setcookie() or $_COOKIE
• $_POST / $_GET handling personal fields (email, name etc.)
• Loading external scripts or pixels (see #1156 / #475)

...and warn if wp_add_privacy_policy_content() is not called anywhere in the plugin.

Start with the WordPress Plugin Handbook guidance linked in the issue, then review the listed patterns: wp_remote_post(), wp_remote_get(), setcookie(), $_COOKIE, $_POST, $_GET, external scripts, and pixels. Done means Plugin Check identifies plugins that appear to handle personal data and warns when wp_add_privacy_policy_content() is not called anywhere.