Can you do basic string pattern matching to prevent leaks of sensitive data?
In the case of a credit card, for instance, how would you distinguish between a user legitimately "buying something on a website" from "posting customer card to a forum" or "sending to a chatbot" (or even "inappropriately making purchase with customer card")?
Can you match the data itself against an allow/flag/deny list?
Can you run data through a local or corporately-situated LLM instructed to "Assess whether this looks potentially sensitive" via a given set of rules, and flag it to the user or a supervisor to proceed/abort?
How extensive are in-built features, and what kind of hooks and feedback/UI interaction is available for third party integrations?