PIIP – PII Protection

PIIP (PII Protection) is a plugin that automatically detects and masks personally identifiable information (PII) in WordPress comments and community plugin content before the data is saved to your database. This helps protect user privacy and supports your compliance efforts under privacy regulations such as the GDPR. Note that PIIP is a technical tool and does not by itself make your site GDPR compliant.

Key Features

• Automatic PII Detection: Intelligently detects multiple types of PII including emails, phone numbers, addresses, credit cards, SSN/My Number, passwords, API tokens, IP addresses, and hosting account IDs

• Server-Side Masking: All masking happens on the server (PHP) for maximum security – cannot be bypassed by users

• WordPress Core Support: Native support for WordPress comments – from the comment form, the REST API (including block editor notes) and later edits – with per-type selection (comments, product reviews, notes, other types)

• Commenter IP Anonymization: Optionally store commenter IP addresses anonymized (192.0.2.123 → 192.0.2.0), the same way WordPress anonymizes them for personal data erasure

• Inquiry-Style Text Protection: Catches contact details posted to a forum by mistake instead of a contact form – labeled names, furigana, addresses, phone numbers, member/login IDs, card expiry dates and security codes (お名前：… / 住所：… / Name: … / Address: …)

• Full-Width Aware: Full-width digits and symbols typed with a Japanese IME (０９０－１２３４－５６７８, ｔａｒｏ＠ｅｘａｍｐｌｅ．ｊｐ) are detected; text outside masked parts keeps its original width

• Image Location Removal: GPS coordinates and author/device identifiers are removed from uploaded photos (JPEG, WebP, PNG, HEIC/AVIF) without re-encoding – WordPress otherwise keeps them in the original upload and, with ImageMagick, in every resized copy

• Abilities API: piip/mask-text and piip/scan-content abilities let MCP clients and AI agents mask text and audit stored content without ever receiving raw PII

• Community Plugin Support: Works seamlessly with wpForo, BuddyPress, bbPress, and other popular community plugins

• Configurable: Choose which PII types to mask via easy-to-use settings page

• Consent Opt-Out: Users can include consent phrases to skip masking when sharing personal info publicly

• Presidio-Level Detection: High-accuracy detection with validation (Luhn for credit cards, check digits for My Number)

• Retroactive Scan: Scan content that existed before installing PIIP and apply masking after a dry-run review

• Custom Patterns: Mask site-specific identifiers (employee IDs, member numbers) with your own regular expressions

• WP-CLI Support: wp piip mask and wp piip scan commands for automation and large sites

Supported PII Types

• Email addresses ([email protected] → e***@domain.com)

• Phone numbers (Japanese mobile/landline, parenthesized 03(1234)5678, toll-free/navi dial 0120/0570, international, US formats)

• Japanese street addresses in free text (東京都新宿区西新宿2-8-1 → 東京都 ) and labeled postal codes (〒123-4567 → 〒 -****)

• Credit card numbers with Luhn validation (4532-1234-5678-9014 → ****-****-****-9014)

• Social Security Numbers / Japanese My Number with check digit validation

• Passwords, including labeled values in free text (password: xxx / パスワードは xxx / PW: xxx → [REDACTED]) and pasted configuration (define( ‘DB_PASSWORD’, ‘…’ ), SMTP_PASSWORD=…, aws_secret_access_key = …)

• HTTP credentials: Basic auth (curl -u, Authorization: Basic, user:pass@host URLs) and Bearer tokens (including JWTs)

• Developer secrets: GitHub, GitLab, Slack (tokens and webhooks), Discord webhooks, AWS, Stripe, Google OAuth, SendGrid, npm, Twilio, Mailgun, Shopify, Telegram, DigitalOcean tokens and SSH/PEM private key blocks

• API Tokens/Keys (partial masking showing first and last 4 characters)

• AI API Keys (OpenAI sk-***, Anthropic sk-ant-***, Google AIza***, Hugging Face hf_***, Replicate r8_***, Cohere, Azure OpenAI)

• Labeled dates of birth (生年月日: 1990-01-15 → ****- – )

• Labeled bank account numbers (口座番号: 1234567 → ***4567)

• Labeled contact details in inquiry-style text: name, furigana, address, phone, member/login ID, card expiry and security code (お名前：山田 太郎 → お名前：山* 太*)

• Labeled ID document numbers: passport, driver’s license, health insurance, basic pension, residence card

• Japanese addresses written without the prefecture, for designated cities and Tokyo’s 23 wards (横浜市中区山下町1-2-3 → 横浜市***)

• Names in self-introduction phrases (山田太郎と申します → 山***と申します; opt-in, off by default)

• IP Addresses: IPv4 (192.168.1.1 → 192...1) and IPv6, including compressed forms (2001:db8::8a2e:370:7334 → 2001:db8:***)

• Hosting Account IDs (XServer, Sakura, AWS, Azure, GCP, ConoHa, Lolipop, mixhost)

Supported Integrations

• WordPress Core

• Comments (comment form, REST API, edits; selectable types: comments, product reviews, block editor notes, other types)

• Commenter IP addresses (optional anonymization)

• User Profiles (display name, nickname, biographical info)

• Form Plugins

• Contact Form 7 (free-text fields; protects sent mail and stored copies such as Flamingo)

• Community Plugins

• wpForo Forum

• BuddyPress

• bbPress

• More integrations coming soon!

How It Works

• User posts a comment or content in a community plugin

• PIIP intercepts the submission before database save

• Automatically detects PII using field names, regex patterns, and validation

• Masks detected PII according to your settings

• Content saves normally with masked data

Privacy & Security

• All processing happens on YOUR server (no external API calls)

• Original values are NEVER stored for maximum privacy protection

• Server-side processing prevents client-side bypass attempts

• Full control over your data

Privacy Policy

PIIP – PII Protection does NOT:

* Send any data to external servers

* Track users

* Use cookies

* Share data with third parties

PIIP DOES:

* Process content locally on your server

* Automatically mask PII without storing sensitive data

* Optionally anonymize the IP addresses stored with comments

Support

For support, bug reports, or feature requests:

com/benridane/piip

Development

Development happens on GitHub. Pull requests welcome!

* Follow coding standards

* All code must pass composer run phpcs