ZTDS Reference Server

RFC v1.0 SPECIFICATION · OPEN CONSORTIUM · ZERO TRUST DATA SANITIZATION (ZTDS)

ZTDS (Zero Trust Data Sanitization) The In-RAM AI Security Standard & Method

Airplane-Mode Privacy for AI. Your customer records, financial figures, and confidential prompts never leave the host device. ZTDS physically stops sensitive data from ever reaching external clouds: masked in volatile memory, verified by cryptographic proof, with 0.00 bytes data leakage and zero GDPR Article 28 subprocessor liability.

Physical In-RAM Execution Topology

Zero Backend Architecture · 0 ZTDS Servers in Loop

1. Host Process

User Application

Sensitive prompt entered in browser, local app, or IDE.

2. In-RAM Enclave < 0.8 ms

Local Volatile RAM

Cleartext swapped for context-preserving tokens. No disk write.

3. Network Socket

Encrypted Transport

Only surrogate tokens cross the NIC. Zero raw PII egress.

4. External Cloud

Public LLM API

Inference executes on tokens. Provider sees 0.00 B private data.

Quick test:

✓ 100% Free Open Specification (Apache 2.0 / CC BY 4.0) · ✓ Invariant-Based Cryptographic Proof · ✓ GDPR Article 28 DPA-Exempt · How the Method Works ↓ · Calculate CISO ROI →

0.00 B

External Data Leakage

< 0.8 ms

Volatile RAM Latency

DPA-Free*

Recital 26 Eligible*

100% Client

Volatile Memory Boundary

* Conformance claims apply when implementations satisfy all 4 ZTDS RFC v1.0 invariants as verified by the Perimeter Scanner. This does not constitute legal counsel. Consult qualified privacy counsel for jurisdiction-specific compliance.

Architectural Paradigm Shift

The ZTDS Method vs. Legacy Cloud DLP

Legacy Cloud DLP = You hand keys to a third party. • ZTDS = You never let raw data leave the room.

Traditional enterprise security relies on intermediate cloud proxies that intercept cleartext traffic, introducing latency and adding third-party subprocessor liability under GDPR Article 28. The ZTDS Method moves the security boundary into volatile process memory: raw PII never crosses the network socket.

Legacy Approach

Cloud DLP & Proxy Gateways

Subprocessor Chain

Data Egress Path Unencrypted Socket Hop

User App → Cloud Proxy (+400ms) → LLM API

×

Network Latency Overhead: Adds 350ms to 600ms of external round-trip network lag to every LLM generation token stream.

×

Mandatory Subprocessor Liability: Cleartext leaves the device and enters a third-party SaaS proxy. Under GDPR Art. 28, this creates a new data subprocessor requiring full DPA & BAA legal agreements.

×

Centralized Cloud Honeypot: Intercepted customer prompts and decrypted payloads sit in proxy memory, disk logs, and cloud buffers, creating an attractive target for credential compromise.

×

Destructive Masking: Blind redaction with [REDACTED] breaks grammatical syntax, destroys LLM attention weight matrices, and produces hallucinatory responses.

The ZTDS Method (RFC v1.0)

In-RAM Client Sanitization

DPA-Exempt Enclave

Memory Boundary Path 0.00 B Raw Egress

User App RAM ↔ ZTDS Enclave (<0.8ms) → LLM API (Tokens Only)

✓

Sub-Millisecond Execution: Executes in < 0.8ms in local WebAssembly or volatile Node.js runtime. Zero external network hops.

✓

GDPR Art. 28 Vendor Exemption: No personal data crosses the client boundary to the software vendor. Operating purely as a local computational utility, the architecture is fully exempt from GDPR Article 28 DPA requirements.

✓

Volatile Auto-Destruction: The ephemeral mapping table exists strictly in volatile RAM. It is never persisted to disk, database, or browser storage, and auto-destructs upon session termination.

✓

Bijective Lossless Tokens: Replaces entities with context-preserving surrogate tokens ([PATIENT_1], [IBAN_1]), preserving LLM reasoning and grammatical concordance.

LIVE IN-RAM DAG ENGINE

Test the ZTDS Method in Your Browser

Executes 100% locally in volatile browser memory. Open Network DevTools to verify 0.00 B network egress.

Sample Payload:

AIRPLANE MODE AUDIT Network socket disconnected. 0.00 B outbound telemetry. All regex tokenization and surrogate lookups execute in browser volatile memory.

Local Memory: 100% Active

1. Raw Ingestion (Cleartext in RAM) 192 chars

2. Sanitized Egress (Sent to LLM) < 0.35 ms

Egress: 0.00 B

✓ Invariant 1: ΔEgress ≡ 0.00 B

✓ Invariant 2: T = M(V, C) Bijective

✓ Invariant 3: Volatile RAM Isolation

✓ Invariant 4: DPA Subprocessor Exclusion

30-Second Empirical Proof Zero Trust

Prove Zero Egress in Airplane Mode

Zero Trust means you never need to trust a vendor's promise. Disconnect your Wi-Fi right now, paste confidential customer records into the sandbox above, and run the sanitizer. Open your browser DevTools Network tab: exactly 0.00 bytes leave your machine.

WAN Packets: 0.00 B Cloud Sinks: 0

Transformer Attention Sub-2ms DX

Surrogates vs. Broken Redaction

Traditional redaction (like [REDACTED] or asterisks) flattens entropy and breaks LLM multi-head attention weights, causing hallucinations. ZTDS bracketed surrogates ([PERSON_1], [IBAN_2]) preserve semantic graph relationships, restored losslessly on your screen upon response.

Entropy Leakage: 0.00 bits Accuracy Loss: 0.00%

Enterprise Fast-Track Zero DPA

