Privacy Policy & Zero-Data Architecture
At PrivacyScrubber, privacy is not a contractual promise — it is an immutable mathematical and architectural guarantee. We do not store, intercept, log, or transmit your sensitive data because our application possesses zero application backend to receive it. All sanitization, pseudonymization, and re-identification occurs 100% locally in your device's memory.
Raw prompts never leave your local RAM
Direct local CPU execution (< 3ms)
Bypasses third-party processor liability
Auto-erased on tab close or refresh
1. Architectural Philosophy: Zero-Trust Data Sanitization (ZTDS)
Traditional Data Loss Prevention (DLP) and cloud proxies operate on a flawed assumption: they require organizations to transmit unencrypted, raw customer records across the public internet to a vendor-controlled server cluster for inspection. This creates a massive secondary attack surface, increases API latency by 1,000–3,000ms, and subjects companies to continuous third-party vendor audits and complex Data Processing Agreements (DPAs).
PrivacyScrubber pioneered Zero-Trust Data Sanitization (ZTDS). By shifting the entire sanitization boundary directly to the client's local computing environment (the browser tab, the local IDE process, or the local container runtime), we eliminate the vendor attack vector entirely. We cannot leak, subpoena, monetize, or log your confidential data because your raw data is never received by any PrivacyScrubber server.
2. Privacy Architecture Across All 4 Execution Environments
PrivacyScrubber provides four distinct deployment surfaces. Each environment adheres to the same uncompromising Zero-Server privacy boundary. Click each tab below to review the specific runtime isolation and data flow mechanics for each surface.
Web Workspace (privacyscrubber.com)
100% Client-Side Web WorkerThe primary web interface loads all detection heuristics, regex pattern matrices (covering 24+ industry profiles), and natural language parsers directly into the browser's RAM via a dedicated Web Worker thread.
- Ephemeral SessionMap: Translation maps linking raw entities to synthetic tokens (e.g.
[NAME_1]) are stored strictly in volatile JavaScript heap memory and destroyed when the tab is closed. - Local Document & OCR Engine: PDF, Word, Excel, CSV, and image uploads are parsed in-browser via the HTML5 FileReader API and client-side WebAssembly builds of Tesseract.js & PDF.js. No files are ever uploaded.
- Encrypted Session Exports: Saved sessions (
.pssession) are encrypted client-side using XChaCha20-Poly1305 with a key derived via Argon2id before saving locally to disk. - Local Cryptographic Receipts: CISO compliance receipts and audit logs are signed locally using SHA-256 digests and rendered to PDF entirely on your CPU via jsPDF.
3. Technical Data Flow & Security Comparison Matrix
The table below provides a rigorous, fact-checked comparison of data handling, encryption, storage, and telemetry characteristics across all four PrivacyScrubber operational surfaces.
| Operational Parameter | Web Workspace | Chrome Extension | PII MCP Server | Developer SDK |
|---|---|---|---|---|
| Raw PII Ingestion Location | Browser Tab RAM | Tab Renderer RAM | Local stdio Stream | Host Process Heap |
| Session Map Storage | Volatile Memory Only | Volatile Memory Only | Volatile Process Memory | Caller State Object |
| Persistent Local Storage | License key, UI theme | chrome.storage.local (Key) | None (Stateless) | None (Stateless) |
| Encrypted Export Standard | XChaCha20-Poly1305 | XChaCha20-Poly1305 | Caller-Controlled | Caller-Controlled |
| Network Egress for Text | 0 Bytes (Zero) | 0 Bytes (Zero) | 0 Bytes (Zero) | 0 Bytes (Zero) |
| Server-Side Telemetry | Aggregate Vercel Views | None (Zero) | None (Zero) | None (Zero) |
| Data Retention Post-Session | 0 Seconds (Wiped) | 0 Seconds (Wiped) | 0 Seconds (Wiped) | 0 Seconds (Wiped) |
4. Third-Party Service Providers & Processors (Full Transparency)
In compliance with global regulatory transparency mandates (including GDPR Article 28 and CCPA), we provide an exhaustive disclosure of all third-party infrastructure providers utilized by the PrivacyScrubber marketing website and billing workflows.
Delivers pre-compiled static assets (HTML, CSS, JS, WASM binaries). Operates as an immutable content delivery network. No customer data, prompt strings, or uploaded files are sent to or stored on our hosting infrastructure.
Paddle.com acts as our Merchant of Record (MoR) for credit cards and digital wallets. PayPal processes direct PayPal payments. Payment transactions occur directly on their PCI-DSS Level 1 certified servers. PrivacyScrubber never touches, handles, or stores your credit card numbers.
When you explicitly submit a contact inquiry or request a copy of the CISO AI Security Guide, your provided name and business email are transmitted via encrypted API solely to deliver the requested correspondence. This administrative channel is strictly air-gapped from the PII scrubbing engine.
We collect aggregate, anonymous page-view statistics (e.g. total visits, browser family, country-level geography) to monitor platform health. We use zero tracking cookies, zero persistent device fingerprinting, and zero cross-site advertising pixels.
5. Global Regulatory & Compliance Standards
PrivacyScrubber's Zero-Server architecture natively satisfies the most stringent global privacy, healthcare, and financial compliance frameworks by eliminating data transfers at the technical boundary.
GDPR (EU 2016/679) & UK GDPR
Under GDPR Article 25 (Privacy by Design and by Default) and Article 32 (Security of Processing), pseudonymization is a primary technical measure for mitigating risk. Because PrivacyScrubber executes strictly client-side without receiving data, PrivacyScrubber does not act as a Data Processor under GDPR Article 28. Your enterprise remains the sole Data Controller with total sovereign custody.
CCPA & CPRA (California Privacy Rights Act)
PrivacyScrubber does not collect, retain, monetize, "sell", or "share" (as defined under Cal. Civ. Code § 1798.140) any personal information or sensitive consumer data processed within the application.
HIPAA Safe Harbor & Protected Health Information (PHI)
PrivacyScrubber provides dedicated Healthcare detection profiles configured to redact all 18 HIPAA Safe Harbor identifiers (§ 164.514(b)(2))—including Medical Record Numbers (MRN), National Provider Identifiers (NPI), patient names, and health plan numbers—before clinician prompts are dispatched to commercial LLMs. Because processing is local, no Business Associate Agreement (BAA) with PrivacyScrubber is required.
SOC 2 Type II & ISO/IEC 27001 Trust Principles
Enterprises auditing AI adoption under SOC 2 Common Criteria (CC6.1, CC6.6, CC6.7) can generate tamper-evident, SHA-256 signed Compliance Audit Receipts directly from PrivacyScrubber, providing cryptographic proof of zero-server PII sanitization.
6. Data Subject Rights & Instant Erasure Mechanics
Because PrivacyScrubber does not store personal data on any server, traditional Data Subject Access Requests (DSARs) and "Right to Be Forgotten" workflows are satisfied by design:
Closing your browser tab, navigating away, or clicking "Reset Session" irrecoverably purges all active token mappings from RAM. There are zero backups, databases, or logs to purge.
Users can export their complete session map as an encrypted .pssession package (XChaCha20-Poly1305) or export compliance audit receipts as structured JSON/PDF.
7. Local Storage, Cookies & State Lifecycles
PrivacyScrubber minimizes persistent state and adheres strictly to a RAM-First Storage Doctrine:
- Volatile RAM:Stores the live
SessionMap(entity replacement dictionary) during active scrubbing. Cleared immediately upon tab closure. - localStorage:Retains solely non-sensitive settings:
ps_license_key(your PRO/TEAMS license key for offline validation),ps_active_profile(e.g. 'finance', 'legal'), custom user regex strings, and UI theme preferences. - Cookies:PrivacyScrubber places zero advertising, tracking, or marketing cookies on your device.
8. User Responsibilities & Threat Modeling
While PrivacyScrubber guarantees zero server-side exposure, the overall security of client-side operations depends on endpoint hygiene:
Maintain host security. PrivacyScrubber cannot shield data from malicious OS keyloggers, screen scrapers, or compromised workstation firmware.
Third-party browser extensions with broad DOM permissions can read active webpage inputs. Audit installed browser extensions on sensitive endpoints.
Review neon visual highlights in the editor before pasting text into public AI chatbots to ensure proprietary company abbreviations are covered by active profiles.
9. CISO Airplane Mode & Independent Verification Playbook
We do not ask security engineering teams to take our word for it. We provide a repeatable, 3-step technical verification procedure that any security analyst can execute in under 60 seconds.
Navigate to privacyscrubber.com, open Chrome DevTools (F12), and select the Network tab. Check "Preserve log".
Disconnect Wi-Fi and Ethernet entirely. Enable device Airplane Mode. The application remains 100% operational.
Paste confidential PII text or drop a multi-page PDF. Click "Scrub". Verify that 0 network requests are attempted and the DevTools log remains 100% empty.
10. Legal Entity, DPO Contact & Governance
PrivacyScrubber is an autonomous Zero-Trust engineering product developed under the BrandMeWeb agency ecosystem. For formal privacy inquiries, Data Protection Officer (DPO) communications, or enterprise security reviews, contact our team:
