Remove PII from AI Prompts Before ChatGPT, Claude or Gemini See It

No. Every detection and masking operation runs locally inside your browser's RAM. Zero bytes of your text, documents, or session tokens leave your device. Verify this yourself: open DevTools → Network tab, test our DLP speed benchmark, or disconnect from the internet entirely — our air-gapped local processing keeps working offline.

The PrivacyScrubber Chrome extension injects real-time PII masking directly inside ChatGPT, Claude, Gemini, Microsoft Copilot (Bing Chat), Grok, Perplexity, DeepSeek, Qwen, Kimi, and Zendesk. For coding agents and autonomous workflows, explore our AI Agents Protection guide, or use the web app at privacyscrubber.com to sanitize text before pasting it into any interface.

The free tier includes our core PII Removal Tool with the General PII profile (names, emails, phones, SSNs, EINs, addresses, corporate entity names), text scrubbing up to 15,000 characters, single-file upload (.txt, .docx), and PDF text extraction up to 3 pages. Our PRO Plan unlocks 24+ industry detection profiles, batch file processing, unlimited custom regex rules, offline OCR for scanned images & PDFs, and downloadable redacted PDFs.

Yes. Our specialized financial PII profile natively detects Employer Identification Numbers (EIN/FEIN), payroll-format names (LASTNAME, FIRSTNAME), corporate employer names with legal suffixes (Inc, LLC, Corp), and US street addresses. All wage amounts, tax withholdings, hourly rates, and financial figures are preserved untouched — essential for loan underwriting and HR payroll compliance.

Yes. Paste the AI's response back into the tool and click Reveal. The 1-Click Reveal engine swaps every token ([NAME_1], [EMAIL_2], etc.) back to the original value using your volatile local session map — zero server round-trips, zero database storage.

PrivacyScrubber is designed to support de-identification under HIPAA Safe Harbor (45 CFR §164.514) for 18 PHI identifiers, GDPR Article 25/32 data minimization, and SOC 2 Type II controls by stripping identifiers in browser RAM before prompt submission. Review our Top 20 Corporate PII Guide and CISO AI Security Blueprint for detailed governance controls.

The session map exists exclusively in volatile browser RAM and is strictly isolated per tab. The moment you close the tab, reload the page, or navigate away, the entire mapping — including all original PII values and cryptographic keys — is permanently purged from memory. Read more in our Technical Security Architecture.

Supported formats include .txt, .docx, .pdf (text-layer and scanned images via Tesseract OCR), .xlsx, and .csv. With Batch File Redaction and Excel Spreadsheet Scrub, you can download sanitized files with PII removed or export redacted PDFs with true vector black-box redactions.

PrivacyScrubber TEAMS uses Argon2id key derivation and XChaCha20-Poly1305 authenticated encryption (via libsodium WASM). Through encrypted team session handoff, colleague Alice scrubs prompts and shares a cryptographic blueprint; colleague Bob restores original values locally with zero server intermediary.

PrivacyScrubber wraps editor inputs and tokenized outputs inside closed Shadow DOM roots. This makes unredacted sensitive text completely inaccessible to DOM-scraping scripts, third-party analytics, or unauthorized browser extensions running on the host page. Learn more about our in-DOM prompt sandbox.

Yes. The official @privacyscrubber/mcp-server package runs as a local stdio-based Model Context Protocol server for Cursor, Windsurf, Claude Desktop, and VS Code. It intercepts codebase prompts, sanitizes database passwords and API tokens in RAM, and protects your software development workflows with zero external calls.

Yes. The @privacyscrubber/sdk NPM package exposes the headless sanitization engine as a programmatic Node.js & ESM library. Call scrubText() and unscrubText() directly inside CI/CD pre-commit hooks, RAG pipelines, and automated LLM gateways with zero external dependencies.

No. Switching between our 24+ industry profiles (e.g. from General to Legal & Contracts or Medical) preserves active tokens and session maps. Tokens remain restorable via Reveal until you click the Clear button explicitly.

After processing documents (PDF, DOCX, XLSX), the engine immediately overwrites all temporary ArrayBuffers at the byte level with zeroes (Uint8Array.fill(0)) before releasing them to garbage collection. Pair this with our tamper-evident audit receipts for verifiable forensic compliance.

Yes. For organizations requiring formal vendor onboarding, purchase orders (PO), or SWIFT/SEPA bank wire transfers, we provide custom invoicing with EU VAT reverse-charge support. Check our transparent pricing matrix or visit our Enterprise Solutions Hub.

No. The platform loads zero analytics trackers, third-party cookies, or fingerprinting scripts. Maintaining strict Content Security Policies (CSP) ensures third-party endpoints cannot inspect memory or DOM states. Review our full commitments in our Zero-Server Privacy Policy.

There are no centralized accounts. Team administrators configure mandatory regex rules and compliance profiles locally in the Teams Deployment Hub, then generate a cryptographically signed Blueprint URL. When team members open this link, the configuration locks client-side without any backend database.

The purchaser acts as the Team Administrator with exclusive authority to configure organization-wide custom Regex rules, corporate token taxonomy (e.g. [PATIENT_ID]), and default compliance profiles in the Teams Dashboard. When the Admin exports a cryptographically signed Blueprint with Lock Rules enabled, Managed Team Members receive a locked, read-only configuration across their Web App and Chrome Extension (badged as 🔒 Enterprise), preventing employees from altering or bypassing corporate DLP policies.

Our Custom Regex Rules Engine discovers proprietary data formats (custom ticket IDs, project codes like PROJ-1234, internal server URLs). Token Labels, in contrast, customize the replacement placeholder (e.g. renaming [NAME] to [PATIENT_ID]) to give LLMs optimal domain context without modifying regex patterns.

PrivacyScrubber utilizes a high-performance deterministic pattern matching engine running natively in browser RAM (sub-2ms execution time). Unlike cloud LLM-based redaction which can hallucinate, omit tokens, or introduce network latency, our deterministic parser guarantees 100% reproducible tokenization across 18 core Safe Harbor/GDPR entity types (names, emails, phones, SSNs, credit cards, IBANs, medical MRNs, API tokens). PRO users can also inject custom regex rules or run local offline OCR for documents.