Bypass 6-Week Security Reviews

Enterprise buyers stall on third-party subprocessor risk. Hand your CISO or customer procurement team our 1-page Zero-DPA Legal Memo: since cleartext never leaves device RAM, vendors are legally exempt from GDPR Article 28 processor obligations.

Read CISO Memo → Download PDF

Formal Verification Axioms

The 4 Foundational Invariants of RFC v1.0

ZTDS is not a proprietary black box. It is a mathematical specification defined by four inviolable system invariants verified through automated network socket inspection.

01 Zero Egress

Zero External Egress Prior to Sanitization

ΔEgress ≡ 0.00 B

No personal data (PII, PHI, commercial secrets) may leave the local boundary in unmasked form. Enforced via socket byte-counting and audited via npx ztds-audit.

Rule: Network Boundary Lock

02 Bijective Tokens

Deterministic Reversible Tokenization

T = M(V, C) ↔ V = M‾¹(T)

Surrogate tokens preserve syntactic structure, grammar, and semantic roles for LLMs. The reverse mapping table is held strictly in volatile RAM for localized detokenization.

Rule: Context Concordance

03 In-RAM Isolation

Verifiable Memory Isolation

DiskWrite = 0 · DB = ∅

Ephemeral mapping tables cannot be written to disk, databases, localStorage, or third-party telemetry sinks. They auto-destruct when the execution session ends.

Rule: Zero Persistence

04 DPA-Exempt

Complete Subprocessor Exclusion

GDPR Art. 28 — Subprocessor Exclusion Path

Software functions purely as a local computing utility. Under GDPR Recital 26 and EDPB doctrine, zero vendor processing of PII means no subprocessor chain and no DPA required.

Rule: Statutory Demarcation

Read the Complete ZTDS RFC v1.0 Formal Specification →

Consortium & Ecosystem Accreditation

Rallying the Ecosystem Around the ZTDS Standard

ZTDS.ai is an open consortium, not a commercial SaaS vendor. We unite AI builders, enterprise CISOs, and security researchers to make client-side zero-trust sanitization the global industry norm.

TRACK A · BUILDERS Open Source & SaaS

Verified AI Applications

Sell to enterprise buyers without 90-day legal reviews. Prove 0.00 bytes cloud leakage with automated CLI verification, an official verified trust badge, and canonical registry inclusion.

Accreditation Benefits:

✓ Run automated CLI audit: npx ztds-audit

✓ Embed official ZTDS Verified™ dynamic SVG badge

✓ Listed in canonical /registry/ and llms.txt corpus

Browse Verified Registry →

TRACK B · ENTERPRISE CISOs & Legal

Corporate Adopters

Deploy internal LLMs and AI agents across your organization without signing new data processor agreements (DPAs) or expanding vendor attack surfaces.

Accreditation Benefits:

✓ Standardize internal AI usage on ZTDS Invariants

✓ 1-Page DPA Exemption Memorandum for Board & Legal

✓ Listed in Corporate Adopter pool (Founding: BrandMeWeb)

Download Legal CISO Pack →

TRACK C · ACADEMIA Researchers & Fellows

Fellows Council

Advance the mathematical and legal foundations of client-side privacy. Author peer-reviewed DOIs across Zenodo, OSF, SSRN, and IEEE-indexed publications.

Accreditation Benefits:

✓ Peer-reviewed DOIs on Zenodo, OSF, and SSRN

✓ Co-authorship on RFC v1.1 working group drafts

✓ Profile in the Global Fellows Council directory

Read Academic Treatise →

ZTDS.ai is governed as a vendor-neutral standard under Apache 2.0 & CC BY 4.0. Architecture sponsorship by BrandMeWeb. Reference engine implementation by PrivacyScrubber.

Read Governance Charter →

Reference Implementations

Deploy the Method in 4 Lines of Code

Deploy using the vendor-neutral open reference package @ztds/core (Apache 2.0) or the enterprise production engine @privacyscrubber/sdk. Both execute 100% locally in WebAssembly or host RAM without external API keys, telemetry, or network calls.

✓ Zero external configuration — operates completely in-RAM

✓ Sub-millisecond latency (< 0.8ms average execution)

✓ Connectors for LangChain, LlamaIndex, OpenAI, Anthropic, and MCP

// 1. Install open engine: npm i @ztds/core (or @privacyscrubber/sdk for enterprise profiles)
import { ZTDSClient } from '@ztds/core';

// 2. Initialize in-memory zero-trust enclave
const ztds = new ZTDSClient();

// 3. Sanitize prompt in volatile RAM prior to external egress
const { safePrompt, tokenMap } = ztds.sanitize(rawUserPrompt);

// 4. Transmit safe surrogate tokens to external cloud LLM (0.00 B PII leak)
const aiResponse = await openai.chat.completions.create({
  model: 'gpt-4o',
  messages: [{ role: 'user', content: safePrompt }]
});

// 5. Reversibly detokenize response locally in volatile RAM
const cleanResult = ztds.restore(aiResponse.content, tokenMap);

LEGAL & COMPLIANCE MEMORANDUM

Why ZTDS-Compliant Architectures Do Not Require a DPA

Under GDPR Article 28 and EDPB doctrine, data processing agreements are legally required only when personal data is processed by a third party. Because the ZTDS Method executes 100% in client RAM with 0.00 bytes transmitted to vendor servers, the vendor never qualifies as a "data processor".

✓ GDPR Art. 28 DPA Exemption

✓ HIPAA Safe Harbor 18 Exclusion

✓ EU AI Act High-Risk Shield

✓ SIG Lite & CAIQ Ready Controls

CISO Procurement Pack

Institutional Memorandum & Security Pack

Hand this directly to your enterprise buyers, legal counsel, and data protection officers.