Support
Get help with Philter, Philter Desktop, and the Philterd toolkit.
Get help with a product
Core redaction
- Philter Redaction API Guides Documentation Issues
- Phileas Redaction Library Guides Documentation Issues
- Philter Desktop Desktop app Guides Documentation Issues
AI models & LLM guardrails
- Philter AI Proxy LLM proxy Guides Documentation Issues
Discovery & monitoring
- Phinder Discovery Guides Documentation Issues
- Phield Monitoring Guides Documentation Issues
Review, policy & operations
- Philter Scope Benchmarking Guides Documentation Issues
- Philter Workspace Human review Guides Documentation Issues
- Philter Diffuse Differential privacy Guides Documentation Issues
- Redaction Policy Editor Policy editor Guides Documentation Issues
Components
- PhEye AI Models & Server Guides Documentation Issues
- PhiSQL Query language Guides Documentation Issues
Redaction policies
A redaction policy is the JSON file that tells Philter, Phileas, and Philter Desktop which PII to look for and what to do with each match. A policy from the library is a starting point, not a finished control: measure it on your own documents before you rely on it.
Policy library
Ready-to-use policies for HIPAA, PCI DSS, FRBP 9037, FERPA, GLBA, AI training data, and more, free under the Apache License.
Browse the libraryWrite your first policy
A hands-on walkthrough from an empty file to a working policy: detect a type, change how it is redacted, and handle false positives.
Start the walkthroughPolicy schema reference
What each part of a policy does, how filters and strategies fit together, and the JSON schema every policy follows.
Read the referenceOther ways to write one
Build a policy in a form with the Redaction Policy Editor, or write it as readable PhiSQL that compiles to the same JSON.
Write a policy in PhiSQL
Ways to get support
Free · Open source
Community support
For everyone using the open source toolkit
Development happens in public. When you file an issue, you reach the engineers who wrote the code, with no support-tier triage in between.
- Documentation Start with your product's support page above, which collects its guides, documentation, and issue tracker. The knowledge base covers how-tos and troubleshooting across the toolkit, and products and packages links every product's docs. If something is wrong or missing, open an issue and we will fix it.
- Issue trackers Report bugs, request features, and ask questions in each product's repository under github.com/philterd. We triage weekly.
Free to use, with no support contract required.
Commercial license
Philter & Philter Desktop
Included with a commercial license
Direct support from the team that builds the toolkit, for production deployments that need a service-level agreement, a custom evaluation on your own data, or hands-on engineering.
- Direct email support Reach the team at support@philterd.ai or the contact form. Keep your receipt handy as proof of entitlement. Please do not send PII or PHI.
- SLAs, evaluations & engineering For a service-level agreement, a custom evaluation on your own data, or hands-on engineering, see commercial support and consulting. We work directly with healthcare, finance, legal, and government teams.
Reporting a security issue
Please do not report security vulnerabilities through public GitHub issues. Email security@philterd.ai and follow the responsible-disclosure process. We acknowledge receipt within two business days.