Maximum intelligence. Fully automated. AI systems by core.iq

Systems operational
Insights · Data protection

Data protection in Swiss shops:banners, notices, breach reports.

Many Swiss shops copy the consent window they know from the EU and assume the law is then satisfied. Swiss law asks for something different in most cases: clear information and a real way to refuse, not necessarily a yes before the first click. This article sets out the duties that actually apply, where explicit consent becomes necessary and what belongs in a privacy notice.

As at: October 202611 min read25 sources
Screen showing the open privacy settings of a user account
Photo: Zulfugar Karimov / Unsplash
In short
  • The Swiss Data Protection Act does not make consent the rule for tracking. It requires adequate information, and the Telecommunications Act adds the duty to point out that the processing can be refused.[1, 10]
  • Explicit consent is needed where sensitive personal data are processed or where high risk profiling takes place.[2]
  • Companies with fewer than 250 employees keep no register of processing activities, as long as they do not process sensitive data on a large scale and do not carry out high risk profiling.[8]
  • Access requests must be answered free of charge, as a rule within 30 days.[6]

Which rules apply to a Swiss shop

Two pieces of legislation apply at the same time to a shop based in Switzerland. The Federal Act on Data Protection governs how personal data may be processed. It has been in force since 1 September 2023.[1] Alongside it stands article 45c of the Telecommunications Act. That provision is not about the data but about reaching the visitor’s device: processing data on third party equipment is permitted only for the telecommunications service itself, or where users are informed about the processing and its purpose and are told that they may refuse it.[10]

The Federal Data Protection and Information Commissioner states in his guidance that this provision applies cumulatively with the Data Protection Act. Every processing operation on someone else’s device must therefore either serve the transmission or remain controllable by the user, and the form of the information follows the Data Protection Act.[11]

The key difference from the EU lies in the starting point. Swiss law puts transparency and a right to object first, while Union law as a rule requires prior explicit consent for non essential cookies. The Commissioner says exactly that in his factsheet of 31 March 2026.[12]

None of this is a free pass. Article 6 requires that data be collected only for a specific purpose that is evident to the data subject, and that processing be proportionate. Article 7 obliges the controller to ensure through suitable default settings that processing is limited to the minimum required for the purpose, unless the data subject decides otherwise.[2, 3]

250,000francs maximum fine under arts 60 and 61 FADP
30 daysnormal deadline for access under art. 25 FADP
44states and territories with adequate protection
Important

Under Swiss data protection law the fine falls on the individual, not primarily on the company. Articles 60 and 61 punish private persons on complaint with a fine of up to 250,000 francs, for instance where they wilfully give false or incomplete information or disclose data abroad without meeting the conditions. Only where a fine of at most 50,000 francs is in question, and identifying the responsible individual would be disproportionate, may the business itself be ordered to pay instead.[7]

The Commissioner’s guidance sorts the use of cookies and comparable techniques into tiers. Which tier applies does not depend on the name of the tool but on how intrusive the processing is.[11]

UseExamplesWhat is required
technically necessarybasket, sign in, language choice, captcha, load balancinginformation in the privacy notice. Objection is only possible by not using the application
not necessary, ordinary profilingaudience measurement, advertising, recognition across sessionsinformation plus an opt out that is immediately visible on the first and on every later visit, with privacy friendly defaults
unexpected or highly intrusivesensitive personal data, high risk profilingexplicit consent before processing. The operator cannot then rely on overriding interests

Classification follows the FDPIC guidance, version 1.1 of 6 October 2025, section 3.

For the opt out the guidance names three requirements: it must be prominently placed, it must work with few clicks, and the defaults must be privacy friendly. Overriding private interests are to be assumed only with restraint, and analysis for purely statistical purposes is tied to its own conditions, anonymisation above all.[11]

Where consent is required, article 6 paragraph 6 applies: it is valid only if given voluntarily for one or more specific processing operations and after adequate information. Paragraph 7 requires the explicit form for sensitive personal data and for high risk profiling. High risk profiling exists, on the statutory definition, where data are linked in a way that allows an assessment of essential aspects of a person’s personality.[2]

What follows from this

A window with a large “accept all” button and a pale “show details” link does not meet the requirement of a visible opt out. The Commissioner names misleading design expressly: dark patterns and nudging can render consent invalid. Where access to the site is tied to consent, validity depends on whether going without the site is reasonable, and in a paid variant the price must be proportionate.[11]

With embedded third party services, a video player or a map view for example, those third parties collect data for their own purposes. Operator and third party are then jointly responsible. The operator has to know which services are embedded, has to make sure every duty to inform is met, and has to obtain any consent in a way that names the third parties unambiguously.[11]

