Industry Insights

DLP Policy Examples and Template for AI Tools 

6
Mins Read

Table of Contents

Still relying on traditional DLP for AI?
There's a better way.

Semantic Understanding

Real Time Inline Action

Dynamic Policy Engine

Get A Free POC

Trusted by 55+ regulated organizations

Key takeaways

  • A DLP policy for AI tools needs three things per data type; the condition, the action (Allow, Warn, or Block), and the message the employee sees.
  • Start with Warn for most data and keep Block for secrets and clearly restricted material, because coaching builds the habit and shows you where real risk sits.
  • The template and seven examples below work on any tool, and Wald AI can apply this kind of policy on the device before a prompt is shared.
AI-Native DLP and the Future of Enterprise AI Security

An executive whitepaper on how AI-Native DLP differs from legacy DLP, and what it means for enterprise security strategy.

Download Whitepaper

A founder writes a one-page AI rule: no confidential data in AI tools. Two weeks later a sales lead asks whether a customer's email thread counts, and nobody can answer. The rule was right, but it was not a DLP policy anyone could follow, because it never said what to do with each type of data. A working DLP policy names the data, the action, and the words the employee sees when the action fires.

Below we give DLP policy examples you can copy, a full template for AI tools, and a four-week plan to roll it out in a small team.

‍

Allow, Warn or Block?

Match the action to the data class.

Allow

Public content

Published copy, draft posts
Warn

Internal material

Meeting notes, plans
Block

Restricted data

API keys, code, pay details

What a DLP policy is, and what changes when the channel is an AI tool

A DLP policy is the written set of rules that says which data must not leave the company, through which channels, and what happens when someone tries. Classic templates cover a long list of sections: purpose, scope, roles, data classification, monitoring, and incident response. Those sections still matter, and we keep them in the template further down.

What changes with AI tools is the moment of enforcement. Nothing is attached or copied to a drive, so the policy has to act on the prompt itself, before it is shared. NIST's Generative AI Profile lists data privacy among its twelve generative AI risks, which is a useful reason to put the rules in writing early. The wider idea of data exposure is also worth sharing with your team, since it explains why a prompt can leak data without any file moving.

Allow, Warn, or Block: choosing the right DLP rules

DLP rules for AI tools come down to three actions. Choosing between them is the main job of the policy.

Action When it fits Example What the employee sees
Allow Public or low-risk content, approved tools Drafting a blog outline from public notes Nothing; the event is still logged
Warn Internal material, first-time or unclear cases Pasting meeting minutes into an approved assistant A short message explaining why it was flagged, with a choice to continue or edit
Block Secrets and clearly restricted data A prompt containing an API key A message that says what was found and what to do instead

Microsoft's endpoint DLP, for example, lets admins audit, block with override, or block a paste based on the content and the destination site, which shows how widely this tiered idea is used. The principle is the same in any tool: save ‘Block’ for the cases where a mistake is expensive, and use ‘Warn’ everywhere else so people learn the line instead of working around it.

DLP policy examples for AI tools you can copy

Each DLP policy example below is a starting point. Change the wording to match your tools, your team's vocabulary, and your own risk tolerance.

1. Secrets. Credentials are the easiest case to write because the cost of a mistake is high and there is rarely a good reason to paste them. This policy covers API keys and other secrets.
‍

Policy Example

Policy:
Block secrets in AI prompts
Condition:
A prompt or upload contains an API key, access secret or database login.
Action:
BLOCK

Message shown to employee

"This looks like a secret key. Remove it and try again. If you need help sharing it safely, ask IT."


2. Code.
Developers use AI tools constantly, so a blanket ban gets worked around. Splitting by account type keeps the policy usable for source code from company repositories.
‍

Policy Example

Policy:
Protect proprietary source code
Condition:
A prompt or upload contains source code from company repositories.
Action:
BLOCK · Personal accounts WARN · Approved tools

Message shown to employee

"This looks like company code. Use the approved tool, or share only the part that shows the problem."


3. Customer information.
This is where small teams most often slip, because drafting a reply is the most natural use of an assistant, and the data involved is usually customer data and PII.
‍

Policy Example

Policy:
Warn on customer information
Condition:
A prompt contains customer data with names, emails or account details.
Action:
WARN

Escalation threshold

BLOCK When PII involves more than 10 people

Message shown to employee

"This includes customer details. Remove names and contact info, or confirm this tool is approved for customer data."


4. People and pay.
Compensation questions are sensitive in a small team where everyone knows everyone, which is why salary data gets its own rule.
‍

Policy Example

Policy:
Block salary details
Condition:
A prompt contains salary data for named people or roles.
Action:
BLOCK

Message shown to employee

"Pay details can't be shared with AI tools. Describe the situation without names or amounts."


5. Contracts.
Contracts are long, so one paste of a contract or an NDA can expose a lot at once.
‍

Policy Example

Policy:
Warn on contracts and NDAs
Condition:
A prompt or upload contains a contract or an NDA.
Action:
WARN

