Two people at the same company summarise the same quote for a customer. One is logged into a personal ChatGPT account, the other into the company tenant. Same document, same prompt, same customer name and margin in the text. For one of them this is a reportable incident and for the other it is Tuesday, and the difference has nothing to do with what either of them did.
That is what makes "is AI safe for company data" a bad question to put to a board. It sounds like one question and it is four. They have different answers and different owners, and three of them were settled long before anyone opened a chat window.
One: which account is this?
The largest variable, and it is almost never about the tool. Nearly every major AI vendor runs two products under one brand: a consumer version and a business version.
On the business tier, the vendor does not train on your input by default, a data processing agreement (DPA) is in place and retention becomes configurable. OpenAI states that split explicitly for ChatGPT Business, Enterprise and the API. On the consumer tier none of that applies, and the training toggle is usually on from the start.
Same person, same prompt, same tool. The only difference is which button they logged in with. If you fix one thing this quarter, fix this one, because it is the only part of the four that you can enforce centrally.
More on this in our comparison of free and business AI accounts and, for ChatGPT itself, in our article on using ChatGPT safely at work.
Two: what does the contract say, and where is the vendor based?
A DPA governs what the vendor may do with your data. Necessary, but not the same thing as safe. Three clauses worth reading properly:
- Retention. How long do conversations persist, including after deletion? Thirty days post-deletion is the common default, and it is a promise rather than a property. In the New York Times litigation, OpenAI was ordered to preserve output logs that users had deleted, including temporary chats. That obligation ended on 26 September 2025, and conversations from the EEA, Switzerland and the UK are no longer held for the case. Retention policies hold until a court decides otherwise.
- Human review. Almost every provider reserves the right to have staff review conversations on suspicion of abuse. That is separate from training, and it survives the training opt-out.
- Transfers. Is the vendor in the EU, or only its data centre? A US company with a Frankfurt region is still a US company. See data sovereignty starts in the prompt field.
Three: what goes into the prompt?
Here is the gap. The first two questions get answered by procurement, legal and IT: once, deliberately, usually well. The third gets answered dozens of times a day by someone finishing something before a meeting.
It is also the only one still open at the moment it matters. The account is fixed, the contract is fixed, but whether the customer name and the margin travel with that quote is a live decision right up until someone hits send.
The useful question there is not "am I allowed to" but "does the model need this". Shortening a quote works without the customer name. Rewriting a complaint response works without the account number. Reviewing a cover letter works without the date of birth. Ask that question and half the sensitive data usually falls out on its own, with no loss to the task.
Four: who can reach it afterwards?
The forgotten one. Your data sits with the vendor, and also in a conversation that persists.
On a business tier, an administrator can in principle reach it through the admin and export functions that come with the plan. That is usually the reason you bought the plan, and it is still worth knowing before anyone types something personal into it. See our article on whether an admin can read your AI chats.
Then there are integrations. Assistants that sit in your mail, your documents, your project tooling. Each connection widens what the tool can see, and that widening is rarely reassessed after the day it was switched on.
When the answer is simply no
For some cases, breaking the question down makes no difference: the answer is no regardless.
Special category data under Article 9 (health, ethnicity, beliefs, criminal matters) does not belong in a general-purpose assistant, business tier or not. The same holds for anything covered by legal privilege or a professional duty of confidence: that is not a data protection rule you can settle with a DPA; it is an obligation attached to the professional.
And if you cannot answer the four questions above, that is itself the answer. Not because something is certainly going wrong, but because you would not find out if it were.
So the honest summary for a board is that three quarters of this question is procurement and configuration, and the remaining quarter is a moment. That moment belongs to someone who is finishing a task and not thinking about policy, which is why the only intervention that changes anything happens there: showing what is in the text before it leaves, so the decision sits with a person rather than with nobody.
