Legal and Compliance
Privacy Policy
Last updated: November 16, 2026
1. Architecture and Privacy Overview
ShadowDiff is an open-source traffic mirroring and regression testing engine. It is architected from the ground up for strict data isolation, zero data exfiltration, and local processing.
When deployed, ShadowDiff acts as a reverse proxy or sidecar service that duplicates HTTP/gRPC requests to shadow targets. All traffic processing, diff evaluation, and noise cancellation happen within the compute environment designated by the operator.
2. Ephemeral In-Memory Telemetry
ShadowDiff operates with an ephemeral in-memory ring buffer for trace storage:
- Mirrored request and response payloads are retained exclusively in volatile system RAM for live inspection and diffing.
- No mirrored payloads are written to external disk or sent to third-party analytics services.
- When the ring buffer limit is reached, older traces are evicted automatically.
- Upon process termination or container restart, all stored traces are immediately erased.
3. Zero-Trust PII Redaction Engine
To prevent accidental capture of sensitive personal information in traffic mirrors, ShadowDiff includes an integrated, zero-allocation data redactor:
- Credit card primary account numbers (PAN) validated via Luhn algorithm are masked before diffing.
- Social Security Numbers (SSN), JSON Web Tokens (JWT), API secret keys, passwords, and sensitive headers (Authorization, Cookie, X-Api-Key) are sanitized.
- Redaction occurs in memory prior to payload storage, diffing, or test synthesis.
- Operators can define custom redaction patterns and field denylists through the configuration file.
4. Self-Hosted and Air-Gapped Operation
ShadowDiff can be operated fully disconnected from external networks:
- For regression test synthesis, ShadowDiff supports local, private LLMs via Ollama, vLLM, or any OpenAI-compatible local endpoint.
- When local providers are configured, zero payload bytes leave your VPC or local host.
- If external providers are explicitly enabled by the operator, only sanitized diff schemas are transmitted.
5. Cookies and Web Tracking
The ShadowDiff web console does not use tracking cookies, browser fingerprinting, marketing beacons, or third-party tracking scripts. The console communicates solely with your local or self-hosted ShadowDiff daemon endpoints.
6. Operator Responsibilities
Operators of ShadowDiff are responsible for ensuring their traffic mirroring policies comply with applicable data protection laws, including GDPR, CCPA, and HIPAA. We recommend enabling the PII redactor and using dedicated staging or synthetic traffic whenever practical.
7. Contact and Inquiries
For questions regarding this privacy policy or the security design of ShadowDiff, submit an issue or security advisory on the official GitHub repository at github.com/vishalrajofficial/ShadowDiff.
ShadowDiff Open-Source Project