---
id: ai-at-work-safety-and-privacy
lang: en
title: "AI at work: safety and privacy"
seoTitle: "AI at work: safety and privacy basics"
description: "What is safe to share with an AI tool and what is not, what happens to what you type, and GDPR in plain terms, with a short checklist to stay safe."
part: foundations
partTitle: "Foundations"
partOrder: 1
order: 4
level: Beginner
durationMinutes: 8
outcome: "Decide what you can and cannot share with an AI tool, and follow a few clear rules to stay safe."
summary: "Never paste secrets, personal data, or client confidences into a consumer AI tool. Business and enterprise plans are safer because they do not train on your data by default."
draft: false
updated: "2026-07-26"
furtherReading:
- title: "What is GDPR?"
url: "https://gdpr.eu/what-is-gdpr/"
note: "a plain-language explainer of Europe's data protection law."
- title: "How your data is used to improve model performance (OpenAI)"
url: "https://help.openai.com/en/articles/5722486-how-your-data-is-used-to-improve-model-performance"
note: "OpenAI's own account of training and controls."
- title: "Updates to our consumer terms and privacy policy (Anthropic)"
url: "https://www.anthropic.com/news/updates-to-our-consumer-terms"
note: "how Claude handles consumer data and the training setting."
- title: "Enterprise data protection in Microsoft 365 Copilot (Microsoft)"
url: "https://learn.microsoft.com/en-us/microsoft-365/copilot/enterprise-data-protection"
note: "what the business tier protects, and how."
- title: "Data collection at Perplexity"
url: "https://www.perplexity.ai/help-center/en/articles/11564572-data-collection-at-perplexity"
note: "Perplexity's data and training policy by plan."
keywords:
- AI safety at work
- AI data privacy
- GDPR and AI
- what not to share with ChatGPT
- is it safe to use AI at work
- AI company policy
quiz:
intro: "Five quick questions. Ace all five and Part 1 is in the bag."
passScore: 5
questions:
- q: "What is the safest assumption to make about a public, consumer chatbot?"
options:
- "Whatever I type disappears the moment I close the tab"
- "What I type may be stored, reviewed by a person, and used to improve the model, so I should not paste secrets"
- "It is a private diary only I can ever see"
- "It is fine as long as I delete the chat afterwards"
answer: 1
explain: "Treat a public chatbot like a postcard, not a sealed letter. On consumer tiers your text may be kept, reviewed, and used to train the model."
- q: "Which of these is fine to paste into a public AI tool?"
options:
- "A client's real name, email, and account details"
- "A colleague's salary and home address"
- "A press release your company published yesterday"
- "Your company's login and password"
answer: 2
explain: "Already public is already safe. The other three are personal or secret data that should never go into a public tool."
- q: "In plain terms, what is \"personal data\" under GDPR?"
options:
- "Only passwords and bank details"
- "Any information that can identify a living person, directly or indirectly"
- "Anything marked 'confidential'"
- "Only data about your own company"
answer: 1
explain: "Personal data is anything that can identify a person: a name, an email, a photo, even a combination of details. You are responsible for what you paste."
- q: "You need AI to help with a real customer file. What is the safe move?"
options:
- "Paste it into your personal free account and hope for the best"
- "Use the business or enterprise tool your company approved, or strip out the identifying details first"
- "Turn off the training setting and paste everything"
- "Email it to yourself first, then paste it"
answer: 1
explain: "Use the approved business or enterprise tool (covered by a data agreement), or anonymise the file first. An opt-out toggle alone is not enough."
- q: "You upgrade from the free plan to a paid personal plan (Plus, Pro, or Max). Is your data now private?"
options:
- "Yes, paying always makes it private"
- "No: paid personal plans usually train on your data just like the free tier; only business and enterprise tiers keep it out of training"
- "Yes, but only on weekdays"
- "Only if you also delete your chats"
answer: 1
explain: "Paying for a personal plan buys speed and features, not privacy. The real divide is personal versus business, not free versus paid."
pass:
badge: "Part 1 complete"
title: "Safe hands. Part 1 done."
body: "Full marks, and that is Foundations wrapped. You know what AI is, how it works, which tool fits, and how to use it without leaking the crown jewels. On to getting started with Claude."
retry: "Check the marked answers and give it another go. You've got this."
---
> **Level:** Beginner · **Reading time:** ~8 min
>
> **What you'll be able to do:** decide what you can and cannot share with an AI tool, and follow a few clear rules to stay safe.
>
> *Last checked: July 2026. How each tool handles your data changes often, so treat the tier-by-tier specifics below as things to re-check against your provider's current policy.*
Picture a new contractor on their first morning. Sharp, fast, weirdly well-read, happy to help with anything. Would you hand them the customer database and your passwords in the first five minutes? Of course not. You would let them earn it.
An AI tool deserves the same caution, for the same reason: **you do not fully control where what you tell it ends up.** This lesson is the one that keeps you (and your company) out of trouble. It is short, practical, and not about fear. Used well, AI is safe. You just need to know the handful of lines you should not cross.
## What actually happens to what you type
When you send a message to a chatbot, it does not stay on your laptop. It travels to the provider's servers, gets processed, and comes back. What happens to it *there* is the part people never think about, and it depends almost entirely on **which tier you are using.**
On a **personal, consumer account**, your conversations are commonly used to help train future models, switched on by default, with a setting you can turn off. They may also be kept for a while and, in some cases, read by a human doing safety checks. None of that is sinister, but it means your words can outlive your chat and leave your control.
On a **business or enterprise tier** (the kind a company buys for its staff), the deal is different: your data sits under a contract, it is **not** used to train the model, and it is held to tighter rules. Same chatbot on the screen, very different treatment behind it.
The one line to remember: **on anything personal or free, treat the chatbot like a postcard, not a sealed letter.** Assume someone could read it. That single habit prevents most problems.
## How the five tools handle your data
You met the five main tools in the [tool landscape](/learn/foundations/the-tool-landscape) lesson. Here is how each treats what you type, as of mid-2026. Read it and one surprise jumps out.
| Tool | Free | Paid personal (Plus, Pro, Max) | Business & Enterprise |
|------|------|--------------------------------|-----------------------|
| **ChatGPT** | Trains on your chats by default; opt-out toggle | Same as free: trains by default, opt-out toggle | Not used for training; covered by a data agreement |
| **Claude** | Trains by default (opt-out); long retention if left on | Same as free (Pro, Max) | Team, Enterprise, API: never used for training |
| **Gemini** | Used to improve; a person may review chats; control via "Apps Activity" | Same (Google AI Pro, Ultra): paying buys features, not privacy | Google Workspace: not trained, not human-reviewed |
| **Copilot** | Consumer Copilot: no enterprise data protection, keep work data out | Copilot Pro (personal): still consumer-grade | Microsoft 365 Copilot: not trained, commercial data protection |
| **Perplexity** | Trains by default; opt out via "AI data retention" | Same (Pro, Max) | Enterprise: not trained; shorter retention |
**Here is the surprise: the "Free" and "Paid personal" columns are almost identical.** Upgrading from free to Plus, Pro, or Max buys you speed, higher limits, and features. It does *not*, on its own, buy you privacy. On every one of these tools, the paid *personal* plan trains on your data by the same default the free one does.
So the real line is not free versus paid. **It is personal versus business.** The column that actually protects your data is the last one: the business and enterprise tiers, where your data sits under a contract and is kept out of training. That is why "but I pay for it" is no defence for pasting a customer file into your personal account.
Two practical takeaways. **On any personal plan, free or paid, find the data setting and turn training off** (each tool has one, named something like "improve the model", "Apps Activity", or "AI data retention"). And **for real work data, use the business or enterprise tool your company provides**, not your own subscription, however nice its features are. Defaults and settings shift often, so check your tool's current policy rather than trusting a screenshot from last year.
## The line: what never goes in a public tool
Here is the whole rule in one picture. When in doubt, ask: *would I be comfortable if this text were read aloud in a meeting, or leaked?* If not, it does not go into a public tool.
Most of the red column comes down to two ideas: **other people's personal data**, and **things that are meant to stay secret.** The green column is the good news: the vast majority of what you would actually ask AI to help with (rewrite my draft, explain this concept, structure my thinking) never touches the line at all.
And there is a neat trick that moves work from the red column to the green: **anonymise before you paste.** Swap "Devlin & Co owes us 12,400 euro" for "a client owes us four figures", and you get the same help with none of the exposure. The AI does not need the real names to draft a good chaser email.
## GDPR, in plain words
If you work in or with Europe, one law shapes all of this: **GDPR.** You do not need to be a lawyer, just to hold three plain ideas.
**One: "personal data" is broad.** It is any information that can identify a living person, directly or by piecing things together: a name, an email, a phone number, a photo, even a customer reference plus a town. It is not just passwords and bank details.
**Two: you are responsible for what you paste.** The moment you drop someone's personal data into a tool, you are handling it, and the rules that apply to your work apply to that act too. "The AI did it" is not a defence.
**Three: the tool has to be allowed to see it.** Companies sign data agreements with providers exactly so personal data can be handled properly. A random personal chatbot account has no such agreement, which is why work data belongs in the tool your company approved, not your private login.
That is the shape of it. For anything you are unsure about, your company's policy and its data protection officer are the real authority. *This lesson is general guidance, not legal advice, and your employer's rules always win.*
## Two traps worth knowing
**The unapproved-tool trap ("shadow AI").** The most common way good people leak data is not malice, it is a shortcut: the company tool feels slow or clunky, so someone quietly uses their personal free account "just this once" to get the job done. That personal account has no data agreement, no guardrails, and trains on what you paste. If your company gives you an approved tool, use *that*, even when the free one is one tab away. If it does not have one yet, that is worth raising, because people will reach for AI regardless, and it is safer to give them a proper tool than to pretend they are not using one.
**The oversharing-to-be-helpful trap.** AI feels like a conversation, and conversation invites you to spill the full backstory: the real names, the actual figures, the messy details. Resist it. The AI almost never needs the sensitive specifics to help. Give it the *shape* of the problem, not the confidential guts, and you get the same quality of answer with none of the risk.
## Already pasted something you shouldn't have?
It happens, and panicking helps no one. Do three things, calmly. **First, tell whoever needs to know:** your manager, and your data protection or security contact. Speed matters more than looking flawless, and a leak of real personal data may carry reporting duties with a clock on them. **Second, limit the spread:** delete the chat, and on a personal account turn off the training setting so future chats are not used (be honest with yourself that this does not un-send what already went). **Third, write down what happened:** what you pasted, when, and in which tool, so the people who handle these things can judge the actual risk. One reported slip is a small problem. A hidden one is how small problems become big ones.
## Pause before you paste
You will not weigh all this every time. You do not need to. Just run a two-second gut check before pasting anything sensitive:
**Whose is it?** If it is about a real, identifiable person and it is not you, stop and think.
**Is it secret?** If it is confidential, under an NDA, or not public yet, keep it out of public tools.
**Which tool am I in?** Real work data belongs in the business or enterprise tier your company approved, not a personal account.
Pass those three and you are almost always fine. Fail one and you have your answer: anonymise it, move to the approved tool, or leave it out.
## Try it
Make your own "never paste" list, tailored to your job. Spend two minutes writing down the specific things *you* handle that should never go into a public chatbot: the client names, the systems, the documents, the numbers. Be concrete.
Keep that list where you will see it. A rule you wrote for your own work sticks far better than a generic warning, and it turns "should I paste this?" from a daily worry into a glance at a list you already trust.
*(General exercise. Role and industry versions come once accounts are in.)*
## Key terms
[GDPR](/glossary#gdpr), [Personal data](/glossary#personal-data), [Anonymisation](/glossary#anonymisation), [Enterprise tier](/glossary#enterprise-tier), [Prompt](/glossary#prompt)