PrivacyScrubber

Organizational Overview & Mandate

The pioneer consumer and enterprise implementation of the ZTDS standard. Operates pure client-side V8/WASM engines in browser extensions and headless SDKs with zero server logging.

As part of the ZTDS verified ecosystem, PrivacyScrubber enforces hardware-isolated and in-memory reversible tokenization to eliminate external cloud intermediary leaks before outgoing prompts reach foundation models.

Certified Compliance Scope

Pure client-side V8/WASM zero-server execution. Zero cloud ingress or egress.

• Invariant 1 (Zero WAN Egress): High-risk corporate identifiers and domain entities are masked in local RAM prior to WAN transmission.
• Invariant 2 (Deterministic Tokenization): Syntactic surrogate tokens maintain prompt context for LLMs while private mapping tables remain strictly in volatile memory.
• Invariant 4 (Zero Subprocessor Chain): Eliminates third-party cloud proxy servers and excludes vendor sub-processor liability under GDPR Article 28.

1,000,000+ Sensitive Entities Sanitized Locally with Zero Server Overhead

import { PrivacyScrubberWasmCore } from '@privacyscrubber/sdk/wasm';

// Pure client-side WebAssembly engine — zero cloud ingress/egress
const scrubber = await PrivacyScrubberWasmCore.init();

// Sanitizes 100+ PII / financial tokens in local V8 memory
const result = scrubber.tokenize({
  text: userPastedPrompt,
  preserveFormatting: true,
  strictMode: true
});

// Dispatched directly to LLM endpoint with zero PII
console.log('Sanitized payload:', result.maskedText);
console.log('Perimeter network egress bytes:', result.egressBytes); // 0