The day Samsung banned ChatGPT

A few keystrokes is all it took. An employee, trying to fix a problem faster, pasted confidential source code into a chatbot. The work got done. The data was gone. Not deleted, gone in the worse sense: copied into a system the company did not control, could not audit, and could not call back.

This is the story of how one of the largest technology companies in the world learned that lesson in public, and what it means for anyone who handles information they are paid to protect.

What happened at Samsung

In April 2023, as widely reported, employees in Samsung's semiconductor division turned to ChatGPT to speed up their work. In separate incidents, staff reportedly pasted confidential material into the tool. One case involved internal source code. Another involved notes taken from a recorded internal meeting.

The intent was not malicious. These were people doing their jobs, using a tool that felt like a smarter search box. They wanted faster answers, cleaner code, a tidy summary. The chatbot delivered. What they did not see was where their words went after they hit enter.

Shortly after, Samsung acted. The company restricted, then banned, the use of generative AI tools like ChatGPT on company-owned devices and networks. It also limited the size of prompts employees could send. A ban is a blunt instrument, and companies do not reach for blunt instruments when the stakes are small.

Samsung was not alone. Around the same period, other large organisations did the same. Banks including JPMorgan restricted employee use of public chatbots. Apple and Amazon placed limits of their own. Different industries, same fear: well-meaning staff sending out data they should never have sent.

Why one prompt is one too many

Here is the part that should worry every privacy officer and every lawyer reading this.

When you paste text into a public AI tool, you are not borrowing the tool. You are handing over a copy. That copy now lives outside your walls. It may be stored. It may be reviewed by humans for quality and safety. It may, depending on the terms and settings, be used to train future versions of the model.

You cannot un-send it. There is no recall button that reaches into someone else's servers and scrubs your trade secret, your client's name, or your draft settlement figure. Once private data is in a prompt, it has left your control, and the only honest assumption is that it is gone.

A confidential document does not stop being confidential because it was useful in the moment. The leak is not the breach you read about later. The leak is the paste.

Think about what passes through a normal working day in a law firm, a clinic, or a finance team:

• Client names tied to sensitive matters
• Draft contracts and settlement terms
• Patient details and case histories
• Internal source code and system designs
• Financial figures that are not yet public

Every one of these is something a professional is trusted to keep. And every one of these is exactly the kind of text someone might paste into a chatbot to "just get a quick summary."

The trap is the tool feels safe

The reason this keeps happening is not that people are careless. It is that the tools feel private.

A chat window looks like a conversation with one assistant. It feels closed, personal, yours. Nothing about the experience signals that your words are travelling to a third party. There is no warning label on the box that says: anything you type here may leave the building.

So the gap is not a gap in good intentions. It is a gap between how the tool feels and what the tool does. You can write a policy that says do not paste confidential data into public AI. Samsung had smart people and serious rules, and it still happened. Policies depend on every person remembering, every time, under deadline pressure. That is not a control. That is hope.

The honest conclusion is uncomfortable: if the only thing standing between your confidential data and a public AI tool is an employee's memory, you do not have a safeguard. You have a near miss waiting to be a headline.

The fix is to mask before you send

There is a better answer than banning the tools, and it is simpler than it sounds.

If the problem is that private data leaves your machine, then the fix is to make sure private data never leaves your machine in the first place. Not to slow people down. Not to block the tools that genuinely help them work. To remove the secret from the text before the text goes anywhere.

This is what masking does. Before a prompt reaches any AI, the sensitive details are stripped out and replaced. The names, the figures, the identifiers, the code that should stay home, all of it is handled on your side. The AI sees a question it can answer. It never sees the parts that would have caused the leak. Your people keep their speed. Your data keeps its place.

Samsung reached for a ban because, in 2023, masking before the prompt was not the default way of working. It can be yours.

The employees in this story were not the problem. They were trying to do good work. The problem was that there was nothing between their good intentions and a system they could not control. Put something there.

See how Velum masks private details before they reach any AI, and request a demo to see it on your own data.