What belongs in the privacy notice

Article 19 sets the minimum content. You must state the identity and contact details of the controller, the purpose of processing and, where applicable, the recipients or categories of recipients to whom personal data are disclosed. Where the data are not collected from the data subject, the categories of data processed are added. Where anything goes abroad, the state and the safeguards or the exception must be named as well.[1]

On form the Commissioner recommends a layered structure: the essentials on the first level, detail on further levels. The notice must be easy to find and must not be available only on request. In case of doubt, assume that the data are personal data.[11]

Checklist

Controller with postal address and email. Purposes, separated into order handling, bookkeeping, shipping, advertising and statistics. Recipients or their categories, named where services are embedded. Retention period or the criteria for setting it. States to which data are sent, with the safeguards. Rights of the data subject and the address for access requests. A permanently reachable link to the tracking settings.

The right of access under article 25 asks for more than the notice. On request you must state, among other things, the personal data as such, the purpose, the retention period or the criteria for it, the available information on the origin of the data, and where applicable the existence of an automated individual decision together with the logic behind it. No one can waive this right in advance, the information is free of charge, and it is provided as a rule within 30 days. If you have a processor handle the data, the duty to answer stays with you.[6]

A register of processing activities is required of every controller by article 12 in principle. Article 24 of the Data Protection Ordinance exempts companies that employ fewer than 250 people on 1 January of a given year. The exemption falls away where sensitive personal data are processed on a large scale or where high risk profiling takes place.[4, 8]

Anyone who leaves processing to a service provider needs a contractual or statutory basis under article 9 and must satisfy themselves that the processor is able to guarantee data security. Sub processing is permitted only with prior approval.[5]

Two further duties sit outside data protection law but belong in the same corner of a shop. The Unfair Competition Act requires, in electronic commerce, clear and complete details of identity and contact address including electronic mail, a statement of the technical steps leading to a contract, suitable technical means for spotting and correcting input errors, and immediate electronic confirmation of the order. For email marketing the same article requires prior consent from customers, a correct sender and a straightforward, free way to refuse. Anyone who obtains contact details in the course of a sale, and points out the option to refuse, may send those customers advertising for their own similar goods without consent. Breaches carry, on complaint, a custodial sentence of up to three years or a monetary penalty under article 23.[17]

Sending data abroad: the country list and the USA

Article 16 allows disclosure abroad where the Federal Council has established that the state concerned guarantees adequate protection. Absent such a decision, suitable protection must be provided by an international treaty, by data protection clauses in a contract that were notified to the Commissioner in advance, by standard data protection clauses the Commissioner has approved, issued or recognised, or by binding corporate rules approved in advance.[9]

The country list sits in annex 1 to the Data Protection Ordinance. It currently holds 44 entries, among them the states of the European Economic Area as well as Canada, Israel, New Zealand, Uruguay and the United Kingdom.[13]

The United States are on the list, but with a limit. Adequate protection applies there to personal data processed by organisations certified under the principles of the Swiss-U.S. Data Privacy Framework. The Federal Council recognised that framework on 14 August 2024, and the amendment to the Data Protection Ordinance took effect on 15 September 2024.[13, 15]

Service in the shopWhat to check
Hosting and shop platformserver location, contract under art. 9 FADP, third party access
Payment serviceplace of business, certification, which fields are actually transmitted
Newsletter and transactional mailplace of business, record of consent, unsubscribe path in every message
Analytics and advertisingopt out or consent, place of business, whether profiles build up across sessions

For every entry the state and the safeguard belong in the privacy notice, because article 19 paragraph 4 requires it.

Important

Anyone who wilfully discloses personal data abroad without the conditions of article 16 being met is punished on complaint under article 61 with a fine of up to 250,000 francs. The same applies to handing processing to a processor without the conditions of article 9, and to falling short of the minimum requirements for data security.[7]

When the GDPR applies on top

Under article 3 paragraph 2, the European General Data Protection Regulation also applies to controllers without an establishment in the Union where the processing relates to offering goods or services to data subjects in the Union, irrespective of whether payment is required, or to monitoring their behaviour in the Union.[16]

For a Swiss shop that means this: as soon as you sell into the EU as a matter of plan, ship there, quote prices in euros or follow visitors from the Union with tracking tools, the Regulation sits on top of the Data Protection Act. Article 27 then requires a representative in the Union in writing, except where processing is occasional, does not include large scale processing of special categories of data and is unlikely to result in a risk. The fine ceiling under article 83 paragraph 5 reaches 20 million euros or four per cent of total worldwide annual turnover, whichever is higher.[16]

