ZTDS.ai Open AI Security Standard
Public Directory · Verifiable Cryptographic Receipts

ZTDS Verified™ Registry

Browse AI applications, browser extensions, agent gateways, and developer SDKs certified compliant with the ZTDS RFC v1.0 standard. All listed products prove 0.00 bytes external sensitive data egress.

For AI Builders & SaaS Founders

Built an AI Agent, RAG Pipeline, or LLM Tool? Get Verified in 5 Minutes.

Enterprise CISOs use this directory to discover zero-data-leakage software. Pass our zero-egress audit, submit your GitOps pull request, and display the official ZTDS seal to fast-track B2B sales and gain high-DR backlink authority.

Showing 14 of 14 certified solutions
OPEN REFERENCE SPECIFICATION Apache 2.0

@ztds/core

Vendor-Neutral RFC v1.0 Reference Engine

Official open-source baseline engine and TypeScript interface. Pure in-memory execution enforcing Invariants 1 through 4 with universal base regex entities (Email, Phone, PAN, SSN, IPv4, Secrets). Zero dependencies, 100% free forever for builders and academic validation.

Install: npm install @ztds/core
Invariant Proof: 0.00 Bytes WAN Egress · RAM Only
Open Source TypeScript Apache-2.0 Sub-0.8ms
PYTHON REFERENCE IMPLEMENTATION MIT · v1.1.1

ztds (Python)

Canonical RFC v1.0 Python Reference Engine & CLI

Official vendor-neutral Python reference implementation and CLI. Pure in-memory volatile RAM execution enforcing Invariants 1 through 4 with zero external dependencies. Features native drop-in hooks for LiteLLM, LangChain, CrewAI, and LlamaIndex.

Install: pip install ztds
Invariant Proof: 0.00 Bytes WAN Egress · RAM Only (<0.05ms)
PyPI Zero-Dependency MIT LiteLLM / CrewAI
ZTDS VERIFIED · PIONEER RFC v1.0

PrivacyScrubber Web

Client-Side Document & Prompt Sanitizer

Zero-server, 100% client-side PII/PHI de-identification web utility. Processes large text, PDFs, and conversation prompts strictly inside browser volatile RAM before passing to LLMs.

Perimeter Invariant: 0.00 bytes socket transmission prior to sanitization.
Compliance Basis: GDPR Recital 26 · HIPAA Safe Harbor · EU AI Act Art. 50.
WebAssembly V8 Volatile RAM Maps Zero Server Storage
ZTDS VERIFIED · BROWSER RFC v1.0

PrivacyScrubber Extension

Manifest V3 Real-Time Interceptor

Chrome extension running client-side on ChatGPT, Claude, Gemini, Perplexity, and DeepSeek. Intercepts sensitive prompts before DOM submit, tokenizes locally, and restores on response.

Perimeter Invariant: Pure client-side DOM injection; zero external telemetry.
Memory Scope: Tab-isolated ephemeral RAM maps; wiped on tab close.
Chrome MV3 DOM Interceptor Multi-Model
REFERENCE SDK Apache 2.0

@privacyscrubber/sdk

Headless Engine for Node.js, Web & Python

Official developer engine sponsored by the consortium. Embeds directly into LangChain, LlamaIndex, CrewAI, or custom REST pipelines with < 0.8ms local execution latency.

Package: npm install @privacyscrubber/sdk
Benchmark: Audited on Open Science Framework (OSF DOI: 10.17605).
TypeScript Python Bridge Sub-1ms
ZTDS VERIFIED · OPEN REFERENCE Apache-2.0

ZTDS Reference MCP Server

Official Anthropic Registry (io.github.moxno/ztds)

Zero-dependency open-source reference Model Context Protocol server. Provides local in-memory PII sanitization and deterministic reversible tokenization for Claude Desktop, Cursor, and Zed with 0.00 bytes external telemetry.

Distribution: npx -y ztds-mcp
Perimeter: Stdio Process Sandbox · Volatile RAM Only
Open Source Anthropic Registry mcpservers.org → Cursor Claude Desktop
ZTDS VERIFIED · BLUEPRINT RFC v1.0

LangChain ZTDS Callback

AI Framework Connector & Agent Hook

Zero-trust client-side callback handler for LangChain & LangGraph workflows. Sanitizes tool inputs and conversation state strictly in local memory before invoking external LLMs.

Perimeter Invariant: In-memory async callback hook with volatile state isolation.
Compliance Basis: GDPR Recital 26 · HIPAA Safe Harbor · EU AI Act Art. 50.
LangChain LangGraph Python & TS Volatile RAM
ZTDS VERIFIED · BLUEPRINT RFC v1.0

LlamaIndex Air-Gap Sanitizer

RAG & Vector Pipeline Ingestion Node

Pre-indexing ingestion pipeline node and query sanitizer ensuring raw PII/PHI is never embedded into vector stores, preventing permanent GDPR Article 17 vector poisoning.

Perimeter Invariant: Client-side ingestion node & deterministic token substitution.
Compliance Basis: GDPR Art. 17 (Right to Erasure) · HIPAA Safe Harbor · SOC 2 Type II.
LlamaIndex Vector RAG Zero Storage Embedding Sanitizer
ZTDS VERIFIED · BLUEPRINT RFC v1.0

Ollama Local Privacy Filter

Local LLM Engine & Loopback Proxy

Sidecar proxy intercepting Ollama REST endpoints on localhost. Guarantees complete air-gapped de-identification and secret stripping before edge inference executes.

