Your auditor asks what keeps PII out of your logs. Hand them the answer instead of writing it the week before the audit. Everything is built for the PII-Shield engine you already run — drop-in config, no upgrade, no new infrastructure.
EU-specific data formats: names, addresses, IBAN, national ID formats, phone numbers. Every rule is validated against the PII-Shield test suite before delivery — not regexes copied off a blog.
What is redacted, how, and where the boundaries are — written so you can hand it to your DPO or auditor as-is, instead of translating configs into compliance language yourself.
Evidence templates for GDPR and SOC 2 prep: what to capture, where redaction happens in your pipeline, and how to show it stayed on.
Versioned changelog. When a new leaky pattern shows up, you get the tested rule — not a TODO.
$149 one-time · early access
Delivered as a ZIP to your email within 5 business days of purchase. Drops into your existing PII-Shield config.
Payment via PayPal · 14-day money-back guarantee — reply to the delivery email, no
form, no questions.
Not sure it fits your setup?
Email one question
before buying.
No. PII-Shield stays Apache-2.0 and fully functional. The pack adds curated GDPR rules and the paperwork layer on top of it.
Yes — that's what most teams do, the week before the audit, and then explain them to the auditor in their own words. The pack is the tested version of that week, plus the explanation.
The rules work anywhere the PII-Shield engine runs: the K8s sidecar, the operator, or the WASM build embedded in your own pipeline.