Switzerland mirrors this. Article 14 requires private controllers domiciled abroad to designate a representative in Switzerland where they process data of people in Switzerland in connection with offering goods and services.[14]

How ordinary cross border trade has become shows in the annual survey by Handelsverband.swiss and NielsenIQ: of 15.8 billion francs of online consumption in 2025, 2.8 billion went to retailers abroad, a rise of eight per cent.[18]

What follows from this

Two legal orders do not mean two banners. The stricter requirement sets the tone, and for non essential tracking that is usually prior consent. If you sell into the EU anyway, an opt in for everything that is not technically necessary is simpler to run than two variants sorted by country of origin.

Data breaches: when you have to report

Article 24 requires a report to the Commissioner as soon as a breach of data security is likely to result in a high risk to the personality or the fundamental rights of the data subject. The report is made as quickly as possible. Swiss law knows no rigid deadline such as the 72 hours of the European Regulation. The processor in turn reports to the controller as quickly as possible. The data subject must be informed where this is necessary for their protection or where the Commissioner requires it.[19]

What the report must contain sits in article 15 of the Data Protection Ordinance: the nature of the breach, as far as possible the time and duration, as far as possible the categories and approximate number of personal data and of people affected, the consequences including any risks, the measures taken or planned, and a contact person with contact details. Missing details are to be supplied as quickly as possible afterwards.[20]

Reports go through the Commissioner’s portal. After sending, a confirmation with the reported details can be downloaded. When a high risk is likely to exist is explained in guidance from the Commissioner dated 23 April 2025.[21, 22]

That the route is used shows in the annual report. In the reporting year 2025/26 the Commissioner received more than 2,000 notifications of possible data protection breaches. From those came 22 preliminary clarifications, nine investigations and 156 interventions with controllers.[23]

What follows from this

You do not need a legal department, but you do need a named person who can assess an incident within hours. That means a list of the systems holding personal data, the contact details of your service providers and a skeleton text for the report. Assembling all of this once the incident has happened costs exactly the time that “as quickly as possible” is about.

How to put this in place

  1. Write down the data flows: which data arise at order, payment, shipping, return, account and newsletter, and where they go. That list is the basis for everything else.
  2. Settle the register question: below 250 employees the register falls away, as long as no sensitive data are processed on a large scale and no high risk profiling takes place. The data flow list shows whether one of the exceptions bites.[8]
  3. Inventory the scripts: every tool that loads in the front end goes on a list and into one of the three tiers. Anything nobody can explain comes out.
  4. Set up the banner: privacy friendly defaults, refuse as reachable as accept, and the choice changeable at any time through a link in the footer.[11]
  5. Write the privacy notice: layered, with the minimum content of article 19 and with the states and safeguards for disclosures abroad.[1]
  6. Bring the contracts up to date: a processing agreement under article 9 for each provider, with sub processing settled.[5]
  7. Rehearse access and reporting: one address for access requests, a process that holds the 30 days, and a reporting route for incidents with a named contact.[6]
  8. Check whether an impact assessment is due: large scale processing of sensitive data or high risk profiling calls for a data protection impact assessment in advance. The Commissioner publishes a factsheet on this.[24, 25]
Where automation helps

The duties that cost time day to day are not the texts but the access requests and the deletion deadlines. One access request touches shop, bookkeeping, shipping and newsletter at once. A process that polls the four systems, puts the hits into one document and logs the dispatch turns the 30 days from a diary problem into a task of minutes. The same holds for deletion deadlines per data type: a rule that flags expired records rather than a reminder in a calendar.

This article is an orientation and not legal or tax advice; for your own shop a professional review of the specific setup is worth the effort.

Frequently asked questions

Does my Swiss online shop need a cookie banner?
A window is not prescribed, the information and the notice about the option to refuse are. Article 45c of the Telecommunications Act requires both for any processing of data on the visitor’s device that does not serve the telecommunications service. In practice a banner is the simplest way to make that visible on the first visit.
Is “accept all” plus a link to settings enough?
No. The Commissioner requires the objection to be prominently placed and to work with few clicks, and the defaults to be privacy friendly. Misleading design can even render consent invalid.
Do I have to keep a register of processing activities?
Companies employing fewer than 250 people on 1 January of a given year are exempt. The exemption falls away where sensitive personal data are processed on a large scale or where high risk profiling takes place.
May I use a newsletter tool based in the USA?
Yes, if the provider is certified under the principles of the Swiss-U.S. Data Privacy Framework. Adequate protection then applies. Otherwise you need one of the safeguards under article 16 paragraph 2, standard data protection clauses recognised by the Commissioner for example.
Does the GDPR apply to my Swiss shop?
It applies on top where you offer goods or services to data subjects in the Union or monitor their behaviour in the Union. Delivery into the EU, prices in euros or EU advertising are clear indications. A representative in the Union must then be designated as well, subject to narrow exceptions.
How quickly must I report a data breach?
As quickly as possible, and only where the breach is likely to result in a high risk to the people affected. The Act names no fixed number of hours. Missing details may be supplied later; the report itself should not wait for them.

