miya

<p>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 ensures GDPR compliance.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Automatic PII Detection</strong>: 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</li>
<li><strong>Server-Side Masking</strong>: All masking happens on the server (PHP) for maximum security – cannot be bypassed by users</li>
<li><strong>WordPress Core Support</strong>: Native support for WordPress comments</li>
<li><strong>Community Plugin Support</strong>: Works seamlessly with wpForo, BuddyPress, bbPress, and other popular community plugins</li>
<li><strong>Configurable</strong>: Choose which PII types to mask via easy-to-use settings page</li>
<li><strong>Consent Opt-Out</strong>: Users can include consent phrases to skip masking when sharing personal info publicly</li>
<li><strong>Presidio-Level Detection</strong>: High-accuracy detection with validation (Luhn for credit cards, check digits for My Number)</li>
</ul>
<h4>Supported PII Types</h4>
<ul>
<li>Email addresses (example@domain.com <span aria-hidden="true" class="wp-exclude-emoji">→</span> e***@domain.com)</li>
<li>Phone numbers (Japanese mobile/landline, international formats)</li>
<li>Addresses (masked to ***)</li>
<li>Credit card numbers with Luhn validation (4532-1234-5678-9010 <span aria-hidden="true" class="wp-exclude-emoji">→</span> ****-****-****-9010)</li>
<li>Social Security Numbers / Japanese My Number with check digit validation</li>
<li>Passwords (masked to [REDACTED])</li>
<li>API Tokens/Keys (partial masking showing first and last 4 characters)</li>
<li>AI API Keys (OpenAI sk-***, Anthropic sk-ant-***, Google AIza***, Hugging Face hf_***, Replicate r8_***, Cohere, Azure OpenAI)</li>
<li>IP Addresses (192.168.1.1 <span aria-hidden="true" class="wp-exclude-emoji">→</span> 192.<strong><em>.</em></strong>1)</li>
<li>Hosting Account IDs (XServer, Sakura, AWS, Azure, GCP, ConoHa, Lolipop, mixhost)</li>
</ul>
<h4>Supported Integrations</h4>
<ul>
<li><strong>WordPress Core</strong>
<ul>
<li>Comments</li>
</ul>
</li>
<li><strong>Community Plugins</strong>
<ul>
<li>wpForo Forum</li>
<li>BuddyPress</li>
<li>bbPress</li>
</ul>
</li>
<li>More integrations coming soon!</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>User posts a comment or content in a community plugin</li>
<li>PIIP intercepts the submission before database save</li>
<li>Automatically detects PII using field names, regex patterns, and validation</li>
<li>Masks detected PII according to your settings</li>
<li>Content saves normally with masked data</li>
</ol>
<h4>Privacy & Security</h4>
<ul>
<li>All processing happens on YOUR server (no external API calls)</li>
<li>Original values are NEVER stored for maximum privacy protection</li>
<li>Server-side processing prevents client-side bypass attempts</li>
<li>Full control over your data</li>
</ul>
<h3>Privacy Policy</h3>
<p>PIIP – PII Protection does NOT:<br />
* Send any data to external servers<br />
* Track users<br />
* Use cookies<br />
* Share data with third parties</p>
<p>PIIP DOES:<br />
* Process content locally on your server<br />
* Automatically mask PII without storing sensitive data</p>
<h3>Support</h3>
<p>For support, bug reports, or feature requests:<br />
* Website: https://github.com/benridane/piip</p>
<h3>Development</h3>
<p>Development happens on GitHub. Pull requests welcome!<br />
* Follow coding standards<br />
* All code must pass <code>composer run phpcs</code></p>


PIIP – PII Protection

Automatically detects and masks PII in WordPress comments and forms to protect user privacy and ensure GDPR compliance.

WebDefender Security – Protection & AntiSpam vs PIIP – PII Protection