

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.
window.crypto.subtle) and mapped into isolated tokens ([NAME_1], [EMAIL_1], [PHONE_1], [CREDIT_CARD_1], [SSN_1]).ztds_encrypted_inbox, Flamingo, postmeta) store only masked tokens. Even if your database backup is leaked, attackers get zero raw personal data.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].wp-admin Login Required):
/?ztds_lead_card=1#ztds_seal=...)..vcf), Copy Full Lead, and AI-Safe Copy (pre-scrubbed with tokens so staff can safely paste the inquiry into ChatGPT, Claude, or Gemini).#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.[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.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].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.[NAME_1]), Email ([email protected]), and Phone (+10005550001)—across all outbound emails and webhooks.[HEALTH_MRN_1]) and clinical diagnosis ([DIAGNOSIS_1]) rules..txt) to save your master key or import it into another administrator’s browser via Import Key.ztds.ai/verify/?domain=yourdomain.com) and the ZTDS™ Official Registry.form.wpcf7-form + automatic Flamingo database scrubbing)form.wpforms-form)form.elementor-form).gform_wrapper form, form[id^="gform_"])form.fluentform)data-ztds="true" or custom CSS selectors in Settings)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.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.