Personal or confidential information can end up sent to an external AI service without anyone meaning it to. Security Filter guards that entry point.
Security Filter detects PII before it reaches a model. Detect-and-warn comes standard from Team, and sending it masked with restore-on-response comes standard from Business.
Scan outgoing content for PII.
Mask what's detected.
Send the masked content to the model.
Restore the masked content when the response arrives.
Included on Team, Business, Business+, and Enterprise. Detection precision and scope grow with the plan.
| 項目 | Team | Business | Business+ | Enterprise |
|---|---|---|---|---|
| Detect and warn | Yes | Yes | Yes | Yes |
| Secret-variable masking | — | Yes | Yes | Yes |
| Auto-mask and restore | — | Yes | Yes | Yes |
| Contextual detection + mask-event audit view | — | — | Yes | Yes |
| Custom detection rules, BYO dictionaries & org-wide enforcement | — | — | — | Yes |
Team gets detect-and-warn, and Business gets automatic mask-and-restore, standard. Business+ adds contextual detection and mask-event audit log viewing on top of that. Custom detection rules, bringing your own detection dictionary (BYO), and an org-wide policy that individual users can't turn off are available to discuss through the Enterprise program.
Security Filter isn't meant to replace perimeter DLP (Data Loss Prevention) — it's designed to work alongside it. Where perimeter tools inspect traffic broadly, Security Filter focuses specifically on content sent to AI models, detecting and masking it before it goes out.
Contextual detection is available on Business+. A tenant-level extension for custom detection dictionaries and rules tailored to your organization is available on Enterprise.
Want to talk about your rollout? Use the contact form.
Try all four modes, including Security Filter, free.
Start free