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
Redaction Policy Editor
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.
Why a visual editor
Live preview
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.
Exports a valid Philter policy
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.
Hosted for free
Use the editor at policies.philterd.ai. No signup, no payment, no data collection. Or run your own copy from source.
Bridges compliance and engineering
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.
Open source
Open source on GitHub under the permissive and business-friendly Apache license. Audit the code, fork it, run it offline, customize the workflow: whatever your privacy posture demands.
Frequently asked questions
If something here isn’t covered, get in touch and we’ll answer.
What is the Redaction Policy Editor?
It is a web console for building Philter redaction policies through a visual, no-code interface. Click to choose entity types, pick a redaction strategy from a dropdown, set conditions and thresholds, and save the result as a Philter policy file. It's aimed at the people who own the privacy policy but don't write JSON: compliance officers, privacy leads, and healthcare administrators.
Do I need to install anything?
No. The editor is hosted free at policies.philterd.ai, with no signup and no payment. If you'd rather keep everything inside your own perimeter, it's open source and you can run your own copy from source.
What does it produce?
A standard Philter-compatible JSON policy file. Drop it into a Philter deployment with no transformation: what you build in the editor is exactly what runs in production.
Can I see what a policy will redact before I export it?
Yes. Paste a few lines of sample text into the live preview and the editor shows exactly what the current policy redacts. You tune by experiment instead of guessing, and without waiting for a CI run.
Who is it for?
The team that knows the regulation usually isn't the team that writes the config. The editor lets compliance and privacy leads own the policy directly, then hands engineering a valid policy file to review and ship, instead of asking engineers to translate requirements into JSON by hand.
Is it open source?
Yes, on GitHub under the permissive, business-friendly Apache License, version 2. Audit the code, fork it, or run it offline, whatever your privacy posture demands.
Ready to use Redaction Policy Editor?
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.