No JSON required
The whole policy lives behind a clean UI. Choose the entity types you care about, pick a strategy from a dropdown, and add an optional condition such as confidence > 0.8. Download the file and 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. Choose entity types and strategies from forms, test against sample text, and download a Philter policy file. Hosted free at policies.philterd.ai, and open source if you want to run your own.
Build a policy without writing JSON
Pick the entity types to act on, choose how each one is handled, and the editor writes a valid Philter policy file for you. Hand the export straight to Philter.
healthcare-intake.json
- SSN / TIN Encrypt (FPE)
- Phone number Mask
- Email address Replace
policy file
{
"identifiers": {
"ssn": { "ssnFilterStrategies": [{ "strategy": "FPE_ENCRYPT_REPLACE" }] },
"phoneNumber": { "phoneNumberFilterStrategies": [{ "strategy": "MASK" }] },
"emailAddress": { "emailAddressFilterStrategies": [{ "strategy": "STATIC_REPLACE", "staticReplacement": "[email]" }] }
},
"fpe": { "key": "env:PHILTER_FPE_KEY", "tweak": "env:PHILTER_FPE_TWEAK" }
}
No JSON by hand. Compliance sets the intent, and engineering reviews a policy file Philter can load.
Why a visual editor
Test before you export
Paste a few lines of sample text and run the current policy against it to see what it redacts. Tune by experiment, not by guessing, and not by waiting for a CI run.
Exports a valid Philter policy
Output is a Phileas policy JSON file that Philter loads with no transformation. The editor tests with its own copy of Phileas, which can be a different version from your Philter, so confirm results in Philter before production.
Hosted for free
Use the editor at policies.philterd.ai. No signup and no payment. The policy and any sample text you test are sent to the editor's server to build and test the policy, and are not stored. 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. Philter loads it with no transformation. The editor tests with its own copy of Phileas, which can be a different version from your Philter, so confirm results in Philter before production.
Can I see what a policy will redact before I export it?
Yes. Paste a few lines of sample text into the Test Policy panel and the editor shows 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.