by
miya
1 (0 reviews)
PIIP - PII Protection
Automatically detects and masks PII in WordPress comments and forms to protect user privacy and support your GDPR compliance efforts.
PIIP ranks #68,476 among WordPress.org plugins with 1+ active installations, is #2,855 of 5,058 in the Security category, a 1/5 rating from 0 reviews, and was last updated Oct 3, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.8.0
Current Version v1.8.0
Updated 1 month ago
Last Update on 03 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#2,855 of 5,058 in Security
Rank
#68,476
—
No change
Active Installs
1+
—
No change
KW Avg Position
52
2 worse
Downloads
233
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
55,539
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 9 more installs to reach 10+
Rank Changes
Current
#68,476
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.8.0
- Last Updated
- Oct 03, 2026
- Requires WP
- 6.9+
- Tested Up To
- 7.1
- PHP Version
- 8.2 or higher
- Author
- miya
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about PIIP - PII Protection
Yes! PIIP has native support for WordPress core comments. Simply enable the Comments integration in Settings → PII Protection. Comments are masked whether they are submitted through the comment form, created through the REST API (for example by headless front ends or apps), or edited later. You can choose which comment types are masked: regular comments, product reviews (e.g. WooCommerce), block editor notes (off by default, as they are internal editorial comments), and other types such as pingbacks.
Yes. Photos taken with phones usually record where they were taken. WordPress keeps the original upload unchanged and publicly reachable, and on servers using ImageMagick every resized copy (including thumbnails) keeps the location too. With "Remove location" enabled (the default), PIIP removes GPS coordinates (EXIF and XMP) and XMP location fields from JPEG, WebP, PNG and HEIC/AVIF files as they are uploaded through WordPress, before thumbnails are created. "Remove author and device IDs" also removes the author, owner name and camera/lens serial numbers, and keeps the author out of the media data the REST API returns. The image itself is not re-encoded: only the metadata bytes are overwritten, so quality, orientation, color profile, camera model and date are preserved. Existing images can be checked and cleaned under Tools > PII Scan (target "Images") or with wp piip scan --target=images --apply. Files uploaded by plugins that bypass the WordPress upload functions (for example Contact Form 7 attachments) are not covered, and what is visible in the picture itself is of course not changed.
Yes. Set "Commenter IP addresses" to "Anonymize before saving" in Settings → PII Protection. The last part of the address is zeroed (192.0.2.123 becomes 192.0.2.0; IPv6 keeps the first 48 bits) for new and edited comments. Existing comments are not changed. Because the address is anonymized rather than removed, WordPress flood protection keeps working, per network block instead of per address.
Yes. With "Labeled contact details" enabled (the default), labeled fields typical of inquiry forms are masked: お名前/氏名, フリガナ, 住所/お届け先, 電話番号/TEL/携帯, 会員番号/ログインID, 有効期限, セキュリティコード and their English equivalents (Name, Address, Phone, Member ID, Expiry, CVV). Email addresses, postal codes, dates of birth, bank accounts and passwords in the same message are masked by their own types. Bare 名前/Name labels are only recognized at the start of a line, so technical text such as 変数の名前: foo is left alone.
Yes. PIIP registers two abilities with the WordPress Abilities API: piip/mask-text masks a piece of text with your site's settings (users who can edit posts), and piip/scan-content runs a read-only scan of stored comments or posts (administrators). Results contain masked text and PII types only, never the raw values. They are available through the Abilities REST API and to MCP adapters that expose public abilities.
Yes! PIIP has native integration with wpForo and will automatically mask PII in forum topics, posts, and private messages.
Yes! PIIP supports BuddyPress activities, profile fields, private messages, group descriptions, and activity comments.
Yes. If enabled, users can include consent phrases like "マスクを外すことに同意" or "I consent to unmasking" in their content to skip PII masking for that specific post.
No. PIIP adds minimal processing time (<20ms per submission) which is imperceptible to users. All processing happens server-side after submission.
No. All masking happens on the server (PHP), so it cannot be bypassed by disabling JavaScript or using browser developer tools.
