PrivacyScrubber ZTDS Guard — GDPR & HIPAA Form Privacy, PII Redaction & Data Masking
PrivacyScrubber ZTDS Guard — GDPR & HIPAA Form Privacy, PII Redaction & Data Masking

PrivacyScrubber ZTDS Guard — GDPR & HIPAA Form Privacy, PII Redaction & Data Masking

0/5 (0 ratings) — active installs Updated Nov 12, 2026
Real-time client-side PII & PHI tokenization in WordPress forms (Contact Form 7, WPForms, Gravity Forms, Elementor, Fluent Forms) with the WCAG 2.1 AA ZTDS™ Verification Seal.

Real-time client-side PII & PHI tokenization in WordPress forms (Contact Form 7, WPForms, Gravity Forms, Elementor, Fluent Forms) with the WCAG 2.1 AA ZTDS™ Verification Seal.

Stop Storing Raw Client PII, Credit Cards, and Medical Details in Your WordPress Database—Without Breaking Your Sales & CRM Workflow.

Every time a visitor submits a form on your WordPress site, sensitive personal data (PII), payment card numbers typed into message boxes, national IDs, and protected health information (PHI) are normally saved in plain text inside your WordPress MySQL database (wp_postmeta, Flamingo, form entry tables) and forwarded across unencrypted emails, Slack channels, and AI chatbots. If your database is ever compromised via a third-party plugin vulnerability—or if a team member pastes a client inquiry into ChatGPT—your business faces immediate regulatory and breach exposure.

PrivacyScrubber ZTDS Guard brings Airplane-Mode Form Security (powered by the Zero-Trust Data Sanitization — ZTDS™ RFC v1.0 standard) to WordPress. It intercepts form submissions inside the visitor’s own browser memory (under 0.4ms) before fetch() or XMLHttpRequest sends data over the network.

