Sensitive data in prompts: what leaves when employees paste into AI tools

Prompts carry source code, customer records, and credentials to model providers and their logs. How to classify what may be shared, configure enterprise retention settings, redact automatically, and log usage.

Lesson 44 of 69 · 10 min read · practice only with authorization

Diagram

A prompt’s path out of the company

Follow the path. One example at a time.

Step 1 of 4

Paste

An engineer pastes a stack trace with a connection string.

Illustration: Paste
psycopg.OperationalError: connection to "db.prod.internal"
 user=app password=Pr0d-S3cret! failed

The example on the open step is one illustration, or the fix you can paste into an application you own.

What this page is made of

3 pieces. Each one says what fails, who is affected, what you would notice, and what you change.

  1. Credentials in pastes

    What fails
    Logs and configs pasted for debugging carry secrets.
    Who is affected
    Systems those credentials open.
    What you would notice
    Gateway redaction counts for secret patterns.
    What you change
    Redact automatically and rotate any secret that was sent.
  2. Customer data

    What fails
    Records pasted for analysis may break contracts or privacy rules.
    Who is affected
    Customers whose data was shared.
    What you would notice
    Prompts containing many emails or account numbers.
    What you change
    Publish what data classes are allowed and block the rest.
  3. Retention terms

    What fails
    Consumer and enterprise plans differ on retention and training use.
    Who is affected
    The company, if data is kept or trained on.
    What you would notice
    Staff using personal accounts for work.
    What you change
    Provide an approved enterprise tool with zero or short retention.

A usable policy

Short rules work better than long ones. Name the approved tools, the data classes that may and may not be pasted, and what to do if something was pasted by mistake.

  • Approved: the company AI gateway and enterprise accounts
  • Never paste: credentials, customer records, unreleased financials
  • Allowed with care: internal code, after removing secrets
  • Mistakes: report to security so secrets can be rotated

Check yourself

Recognition and the fix. Nothing here is a procedure.

1 / 3

An engineer pasted a production password into a chat assistant. What is the complete response?

Sibling techniques

Pages at the same depth, plus a lab and a glossary card for this one.

This page stands on its own. The lab and the glossary card are the next reading.

Practice

  1. LabControl benchA failure is described. Choose the control that changes the outcome.

Glossary

  1. CardSensitive data in promptsPeople paste secrets and customer records into a chat box, and the log keeps them.