Stop privacy debt at the edge.
Voidwall stops sensitive data at the edge of every request — inbound and outbound — before it spreads across internal infrastructure, external services, logs, AI systems, and storage layers.
Run it two ways: inline as an HTTP proxy that filters live traffic, or as a REST API you call to scan and redact on demand. The tag on each card shows where it applies.
Parse and scan every outgoing payload across JSON, CSV, TSV, and plain text.
Replace detected PII with placeholders like [EMAIL], [US_SSN], [FR_NIR]...
...or mask with configurable characters.
Block the entire request if contains sensitive data.
Warn when sensitive data leak is detected.
Detection coverage
Voidwall is able to detect PII using pattern recognition, contextual analysis and validation, so it warns about real values, not just looks-like ones. Here are examples of what can be detected.
Custom types can be added via configuration file.
Analytics, sanitized
Front-end tracking is the leakiest path out of a product — marketing teams add events, users paste their PII to search bars, and personal data slips into Google or Matomo unnoticed. Even 20% of websites have this problem. Voidwall may be a proxy between your product and web analytics, preventing your users' personal data from leaking out.
Specializations know what to scan — catching sensitive data even inside doubly-encoded payloads. They also know what not to scan, so the integration keeps working as intended.
Format-aware
Voidwall parses the request before it scans it. Whether the payload is a nested JSON, a flat CSV, a tab-separated data, a URL packed with query parameters, or free-form text, the same matchers apply.
Performance
Voidwall scales horizontally, runs in your cluster, and adds a budget you can measure in single-digit milliseconds. It's designed to be a lightweight, self-hosted service that doesn't break the bank as you grow.
added per request, payload size 10 KiB
single container, 6 logical cores, 10 KiB payload
single container, 6 logical cores, 10 KiB payload
Stateless by design. No shared database, no coordination between containers, no dependencies to provision first.
Pull the image and go. Runs entirely in your environment. No payloads leave your infrastructure.
Drop it inline as a reverse or forward proxy, or call the HTTP API to scan and redact on demand. Same engine, three ways to plug in.