Message shown to employee

"This looks like a contract or NDA. Summarize it yourself first, or ask legal before sharing."


6. Internal notes.
Leadership material often carries plans that are not public yet, such as meeting notes or a board deck.
‍

Policy Example

Policy:
Warn on internal planning material
Condition:
A prompt contains meeting notes or a board deck marked internal
Action:
WARN

Message shown to employee

This looks like internal planning material. Share only what the task needs.


7. Public content.
A policy that only restricts looks like a ban, so write the Allow rule too.
‍

Policy Example

Policy:
Allow public marketing content
Condition:
A prompt contains published website copy, public product descriptions or draft posts with no customer details
Action:
ALLOW
Activity logged

Why DLP rules written as patterns fall short

A pattern rule catches a card number, but it misses a paragraph of unreleased pricing, because nothing about that paragraph looks like a known format. Manual policies can only address known behaviors, but AI interactions are dynamic and constantly evolving, so by the time a new data exposure risk is discovered, it may be too late to configure a policy to prevent it.

Our view at Wald AI is that a policy is only as good as its ability to tell what a prompt means, so we write conditions about what the data is and what the person is doing with it, and we let classification decide whether a prompt matches. We also start with Warn, because the best AI policy is the one employees do not work around. Wald AI is a solution that uses multiple small language models (SLMs) on your device to spot sensitive data in prompts, understand what it means, and apply the right policies before it is shared with ChatGPT, Claude, or another AI tool. When it flags a prompt, it coaches the employee on why, so the message in each policy above does real work instead of being a generic warning.

The DLP policy template for AI tools (copy and edit)

We built this template for small teams, so copy it into your policy document and replace the brackets.
‍

AI Governance · Policy Template

The DLP policy template for AI tools

A practical starting point for small teams. Use this template to establish how company data can be shared with AI tools and what happens when a policy is triggered.

Highlighted fields Add your organisation's details before adopting this policy.

Policy foundations

  1. Purpose: Protect company data while letting people use AI tools to do their work.
  2. Scope: All employees and contractors, all AI tools they use, including personal accounts on company devices.
  3. Approved tools: [Insert approved AI tools]. Any tool not listed defaults to Warn.

Data classification and enforcement

  1. Data classes: Restricted (secrets, source code, pay details), Internal (customer details, plans, notes), Public (published content).
  2. Actions: Restricted = Block. Internal = Warn. Public = Allow.
  3. Exceptions: [Specify roles], approved by [Policy owner], reason logged.

Employee guidance

  1. Coaching: Every Warn or Block explains the reason in plain words and says what to do next.

Monitoring and accountability

  1. Logging and review: Every interaction is logged. [Policy owner] reviews flagged events every month.
  2. Incident response: If sensitive data was shared, [Policy owner] is told the same day, and the account and data are checked.
  3. Review: Update this policy every quarter and whenever a new AI tool is adopted.

Replace all highlighted fields with your organisation's details. Review the policy before putting it into effect.


Every interaction is logged, including what was detected and what action was taken. These audit logs help your team support its compliance efforts, while Wald AI's zero data retention policy and SOC 2 Type II report provide additional assurance.

How to roll out the policy in four weeks

A new policy lands better when people see it working before they see it blocking.

  1. Week 1: Turn it on in log-only mode. You learn what people actually paste before anyone is interrupted.
  2. Week 2: Switch the internal class to Warn, so employees start seeing the messages and learning the line.
  3. Week 3: Switch secrets and code on personal accounts to Block, because those cases are clear.
  4. Week 4: Review the log, tune the conditions, and write down the exceptions you approved.

Conclusion

A DLP policy for AI tools works when it is short enough to read and specific enough to enforce: one action per data type, one clear message per action. Start with the template, adapt the seven examples to your team, and begin with Warn so people learn the line. If you want to see how contextual classification applies a policy like this on a real team's AI use, see Wald AI in action.

‍

Frequently Asked Questions

What is a DLP policy?

A DLP policy is a written rule set that says which data must not leave the company, through which channels, and what happens when someone tries. For AI tools it names the data types, the action for each (allow, warn, or block), and the message the employee sees.

What are DLP rules, and how are they different from a policy?

DLP rules are the individual conditions and actions inside a policy, such as "block a prompt that contains an API key." The policy is the whole document with purpose, scope, roles, and review; the rules are the parts that a tool actually enforces.

How many DLP policies does a small business need?

Most small businesses need one policy with three or four rules grouped by data class: restricted, internal, and Public. Separate DLP policies only become useful when teams handle very different data, such as finance and engineering.

Should we block ChatGPT outright?

Usually not. A full block pushes people to personal accounts and phones, where you have no visibility at all. A tiered policy keeps the tool available for routine work and stops only the data that should not leave.‍

Still relying on traditional DLP for AI?
There's a better way.

Semantic Understanding

Real Time Inline Action

Dynamic Policy Engine

Get A Free POC

Trusted by 55+ regulated organizations