data protection

ChatGPT and customer data: what Swiss data protection means for SMEs

AA
Aurum Avis Labs Author
6 min read

ChatGPT and customer data under Swiss law

May staff paste client or customer data into ChatGPT? The Swiss Data Protection Act still applies. There is no separate AI statute that replaces it. In German the revised act is the nDSG; in English you will also see FADP. Whoever processes personal data with an AI tool stays responsible for it. A foreign vendor does not take that responsibility away. This article is not legal advice. It is the traffic light a small Swiss office can use before the next contract, invoice, or complaint gets pasted into a prompt.

The FDPIC states the same starting point: the Data Protection Act is technology-neutral, and the controller remains responsible when personal data is processed with AI. Read that page if you need the authority’s own wording. Do not treat this blog as a substitute for it, or for advice on your specific file.

“Customer data” in an SME is usually concrete. A name plus an email. An invoice with an address. A quote tied to a company and a contact. A sick note scanned into the inbox. A payroll list. If a person can be identified from what you paste, treat it as personal data and use the red basket below until someone who owns the decision says otherwise. If you are unsure, red is the working assumption.

Free, Plus, and the company account

On ChatGPT Free and Plus, OpenAI may use content to train models unless the user opts out. Customer files, named quotes, sick notes, or payroll lists do not belong there. Opting out is a setting on a personal account you do not control, on a phone you do not own. That is a poor place to keep a mandate file.

Business, Team, and Enterprise plans, plus the API: OpenAI says organisational data is not used for training by default, and a data processing addendum exists. That does not green-light especially sensitive data. It is the difference between “a private account on a phone” and “the firm has a contract and an allow-list”.

The company stays responsible either way. A subscription is not an internal rule. People still need to know which tool is the contracted one, and which files may go into it. Pasting a whole customer dossier into a Team workspace because “it is the paid plan” skips that second decision.

A practical test before anyone pastes: could this text appear on the website tomorrow without a phone call to the customer? If yes, it is probably public. If you would not pin it on the noticeboard in reception, do not put it in a free chat to save ten minutes on a draft.

Traffic light: three baskets

  • GreenPublic

    Press copy and figures already on the website. No personal data in the prompt.

  • AmberInternal

    Anonymised samples or process notes without names. Not the private Free chat for trade secrets.

  • RedPersonal

    Names, salaries, mandate files, health data. Not in Free or Plus. Only in the contracted channel, with a human check.

If the basket is unclear, treat it as red.

Amber is the one people stretch. “I removed the company name” is not anonymised if the project, the amount, and the city still identify the customer to anyone in your market. A process note (“we file supplier invoices on Tuesdays”) can be amber. A process note with the customer’s name in the example is red. Trade secrets are not personal data, and they still do not belong in a private Free chat. Amber means an internal, contracted tool, or no tool.

Red includes anything you would call sensitive in ordinary speech: health, salary, a dispute with a named person, identity documents. It also includes sensitive personal data under the FADP (for example sick notes or information on beliefs or union membership), even when you have a company plan. The contracted plan is the starting point for ordinary customer correspondence you have decided may be drafted there, not a blanket permission for those files. When the text will be sent back to a customer, a person in the firm reads it first. The model drafts. It does not send.

If someone already pasted a client file

This is an operational response, not a statement that you have met the Act. Stop pasting more of that file into the same chat. Tell the person who owns the client relationship what was pasted and in which account (private or company). Move the next draft to the allow-listed tool, or do it by hand if you do not have one yet. If the content was health data, salary data, or a large customer dossier, get advice from whoever handles data protection for the firm. Do not wait for a workshop invitation to stop the pasting.

Deleting a chat in a personal account is not something this article can promise will remove the data from the vendor. We do not describe that as a fix. The fix you control today is: no further paste, a named owner informed, and a rule for tomorrow.

A rule beats a ban

A blanket ban sounds clean. In practice the chat moves to a private phone. That is shadow AI at work: the same prompt, no contract, no shared rule.

The minimum is dull and often enough. Which tools sit on the allow-list. Which basket may go where. A human checks before anything goes to a customer. One page, signed by the managing office, half an hour with the people who actually draft the mails. Not a 40-page policy.

What to do next

If you want those rules locked with the team in a day: the AI in Business workshop.

If one recurring workflow should come out of the chat and be built, so people are not pasting the Monday file in the first place: the Process Check, half an hour, one case. Workshop and Check are two different purchases. The fork is in workshop or implementation.

Can we paste a customer email into ChatGPT Free?

Treat a customer email as personal data. Free and Plus are the wrong place for it. Use a company plan where you have a contract, keep an allow-list, and have a person read the draft before it is sent. This is a working rule for the office, not legal advice. The FDPIC’s position is that the Data Protection Act still applies and your firm remains responsible.

data protection chatgpt ai sme
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.