The $229 self-hosted PII redaction sidecar that keeps regulated data on your servers — not your LLM provider's. One Docker container. One environment variable change. Zero data egress.
🔒 Stop the Leak — Buy Now $229Every prompt your app sends to an LLM API contains raw, unredacted user data. Names. Emails. Phone numbers. SSNs. Credit cards. Sent in plaintext. Sitting on third-party servers. Your compliance team probably doesn't know.
DDS Protect sits between your app and any OpenAI-compatible LLM API. It detects and redacts PII before a single byte leaves your infrastructure.
Eight capabilities that turn your AI features from "compliance liability" to "auditor-ready" in five minutes.
DDS Protect runs entirely on your hardware. Detection in your container's memory. Redaction inside your network. No telemetry. No license check phoning home. The only thing that leaves: sanitized text.
Out of the box: names, emails, phones, addresses, SSNs, credit cards, dates of birth, IPs — 96% F1 via OpenAI's open-source privacy-filter model (Apache 2.0). The model is fine-tunable: the community has already extended it from 8 to 50+ entity types using domain-specific training data. Medical record numbers, passport IDs, custom organizational codes — if you can label it, the model can learn it. Fine-tune once, deploy forever.
Change one environment variable: OPENAI_BASE_URL from api.openai.com to localhost:8080. Your existing SDK calls, LangChain pipelines, and custom clients work without modification. Five minutes from download to redaction.
Server-Sent Events pass through transparently. Chat messages stream token-by-token exactly as they do today. 50–200ms detection latency happens before the first token — zero perceived delay for your users.
Every detected PII span logged to a local SQLite database: category, original value, position, confidence score, timestamp. Append-only — no record ever modified or deleted. This is your legal defense, not just a feature.
audit-viewer.html ships with every download. Open in any browser — connects to the sidecar's /audit API endpoint for live redaction data. Total events, category breakdowns, confidence distributions, searchable event log. Auto-refreshes; just point it at your running sidecar.
Linux, macOS, Windows. On-prem, AWS EC2, that dusty Dell PowerEdge. CPU-only: 8GB RAM. GPU (CUDA / Apple Silicon MPS): auto-detected, drops latency from ~150ms to ~30ms.
The detection model — openai/privacy-filter — is Apache 2.0 licensed, publicly available on HuggingFace. Inspect the model card. Verify benchmarks independently. ~700 lines of readable Python wrapper. If we disappeared tomorrow, your deployment keeps running.
Enterprise PII redaction gateways start at $30,000–$50,000 per year. If you're not Fortune 500, that price isn't expensive — it's disqualifying. But GDPR fines don't scale down for smaller companies.
| What you get |
✓ Full source code (~700 lines Python) ✓ Docker image + docker-compose.yml ✓ audit-viewer.html dashboard ✓ GDPR/HIPAA DPIA compliance template ✓ Setup guide · 30 days email support |
| What you don't get |
✗ Ongoing support beyond 30 days ✗ Hosted/SaaS version ✗ Automatic model updates ✗ Custom model fine-tuning ✗ Someone to deploy it for you |
Detection model: openai/privacy-filter — Apache 2.0, free for commercial use, ~3GB, cached locally on first run.
We're new. But what we ship is open, auditable, and built on battle-tested architectural patterns.
openai/privacy-filter — Apache 2.0. Publicly available on HuggingFace. Download it, benchmark it, verify the 96% F1 claim yourself. No proprietary black box.
The entire DDS Protect wrapper is ~700 lines of readable, documented Python. A senior engineer can read the full codebase in an afternoon. No hidden functionality. No telemetry. No surprises.
Transparent sidecar proxy — the same architectural pattern used by Kong, Envoy, and Apigee. Applied to one specific, high-risk use case: preventing PII from reaching LLM APIs.
Every purchase includes a 444-line DPIA template for GDPR Article 35 and HIPAA. Maps each PII category to specific regulations. Drop it into your existing DPIA with minimal modification.
You have three choices. Two of them are expensive. One of them is five minutes.
From Stripe receipt to PII redaction in production — here's exactly what happens after you buy.
Receive a download link instantly after purchase. Contains full source code (~700 lines), Docker image configs, and the dashboard. No waiting for account provisioning.
Set OPENAI_API_KEY and OPENAI_BASE_URL in your environment. That's it. The detection model downloads and caches automatically on first run.
docker compose up -d — DDS Protect starts proxying requests on port 8080. Your existing OpenAI SDK calls work unchanged. No code changes in your app.
Open audit-viewer.html in your browser. Watch PII detections arrive in real-time. Check your DPIA template. Show your compliance team. You're done.