Privacy

In-Flight Data Redaction

Strip secrets, PII, and sensitive payload fields from requests and responses before they reach logs or downstream services — without changing application code.

Start for Free Read the Docs

Redact at the Edge

Sensitive fields are removed from the request and response at the proxy so callers never see the raw values.

Pattern & Path Based

Remove by JSON path, header name, or regular expression — so credit-card-shaped strings disappear wherever they appear.

Compliance Ready

Reduce blast radius of breaches and support GDPR, HIPAA, and PCI obligations with one consistent layer of defense.

Privacy

Filter Payloads Without Touching Code

Define dynamic filters that remove specific JSON fields, headers, or regex matches on requests and responses. Roll a change out in seconds without redeploying any code.

Learn more in the docs

Payload Filter

BEFOREAFTER

{

"user_id": "usr_0xA4f3" ,

"email": "alice@example.com" ,

"route": "POST /api/users" ,

"card_number": "4111 1111 1111 1111" ,

"status": "200" ,

"ssn": "123-45-6789" ,

}

Active Filters

^email$^card_number$^ssn$

Privacy

Real-Time Telemetry

Every redaction decision is logged and can stream to your existing logging and SIEM stack (Enterprise only). See successful and suspicious patterns the moment they emerge.

Learn more in the docs

Redaction Coverage

LIVE

field^card_number$

8,241redacted

field^ssn$

3,108redacted

field^email$

21,093redacted

Authorization

1,872redacted

regex\d{3}-\d{2}-\d{4}