Quick fixes AG-S002

That data belongs to someone else

Shared methods · A shared method; linked tool guides explain the exact steps.

Your colleague's appraisal, a customer's complaint, your friend's medical story — pasting it is a decision about their data that only you were present for.

Quick fix: That data belongs to someone else

Instead of Paste the whole complaint email, name, address and account history included, to draft a reply.

Try A customer is upset because [the situation, no identifiers]. Their key points: [paraphrased]. Draft a reply in a calm, concrete tone.

The reply needs the situation, not the person.

Why this works

Your own data is yours to risk; other people's is not, and they are not in the room when you paste. Names, addresses, health details, employment matters: the identifying parts are almost never what the model needs to help. The situation, the pattern, the ask: those carry the task. And "anonymised" needs honesty; a rare job title plus a small town plus an age is a name in three pieces. Describe the case one step more generally than feels natural, and the answer quality survives while the exposure does not.

When this applies

The paste contains a real person who is not you: a colleague, a customer, a patient, a family member, an applicant — especially in work contexts where data-protection duties attach to exactly this.

Template

The situation: [what happened, roles instead of names]. What I need: [the task]. (Nothing in this describes an identifiable person.)

Go deeper

The full classification, and the consumer-vs-work-account difference that most people miss: what data may go in. The absolute cases live in what never goes in a prompt, and teams handling the strictest categories have their own page.

Improve next

Last verified · Reviewed by Timothy Fehr