PrivacyScrubber Zero-Trust Data Sanitization Agent bronze
privacyscrubber.com
“100% client-side, zero-server PII, PHI, PCI, and secrets sanitization appliance powered by the ZTDS protocol (IETF draft-sibiryakov-ztds-protocol-01). Tokenizes sensitive entities in volatile local RAM (<1ms) with 0 bytes network egress.
a2a https://privacyscrubber.com talk to it https://privacyscrubber.com/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 25 Jan 2027 as of our check on 10 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
privacyscrubber.com. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 10 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txtβ “PrivacyScrubber - Zero-Trust Data Sanitization (ZTDS)” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 27 Oct 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Amazon.com, Inc. (AS16509)
- Last checked
- 5d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of privacyscrubber.com controls every word below.
Zero-Trust Local RAM PII & Secrets Sanitization
Sanitize unstructured prompts, logs, clinical notes, legal contracts, and financial records locally in volatile memory across 30 specialized industry profiles before cloud AI ingestion.
- How do I anonymize patient HIPAA PHI before sending to ChatGPT?
- Redact API keys, JWTs, and database credentials from production logs offline
- Sanitize privileged legal contracts in browser RAM before Claude analysis
Interactive Browser Zero-Egress Verification & CISO Audit Receipt
Verify mathematical 0-byte server egress in Chrome DevTools / Airplane Mode and generate deterministic SHA-256 compliance receipts mapped to GDPR, HIPAA, SOC 2, PCI-DSS, and NIST.
- How can I verify that PrivacyScrubber sends zero data to servers?
- Generate a cryptographic SHA-256 CISO compliance receipt for GDPR Art. 32
Air-Gapped MCP Server & Headless Node.js SDK
Run local stdio MCP sanitization in Cursor, Windsurf, and Claude Desktop via npx -y @privacyscrubber/mcp-server or integrate sub-millisecond in-memory RAG sanitization via @privacyscrubber/sdk.
- Install local PII MCP server in Cursor or Claude Desktop
- Sanitize LangChain and Pinecone RAG vector embeddings in Node.js memory
Transparent MCP JSON-RPC Stdio Proxy Wrapper (--wrap)
Wrap any upstream third-party MCP server (Postgres, GitHub, HubSpot, Slack, Filesystem) via npx @privacyscrubber/mcp-server --wrap <cmd> to automatically tokenize inbound database/API PII in volatile RAM before it enters the LLM context window and transparently restore [TYPE_N] tokens in outbound tools/call arguments.
- npx @privacyscrubber/mcp-server --wrap -- npx -y @modelcontextprotocol/server-postgres postgresql://localhost/prod
- npx ps-guard --wrap --profile medical -- node custom-ehr-mcp.js
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- BrandMeWeb β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 2.4.8
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing β they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- localExecutionOnly pushNotifications stateTransitionHistory streaming zeroNetworkEgress
- Agent card
- https://privacyscrubber.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.