An AI policy layer is an important part of every source of AI-generated text because it inspects the AI-generated text to prevent sensitive information from being exposed. A policy layer can help remove information such as names, addresses, and telephone numbers from responses.
In this blog post we will describe the function of an AI policy layer and how Philter is well-suited for the role. Philter is available on the AWS Marketplace, Google Cloud Marketplace, and the Microsoft Azure Marketplace.
As Cassie Kozyrkov wrote in her blog post linked below, "If you care about AI safety, you’ll insist that every AI-based system should have policy layers built on top of it. Think of policy layers as the AI version of human etiquette." - AI Bias: Good intentions can lead to nasty results
An AI policy layer is a part of your AI architecture that sits between your chat bot (or other source of AI-generated text) and your end-user. The role of an AI policy layer is to inspect the AI-generated text for sensitive information and remove it before sending the text to the user.
An AI policy layer is needed because it can be extremely difficult to know what data an AI model was trained on. Even when due diligence is done and care is taken, sensitive information can find its way into training data and it can be hard to detect simply due to the vast size of the training data.
Philter was designed to integrate into virtually all types of applications. Philter's API is very simple and can be called from any application. With its text-in and redacted text-out operation, Philter can receive your AI generated text, inspect it for sensitive information based on your configuration, and redact any that is found.
Yes! How Philter finds and redacts sensitive information is defined in a file called a filter profile. A filter profile can be thought of as a policy because it lets you specify what types of sensitive information should be redacted. You can create as many filter profiles as you need.
A policy layer is an important part of every source of AI-generated text. The policy layer inspects AI-generated text to prevent sensitive information from being exposed.
Philter can be deployed and used as an AI policy layer. Philter's ability to find and remove sensitive information in text along with its API makes it ideal for integrating into an AI architecture.
Philter can be configured to redact over 30 types of PII, PHI, and user-defined sensitive information.
Philter's simple redaction API can be called from Python, Java, .NET, or any other language.
Philter can identify and redact over 30 types of PII, PHI, and other types of sensitive information. It is highly configurable and gives you control over how PII and PHI should be redacted through features like consistent anonymization, redaction logic, and multiple filter profiles.
Copyright 2023 Philterd, LLC. All Rights Reserved .