Perimeter Invariant: Loopback reverse proxy with RAM-only stream buffer.
Compliance Basis: NIST 800-53 · ISO 27001 A.8.11 · Zero External Socket Policy.
Ollama Local LLM Loopback Proxy Edge Privacy
ZTDS VERIFIED · ENTERPRISE RFC v1.0

Envoy Proxy WASM Filter

Enterprise Network Gateway & Service Mesh

High-performance WebAssembly HTTP filter for Envoy and Istio service mesh. Enforces zero-egress PII sanitization at egress gateways with < 0.8ms overhead.

Perimeter Invariant: Proxy-WASM sandboxed bytecode engine (<0.8ms overhead).
Compliance Basis: SOC 2 CC6.7 · PCI-DSS v4.0 · FedRAMP Moderate · HIPAA Safe Harbor.
Envoy Proxy Istio Mesh WebAssembly Sub-1ms WASM
ZTDS VERIFIED · GATEWAY RFC v1.0

FastMCP Stdio Gateway

Sub-millisecond Python Model Context Protocol Adapter

High-throughput FastMCP stdio daemon running locally for Python agent workflows. Strips corporate secrets, database connection strings, and PII before dispatch to Cursor, Windsurf, or Claude Desktop.

Perimeter Invariant: Stdio stream filter with RAM-only ephemeral surrogate table.
Compliance Basis: SOC 2 CC6.7 · ISO 27001 A.8.11 · GDPR Art. 28 Vendor Exemption.
FastMCP Python 3.10+ Claude Desktop Sub-1ms
ZTDS VERIFIED · BLUEPRINT RFC v1.0

CrewAI Privacy Agent

Multi-Agent Inter-Node Communication Sanitizer

Memory-isolated hook preventing sensitive data cross-contamination between autonomous multi-agent swarms. Enforces 0.00 bytes leakage during delegated task execution and tool handoffs.

Perimeter Invariant: In-memory message interceptor & reversible ephemeral token mapping.
Compliance Basis: EU AI Act Art. 50 · GDPR Art. 28 Vendor Exemption · HIPAA Safe Harbor.
CrewAI Multi-Agent Ephemeral RAM Zero Egress
REFERENCE IMPLEMENTATION Commercial / Proprietary

PrivacyScrubber MCP Server

Reference Implementation · AI Agent & IDE Security Gateway

Zero-trust stdio model context protocol server intercepting tool inputs and outputs for Cursor and Claude Desktop.

Distribution: https://ztds.ai/sdk/#mcp
Architecture: Local Stdio JSON-RPC Stream Interceptor
SOC 2 CC6.7 ISO 27001 A.8.11 OWASP Top 10 for LLM
REFERENCE IMPLEMENTATION GPL-2.0+ / Commercial

PrivacyScrubber WordPress ZTDS Guard

Reference Implementation · CMS & Web Form Intake Interceptor

Zero-trust client-side PII sanitizer for WordPress forms (Contact Form 7, WPForms, Elementor, Gravity Forms, Fluent Forms) with AES-256-GCM Dual-Envelope vaulting.

Distribution: https://privacyscrubber.com/integrations/wordpress/?utm_source=ztds.ai&utm_medium=ecosystem_registry
Architecture: DOM Capture-Phase RAM Interceptor (<0.4ms) & Dual-Envelope WebCrypto Vault
GDPR Art. 32 HIPAA Safe Harbor PCI-DSS v4.0 Dual-Envelope Vault
REFERENCE IMPLEMENTATION Commercial / ZTDS SDK Certified
Learning Center USA Logo

LearningCenterUsa.net — PSTN Voice Enclave

Reference Implementation · Client-Side Voice & Transcript Sanitization App

Interactive US PSTN (300Hz–3,400Hz) voice and spoken-English simulator sanitizing spoken SSNs, USCIS A-Numbers, and payment cards in volatile browser RAM prior to scoring.

Distribution: https://learningcenterusa.net
Architecture: Browser Web Audio & In-Memory Surrogate Tokenization (@privacyscrubber/sdk)
Cal. Penal Code § 632 Illinois BIPA GDPR Recital 26 Zero Voice Retention
Direct Answer Knowledge Base

ZTDS Verified Public Registry & Accreditation FAQ

What does a ZTDS Verified listing in the public registry signify? ↓
A listing in the ZTDS Verified Public Registry confirms that an AI application, SDK, or Model Context Protocol (MCP) server has passed automated conformance testing against the four ZTDS RFC v1.0 invariants, proving 0.00 bytes of cleartext PII egress and deterministic in-RAM surrogate tokenization.
How are Ed25519 conformance certificates tied to registry entries? ↓
Every accredited implementation in data/registry.json is issued a cryptographically signed ZTDS-CERT-v1 token canonicalized under RFC 8785 (JCS) and signed with the consortium Ed25519 root key (RFC 8032), allowing enterprise buyers to verify build integrity offline at ztds.ai/verify/.
What is the difference between open reference implementations and certified commercial engines in the registry? ↓
Open reference packages (@ztds/core, ztds-mcp, ztds-python) provide Apache 2.0 baseline entity sanitization for standard developer workflows. Certified commercial engines such as PrivacyScrubber (engineered by BrandMeWeb) provide 30 specialized industry profiles, multimodal document redaction, and air-gapped enterprise licensing.
How can a software vendor submit an AI product to the ZTDS Verified Registry? ↓
Vendors run npx ztds-audit --strict locally to generate a cryptographic SHA-256 compliance receipt and submit a self-serve GitOps pull request via ztds.ai/apply/ for automated CI invariant verification and registry indexing.