How It Works in 3 Steps (Built for Non-Technical Teams & CISOs)

  1. Instant Browser Shield (Before Network Send): When a visitor clicks Submit, sensitive details (Names, Emails, Phone Numbers, Credit Cards, SSNs/National IDs, Bank IBANs, Medical Record Numbers) are detected locally in the visitor’s browser (window.crypto.subtle) and mapped into isolated tokens ([NAME_1], [EMAIL_1], [PHONE_1], [CREDIT_CARD_1], [SSN_1]).
  2. Smart CRM & Database Split (Zero Workflow Friction):
    • In Your WordPress MySQL Database (100% Zero-PII): All form entries saved in WordPress (ztds_encrypted_inbox, Flamingo, postmeta) store only masked tokens. Even if your database backup is leaked, attackers get zero raw personal data.
    • In Your Email & CRM (Smart CRM Mode — Default): Your sales, support, or clinic staff still receive the client’s working Name, Email (Reply-To), and Phone so they can reply in Gmail/Outlook or route leads into HubSpot, Pipedrive, or Salesforce immediately—while accidental high-risk secrets inside the message body (Credit Cards, SSNs, Passports, Bank Accounts, Medical IDs) remain safely masked as [CREDIT_CARD_1] or [SSN_1].
  3. 1-Tap Staff Lead Card (No wp-admin Login Required):
    • Every notification email includes a secure Open 1-Tap Staff Lead Card button (/?ztds_lead_card=1#ztds_seal=...).
    • Receptionists, account managers, doctors, or legal staff tap the link on their phone or desktop to view the decrypted inquiry in browser RAM—complete with 1-tap buttons for Call Client, WhatsApp Chat, Reply via Email, Save Contact (.vcf), Copy Full Lead, and AI-Safe Copy (pre-scrubbed with tokens so staff can safely paste the inquiry into ChatGPT, Claude, or Gemini).
    • Zero-Server Fragment Security: The decryption key is carried inside the URL #ztds_seal hash fragment, which browsers never send to the server over HTTP, and is automatically erased from the browser address bar (history.replaceState) the instant the card opens.

Why Tokens Never Collide or Mix Up Across Leads

  • Per-Submission Isolated Crypto Envelopes: [NAME_1] and [EMAIL_1] are never stored in a shared global table. Every single form submission generates its own unique cryptographic key/IV and its own self-contained encrypted dictionary (_ztds_vault_payload and #ztds_seal). Lead #1’s [NAME_1] and Lead #2’s [NAME_1] live in completely separate encrypted envelopes and can never overwrite each other.
  • Smart Name Field & Product Phrase Awareness: Dedicated Name fields deterministically capture single-word, lowercase, or multilingual names (Latin, Cyrillic, Hebrew) as [NAME_1], while built-in product/business phrase guards prevent capitalized product names (e.g., “Wooden Barrels”, “Custom Order”, “Best Regards”) from being falsely flagged as [NAME_2].

Step-by-Step Admin How-To Guide (Settings -> PrivacyScrubber ZTDS)

  1. Choose Your CRM & Email Routing Mode:
    • Smart CRM & Email Safe Mode (Recommended): Keeps Name, Email, and Phone readable for your CRM webhooks and Gmail Reply-To headers while masking high-risk secrets (Cards, SSNs, IDs, IBANs, Medical IDs) in messages and scrubbing 100% of PII into tokens inside WordPress MySQL.
    • Strict Zero-Egress Mode: Masks 100% of fields—including Name ([NAME_1]), Email ([email protected]), and Phone (+10005550001)—across all outbound emails and webhooks.
  2. Set an Optional 1-Tap Staff Card PIN:
    • Enter a 4–8 digit team PIN in 1-Tap Staff Card PIN (Optional) if you want staff to enter a short passcode before viewing a lead card on mobile/desktop, or leave it empty for instant 1-tap access from email.
  3. Select Your Industry Baseline Profile:
    • Choose General — Universal PII & Secrets (RFC v1.0 Baseline) for standard business, agency, e-commerce, and financial forms, or Medical — Patient Intake & PHI Baseline to add Medical Record Number ([HEALTH_MRN_1]) and clinical diagnosis ([DIAGNOSIS_1]) rules.
  4. Decrypt Leads in the WP-Admin Encrypted Submissions Inbox:
    • Scroll to ZTDS Encrypted Submissions Inbox to inspect recent tokenized submissions stored in WordPress.
    • Click Reveal Real Data on any row to decrypt that lead’s values locally in your browser memory (click Re-Mask Data to hide them again), or click 1-Tap Staff Card to open the standalone lead action screen.
  5. Back Up or Share Your Dual-Key Admin Vault Secret:
    • Under Zero-Knowledge Admin Vault Secret, click Copy Key or Export Key Backup (.txt) to save your master key or import it into another administrator’s browser via Import Key.
  6. Enable the Frontend ZTDS™ Verification Badge (Optional):
    • Check Display “Protected by ZTDS™ Privacy Guard” seal below forms to show visitors a WCAG 2.1 AA accessible security badge with live links to your Verified Domain Certificate (ztds.ai/verify/?domain=yourdomain.com) and the ZTDS™ Official Registry.

Supported Form Builders (Zero Configuration)

  • Contact Form 7 (form.wpcf7-form + automatic Flamingo database scrubbing)
  • WPForms (form.wpforms-form)
  • Elementor Forms (form.elementor-form)
  • Gravity Forms (.gform_wrapper form, form[id^="gform_"])
  • Fluent Forms (form.fluentform)
  • Custom HTML / AJAX Forms (via data-ztds="true" or custom CSS selectors in Settings)

Key Architectural & Compliance Guarantees

  • Zero Network & Cloud Leakage: 100% of detection, tokenization, and AES-256-GCM encryption executes locally in the visitor’s browser. Zero bytes of form content are ever transmitted to PrivacyScrubber or external cloud servers.
  • Fail-Open Business Continuity: If a legacy browser lacks WebCrypto support or encounters a custom DOM exception, the interceptor gracefully bypasses tokenization so your business never loses an inbound client or patient lead.
  • Statutory Risk Minimization & Technical Safe Harbor: Implements proactive Technical & Organizational Measures (TOMs) supporting GDPR Article 32 pseudonymization, HIPAA Safe Harbor (45 CFR § 164.514(b)), PCI-DSS v4.0 intake hygiene, and Israel Protection of Privacy Law Amendment 13 Section 17.

External Services & Privacy Disclosure

This plugin executes 100% locally in the visitor’s browser and does not transmit any form data, visitor PII, or telemetry to any external server. Optional verification badge links to https://privacyscrubber.com/integrations/wordpress/ and https://ztds.ai/ are disabled by default and strictly controlled by the site administrator under Settings -> PrivacyScrubber ZTDS.