Sources

  1. Federal Act on Data Protection, art. 19 FADP, duty to inform on collection of personal data (SR 235.1). fedlex.admin.ch↑
  2. Federal Act on Data Protection, art. 6 paras 6 and 7 FADP, validity and explicit form of consent (SR 235.1). fedlex.admin.ch↑
  3. Federal Act on Data Protection, art. 7 FADP, data protection by design and by default (SR 235.1). fedlex.admin.ch↑
  4. Federal Act on Data Protection, art. 12 FADP, register of processing activities (SR 235.1). fedlex.admin.ch↑
  5. Federal Act on Data Protection, art. 9 FADP, processing by a processor (SR 235.1). fedlex.admin.ch↑
  6. Federal Act on Data Protection, art. 25 FADP, right of access, free of charge and a normal deadline of 30 days (SR 235.1). fedlex.admin.ch↑
  7. Federal Act on Data Protection, arts 60, 61 and 64 FADP, fines of up to 250,000 francs and offences committed in businesses (SR 235.1). fedlex.admin.ch↑
  8. Data Protection Ordinance, art. 24 DPO, exemption from the duty to keep a register of processing activities (SR 235.11). fedlex.admin.ch↑
  9. Federal Act on Data Protection, art. 16 FADP, principles for disclosure abroad (SR 235.1). fedlex.admin.ch↑
  10. Telecommunications Act, art. 45c TCA, data on third party equipment (SR 784.10). fedlex.admin.ch↑
  11. FDPIC, guidance on data processing by means of cookies and similar technologies, version 1.1 of 6 October 2025 (PDF, German). edoeb.admin.ch↑
  12. FDPIC, factsheet on the use of cookies and similar technologies in connection with online tracking, 31 March 2026 (PDF, German). edoeb.admin.ch↑
  13. Data Protection Ordinance, annex 1, list of states and territories with adequate data protection, 44 entries, no. 44 limited to certified organisations (SR 235.11). fedlex.admin.ch↑
  14. Federal Act on Data Protection, art. 14 FADP, representation in Switzerland (SR 235.1). fedlex.admin.ch↑
  15. The Federal Council, press release on the Swiss-US Data Privacy Framework, 14 August 2024, in force on 15 September 2024. admin.ch↑
  16. Regulation (EU) 2016/679, art. 3 territorial scope, art. 27 representatives, art. 83 para. 5 fine ceiling. eur-lex.europa.eu↑
  17. Unfair Competition Act, art. 3 para. 1 let. o and let. s and art. 23 UCA (SR 241). fedlex.admin.ch↑
  18. Handelsverband.swiss and NielsenIQ, annual survey of Swiss online retail 2025, press release of 12 March 2026 (German). handelsverband.swiss↑
  19. Federal Act on Data Protection, art. 24 FADP, notification of breaches of data security (SR 235.1). fedlex.admin.ch↑
  20. Data Protection Ordinance, art. 15 DPO, content of the notification to the FDPIC (SR 235.11). fedlex.admin.ch↑
  21. FDPIC, reporting portal for breaches of data security. edoeb.admin.ch↑
  22. FDPIC, guidance on notifying breaches of data security and informing data subjects under art. 24 FADP, 23 April 2025 (PDF, German). edoeb.admin.ch↑
  23. FDPIC, press release on the annual report 2025/26, 30 June 2026, more than 2,000 notifications, 22 preliminary clarifications, 9 investigations, 156 interventions. edoeb.admin.ch↑
  24. Federal Act on Data Protection, art. 22 FADP, data protection impact assessment (SR 235.1). fedlex.admin.ch↑
  25. FDPIC, factsheet on the data protection impact assessment under arts 22 and 23 FADP, 4 August 2023 (PDF, German). edoeb.admin.ch↑
First contact

One conversation,
then a proposal.

Tell us which data arise in your shop and where they go today. We will show you which steps a system can take over.

✓Assessment of your process
✓Concrete starting points for your business
✓Written support in English
Write to us →