A prompt requires no authorisation. No ticket, no need to check with IT. All it takes is a browser tab and a few minutes. This is precisely what makes AI so useful in the workplace – and what makes controlling it so challenging. The question, therefore, is no longer whether ChatGPT, Microsoft Copilot, Gemini or Claude are used in day-to-day work. What matters is which data reaches which tool and what happens to it there.
Whether employees are editing a text, summarising a contract or analysing customer data: responsibility for the data processed remains with the company. Nor does the Swiss Data Protection Act distinguish between traditional applications and AI. Anyone processing personal data must, amongst other things, ensure transparency, purpose limitation and proportionality. In the case of high-risk processing operations, a data protection impact assessment may also be required.
Guidance on selecting suitable AI services is provided by the regularly updated overview from the law firm VISCHER and lawyer David Rosenthal. It does not simply consider ChatGPT, Copilot or Gemini as a whole, but distinguishes between specific product and contract variants.
Before authorising the use of an AI service, companies should therefore clarify a number of fundamental questions:
Whether a general marketing text is being corrected or a customer contract is being uploaded makes a crucial difference. The last question in particular is often overlooked: additional services such as web search may entail their own data flows and contractual terms.
Public information has different requirements to internal documents, customer data or trade secrets. An AI service cannot therefore be categorised across the board as either secure or insecure. The decisive factors are what data is processed and under what conditions this takes place.
Even the name of the provider is not sufficient in this regard. ChatGPT Free, Plus, Business, Enterprise and the API, for example, differ in terms of contract, data processing and features. The same applies to offerings from Microsoft, Google or Anthropic.
Companies should therefore not simply ‘release’ ‘ChatGPT’ or ‘Copilot’ but rather a specific product variant with defined contractual terms and settings.
The crucial question is therefore not: Which AI is secure? But rather: Which data may be processed using which specific service?
One aspect is easily overlooked when using AI: web search, or ‘web grounding’.
Many AI assistants can use this to incorporate up-to-date information from the internet into their responses. In doing so, parts of a query may be passed on to a search engine. Depending on the provider, different contractual terms or data locations may apply to this processing step than to the actual AI service.
In the case of Microsoft 365 Copilot, for example, VISCHER points out that when Bing Search is used for this processing step, the Microsoft DPA does not apply.
This becomes particularly relevant if the search query itself already contains confidential information. A customer name, details from a contract or information about an internal project may form part of such a query.
The specific implementation varies depending on the provider and product. MTF therefore recommends not enabling web search and grounding by default in corporate environments. They should be used selectively where they are required for the specific use case and where the associated data flows have been clarified.
In addition to web searches, other factors play a role: data location, the use of input data for training, abuse monitoring, retention periods, zero data retention and contractual assurances.
A simplified comparison based on the MTF analysis highlights some of the differences:
A simplified classification based on an MTF analysis of common AI solutions. Product variants, features and contractual terms vary and are subject to change. The terms and conditions of the specific service used therefore always take precedence.
With various international services, content may be stored for a limited period for the purpose of detecting misuse. Particularly in the case of confidential information and professional and official secrets, it must therefore be assessed whether this processing is compatible with the necessary confidentiality requirements.
In addition to the data location, it is also relevant which sub-processors are involved and which legal jurisdictions the provider and data processing are subject to. For business and enterprise services, a documented risk assessment is therefore required – in addition to the contract and configuration – to determine whether a service is suitable for the intended use case.
The latest VISCHER overview from July 2026 includes Swiss AI providers for the first time. MTF Solutions AG is among them.
VISCHER generally classifies the use of the service for confidential data and personal data as feasible, provided the relevant conditions are met. MTF is also listed as a provider for professional and official secrets, provided the intended contractual addendum is used.
This is not a seal of approval and does not replace an assessment of the specific use case. For businesses, however, this independent classification offers additional guidance when selecting suitable AI solutions.
With MTF Private AI, the focus is not on a single language model, but on the operating model. The AI services run in the MTF Private Cloud, with inference and data processing taking place in Switzerland. Customer data is not used for training the models. In addition, there is zero data retention and the service operates without abuse monitoring.
Particularly where information is subject to professional or official secrecy, stricter requirements apply. This applies, for example, to trustees, law firms, public authorities, healthcare organisations or other public institutions. The location of the data alone is not sufficient in this context. Contractual safeguards are also crucial. To this end, MTF provides a corresponding contractual addendum.
A blanket ban on AI rarely solves the problem. If staff are not provided with suitable tools, there is an increased risk that freely available services outside the company’s guidelines will be used. Effective AI governance therefore begins with a clear answer to the question: Which data may be processed using which services?
A simple classification can already make a big difference:
Specific usage guidelines for staff can be derived from this. Instead of long lists of prohibitions, this provides simple guidance for day-to-day work.
Public and private AI meet different requirements. For many day-to-day tasks, business and enterprise services from the public cloud may be the right choice. The more sensitive the information and the higher the requirements for data sovereignty and confidentiality, the more important data processing, the operating model and contractual safeguards become.
Companies therefore do not need to block as many AI services as possible. Rather, they should know which tools are being used, what data is being processed, and which service has been authorised for which use case.
A prompt will still not require authorisation in future. However, if it is clear which data is permitted to go where, then it will not need any either.
MTF supports Swiss SMEs in integrating AI into their day-to-day operations in a controlled manner. This includes categorising data and use cases, defining clear guidelines for use, and selecting and technically implementing suitable public and private AI solutions.
This creates an AI environment that boosts productivity whilst meeting the company’s requirements for data protection, confidentiality and data sovereignty.