No JSON required
The whole policy lives behind a clean UI. Click the entity types you care about, pick a strategy from a dropdown, set thresholds with a slider. Save and download — Philter takes it from there.
Build redaction policies without writing JSON
The Redaction Policy Editor is a web console for the non-engineers who actually own the privacy policy — compliance officers, privacy leads, healthcare administrators. Click to choose entity types, drag to order conditions, save as a Philter policy file. Hosted free at policies.philterd.ai, and open source if you want to run your own.
The whole policy lives behind a clean UI. Click the entity types you care about, pick a strategy from a dropdown, set thresholds with a slider. Save and download — Philter takes it from there.
Paste a few lines of sample text and see exactly what the current policy redacts. Tune by experiment, not by guessing — and not by waiting for a CI run.
Output is a Philter-compatible JSON file. Drop it into a Philter deployment with no transformation — what you see in the editor is exactly what runs in production.
Use the editor at policies.philterd.ai — no signup, no payment, no data collection. Or run your own copy from source.
The team that knows the regulation isn't usually the team that writes the JSON. The editor lets compliance own the policy directly — engineering reviews and ships, instead of translating requirements into config.
Apache 2.0 on GitHub. Audit the code, fork it, run it offline, customize the workflow — whatever your privacy posture demands.
Three ways to get going — deploy the open source yourself, spin it up from a cloud marketplace, or work with our team directly. Pick the path that fits.