A marketing database goes through an approved decision, then disappears, crossed out: the FDPIC is having marketing databases deleted

Published by Thomas dans la catégorie Compliance on 04.11.2026 Last update : 17.11.2026 à 16h18


Table of content

In 2026 the Federal Data Protection and Information Commissioner stopped merely restating the law: it issued decisions ordering companies to stop processing data for advertising and to erase the data concerned. Two cases closed this year show it, and neither of them is about a badly configured cookie banner. What was sanctioned is the failure to honour an objection, to prove a consent, and to answer the authority.

For a Swiss SME or an agency, that changes the nature of the risk. Until now the discussion was about the fine, which remains rare. It is now about an administrative order that can deprive you of your customer file, with a thirty-day deadline and supporting evidence to produce.

The essentials

  • Decision of 17 April 2026 against Cream della Cream Switzerland GmbH and Philipp Plein International AG: advertising sent despite customers' objections, deletions confirmed and then not carried out. The decision has become final.

  • Decision of 26 June 2026 against Add Conti GmbH, published on 22 October 2026: a ban on processing data for advertising purposes, and deletion of all the data within thirty days, with documentary proof.

  • The FDPIC does not impose administrative fines. It orders measures under art. 51 FADP. Fines, up to CHF 250,000, are criminal, target natural persons, and are prosecuted by cantonal authorities.

  • A single report, even an anonymous one, can be enough to open an investigation. The old law's system-error threshold is gone.

  • In both cases the fault is architectural first: the objection and the deletion do not propagate to the end of the tool chain.

What changed in 2026?

The sequence is readable, and it had been announced. In October 2025 the FDPIC published version 1.1 of its guide on data processing through cookies and similar technologies, stating that an awareness campaign would follow, and then supervisory measures in line with the guide. On 31 March 2026 it added a memorandum on the use of cookies and other similar technologies in the context of online tracking. Both documents appear in its public documentation.

Then came the decisions. They are not about cookies, but about what comes next: the advertising use of the contact details collected. That is an important shift for anyone working in marketing, because companies concentrate almost all their attention on the consent banner, while the two cases decided this year are about handling objections and deletion requests.

One significant nuance, and it comes from the FDPIC itself. In its 33rd activity report, covering 1 April 2025 to 31 March 2026, it states that it did not carry out the prescribed periodic controls within the set deadlines, because of its limited resources, and that it cannot call on additional staff until further notice given the strained state of federal finances. It also notes that over the past decade the number of requests filed per year has more than tripled.

This should not be read as good news. An authority that cannot inspect systematically does not inspect at random: it acts on reports. Both 2026 cases started from complaints by individuals, not from a routine audit. Your exposure therefore does not depend on your size or your visibility, but on how many people your marketing annoys enough that they write to Bern.

Cream della Cream and Philipp Plein: advertising sent despite the objection

The two companies, based in Mendrisio, are joint controllers for the data collected on the group's websites. In December 2023 the FDPIC receives a first report: a customer kept receiving advertising after objecting to it. It writes to the companies. No reply.

Between January and October 2024, other customers in several European countries report advertising SMS and emails received after a purchase, despite repeated requests to stop. The unsubscribe links in the emails are ineffective. The SMS messages do not say how to unsubscribe. Some deletion requests go unanswered. Others receive a confirmation of deletion, and the advertising continues. The FDPIC writes a second time in October 2024, again without reply, then opens an investigation in October 2025. The companies take no position and do not contest the facts.

The decision of 17 April 2026 holds, among other things, that sending advertising to identified customers is a processing of data, that processing data against the express will of the person is an infringement of personality under art. 30 para. 2 let. b FADP, and that an objection requires no particular form. The infringement is unlawful unless there is a justification, and it is for the controller to prove that justification. The FDPIC describes confirming a deletion while continuing to send advertising as a manifest breach of the good faith principle under art. 6 para. 2 FADP.

The measures ordered are simple to state and expensive to implement when nobody planned for them: immediately stop any advertising processing where there is an objection, erase data on request, and no longer process the data of people who have already exercised those rights. As the parties did not use their right to take part in the procedure, the decision became final at the end of the thirty-day appeal period. Olivia Breitler published a detailed analysis on swissprivacy.law on 28 October 2026, noting in passing that such facts could also fall under unfair competition law, which the decision does not examine.

Add Conti: a ban on processing, and deletion of the whole database

The second case goes further, because the measure ordered does not target a few contacts but the entire data set.

The FDPIC opens its investigation on 4 June 2025, after more than a dozen complaints from people living in Germany who were receiving advertising from German companies citing Add Conti GmbH as the source of the data. The company claims it collected the data through online prize competitions, which would amount to consent to passing it on to advertisers. The complainants deny having taken part in any such competitions.

The FDPIC finds the explanations not credible, and the detail of its reasoning deserves to be read by anyone running prize competitions as an acquisition channel: the sites relied on were reachable only by typing the address directly, contained almost nothing but legal notices, and had been displaying the same three winners for months. No valid consent was proven. Access, deletion and objection requests went unanswered, and the FDPIC states that the claimed outsourcing of those tasks to providers in Germany does not discharge the company from its responsibility.

In the meantime, in August 2025, the FDPIC had filed a criminal complaint with the public prosecutor of the canton of St. Gallen for breach of the duty to cooperate: a letter delivered, a thirty-day deadline, an extension granted, no reply.

The decision of 26 June 2026, published on 22 October 2026, orders an end to the unlawful processing and disclosure of the data, for the company and for its processors, then deletion of the data within thirty days of the decision taking effect, and confirmation of that deletion to the FDPIC with supporting evidence. The authority even waives ordering the retroactive provision of information, since the data has to be erased in any case. Bankruptcy proceedings were opened against the company with effect from 20 June 2026.

Remember the combination: ban on processing, total deletion, thirty days, and proof to supply. For a company whose model rests on a file, that is a measure close to a shutdown.

What can the FDPIC order, and what do you actually risk?

This is the point boards misunderstand most, because the comparison with the GDPR misleads. The FDPIC cannot impose an administrative fine. What it can do, under art. 51 FADP, is take measures.

  • Modify, suspend or stop all or part of the processing, and erase or destroy the personal data.

  • Suspend or prohibit a disclosure of data abroad that is contrary to art. 16 or 17 FADP.

  • Order compliance with the security requirements of art. 7 and 8, a data protection impact assessment under art. 22, or the provision of information under art. 25.

  • Limit itself to a warning if the controller restores compliance during the investigation. That is one of the few levers you still have once an investigation is open, and it argues for cooperating quickly.

The measures can also cover future processing, which means the order does not expire once the database has been cleaned.

The criminal side is separate, and it targets people, not companies. Breaching the duties to inform, to provide information and to cooperate (art. 60 FADP) and failing to comply with a decision of the FDPIC (art. 63 FADP) are punishable by a fine of up to CHF 250,000, on complaint. Cantonal authorities prosecute and judge (art. 65 FADP), with the FDPIC able to report offences and exercise the rights of a complainant. That is exactly what happened in St. Gallen in the Add Conti case.

The difference with the European regime therefore comes down to three points, and we set out that comparison in our FADP versus GDPR guide for web agencies.

  • Under the GDPR, the authority itself imposes an administrative fine on the company, calculated on its turnover.

  • Under the FADP, the fine is criminal, capped at CHF 250,000, and targets the responsible natural person. It is not imposed by the FDPIC.

  • In exchange, the Swiss administrative measure hits the asset: it stops the processing and can erase the data. For an SME, losing the file usually costs far more than a fine.

The five stages of an FADP procedure in Switzerland, from complaint to a fine of up to CHF 250,000.From complaint to sanctionHow a procedure unfolds in Switzerland1ComplaintCustomer, competitoror former employee2InvestigationThe FDPIC opensan inquiry on its ownor after a report3DecisionThe FDPIC ordersmeasures(no fine)4ProsecutionCantonal criminalauthority5FineUp to CHF 250,000for intentionalviolationsYour best defence: proving what your site does(consent logs, tracker list, up-to-date privacy notice).

How does an FDPIC investigation start?

The FDPIC opens an investigation, on its own initiative or on a report, when there are sufficient indications that a processing operation could breach data protection rules (art. 49 para. 1 FADP). On its own reading of that provision, indications are sufficient when they allow a breach to be presumed with a certain likelihood. A vague hypothesis is not enough.

Three features of the procedure deserve to be known by any management team.

  • A single data subject can be enough. The system-error threshold that existed under the old law is gone: the materiality criterion can be met even where only one person is concerned. The FDPIC may decline to investigate where the breach is minor, but it may be required to act as soon as the breach, by its intensity, risks seriously affecting privacy.

  • Reporting is free, unrestricted and can be anonymous. It can come from the data subject or from a third party. No form is required and the handling is not subject to fees. The reporter has no party status, but if they are personally concerned, the FDPIC must inform them of the follow-up, which in practice rules out anonymous reports.

  • There is almost always an informal phase before the investigation. The FDPIC writes, asks questions, with no decision at the end and no duty to cooperate at that stage. In both 2026 cases, it is precisely the absence of any reply to those letters that led to a formal investigation being opened. An unanswered letter from the FDPIC is the worst available decision, and the cheapest to avoid.

Once the investigation is open, the Federal Act on Administrative Procedure applies and the duty to cooperate arises. If cooperation fails, the FDPIC can order access to information, documents, the register of processing activities and the personal data, access to premises, the hearing of witnesses and expert reports (art. 50 FADP). For enforcement it can call on cantonal and communal police bodies. Professional secrecy is expressly reserved, but official secrecy cannot be invoked against it. Only the party under investigation has party status, and it must be heard before the decision is issued. The opening of an investigation cannot be appealed; the Federal Administrative Court is the competent appeal body.

On what the authority actually asks for when it writes to you, we set out the list in our article on the five documents the FDPIC may request during an inspection.

Why these two cases are data chain failures first

Here is our reading, and it is technical rather than legal. Read the facts held against Cream della Cream again: ineffective unsubscribe links, SMS that do not say how to unsubscribe, a deletion confirmed in one system while another keeps sending. These are not legal subtleties. They are integration defects.

In a normally equipped SME, an objection has to travel through six or seven systems. It almost always stops in the same places. Here are the breaks we meet most often in audits.

An objection travels through the consent banner, the CRM and the emailing tool, then stops before the SMS tool and the already uploaded advertising audience.Where an objection stopsThe same refusal, followed tool by toolConsentrefusal recordedCRMstatus updatedEmailingcontact removedSMSseparate listAds audiencealready uploadedAdvertising resumes through the first tool the objection never reaches.
  • The consent platform records the refusal, but the CRM never learns about it: nothing connects the two.

  • The emailing tool processes the unsubscribe, but the transactional tool and the SMS tool each have their own list, fed by an earlier export.

  • The contact is erased from the CRM, but survives in a customer list targeting audience already uploaded to an advertising platform, where it stays activatable for months.

  • The contact disappears from the live database, but remains in exports, data warehouse tables and the backups used to rebuild audiences.

  • A provider handles the requests, and nobody checks that it did. The FDPIC settled this point in the Add Conti case: outsourcing does not discharge the controller.

The fourth and fifth cases are the most dangerous, because the company is acting in good faith. It did delete the contact, it confirmed it in writing, and the advertising starts again at the next synchronisation. That is exactly the configuration the FDPIC described as a manifest breach of the good faith principle. Intention offers no protection: what is judged is the result observable by the person concerned.

The same reasoning applies to offline conversion imports to advertising platforms, which we describe in our article on offline conversions between CRM and Google Ads: an export that does not re-read the consent state on every run sends back out, every month, the contacts you removed. And if a leak occurs in that chain, the notification deadlines are a subject of their own, which we cover in our article on a data leak through your marketing tools.

This is the question that brought Add Conti down, and the one almost no SME can handle. Art. 31 FADP provides that an infringement of personality is unlawful unless justified, in particular by the person's consent. But the burden of proving that justification lies with the controller. Claiming that the data comes from a prize competition is not enough: you have to be able to demonstrate it, contact by contact.

A consent log that is still usable two years later carries at least the following.

  1. The date and time of collection, with the time zone.

  2. The exact wording shown to the person, not a reference to a template that has changed since.

  3. The channel and the location: which form, which page, which app, which point of sale.

  4. The scope: which purposes and which channels were accepted, separately.

  5. The version of the banner or form, so the record can be tied to the text actually shown.

  6. Later events: objection, deletion request, reactivation, each with its date.

One technical consequence follows directly. A consent platform that keeps the state only in the visitor's browser gives you nothing to produce before an authority. Browsers forget, users change device, site data is cleared. The proof is built server-side, in a log you control, and that is one reason why server-side architecture is not only an advertising performance topic. The mechanics of the consent signal and its transmission are detailed in our guide to Google Consent Mode v2.

A final remark on cookies, since the FDPIC's guide returns to them. The document holds that consent may be required where a site operator embeds third-party cookies that give third parties paid access to visitor information, and that those third parties, present across several sites, may build high-risk profiling, meaning a particularly serious infringement of personality. It also deals with location data, often amounting to high-risk profiling, and with paid consent walls.

Which checks should you run this month?

Eight verifications, all feasible in-house, ranked by the ratio of risk removed to effort.

  1. Take five contacts who unsubscribed more than three months ago and check, tool by tool, that none of them can still be reached. This test reproduces exactly the facts of the Philipp Plein case.

  2. Click your own unsubscribe link, in every language and every template, and check that it writes to the system of record and not only to the sending tool.

  3. Check that your SMS and instant messaging sends state clearly how to unsubscribe, and that the refusal actually works.

  4. Pick three addresses in your database and try to produce the date, the wording and the channel of their consent. If you cannot, you have found your priority project.

  5. List the audiences uploaded to your advertising platforms and check when they were last refreshed from a database purged of objections.

  6. Name who handles access and deletion requests, and what evidence of handling you keep, including for your providers.

  7. Test the path of the post. Who opens mail addressed to the company, and how long does a request take to reach the right person? Both 2026 cases started with unanswered letters.

  8. Reread your register of processing activities and your privacy policy and check that they actually describe the advertising use you make of the data, recipients included.

How A-Track can help

Our tracking and compliance audit establishes what your tools really send and where an objection gets lost in your chain, including integrations set up by former providers and never documented. Our tracking and compliance offer covers designing the full chain, from consent collection to the export filter on the CRM side, with the evidence log that goes with it. Our annual maintenance provides the periodic checking of those paths, because an objection that propagated correctly last year stops doing so as soon as a tool is added.

We work from Geneva, with Swiss SMEs and with web and marketing agencies for whom we take on the measurement and compliance side at their own clients.

Conclusion: where to start

The two 2026 decisions create no new obligation. Objection, deletion and proof of consent were already in the law. What changes is that the FDPIC now enforces them by decision, with short deadlines and evidence to produce, and that a single report is enough to set the machine in motion.

The first step takes half a day. Take five people who asked you to stop, and follow them through every one of your tools, one by one, all the way to the audiences uploaded to your advertising platforms. If one of them is still reachable somewhere, you have just reproduced, in your own company, the facts that earned two companies a decision this year. And you know where to start.

Related services

Tracking & Compliance

Server-side tracking and FADP / GDPR compliance: around 40% more data recovered on average (measured across 100+ installations), from CHF 1,200.

Tracking & Compliance Audits

Tracking audit, FADP and GDPR compliance audit, data governance audit. Custom quote.

Annual Maintenance

Your tracking monitored and your compliance kept up to date, from CHF 900 a year.

Questions fréquemment posées

Can the FDPIC order my marketing database to be deleted?

▾
Yes. Art. 51 FADP allows it to modify, suspend or stop all or part of a processing operation, and to order the erasure or destruction of personal data.

That is exactly what it did on 26 June 2026 in the Add Conti GmbH case: a ban on processing data for advertising purposes, deletion of all the data within thirty days of the decision taking effect, and confirmation of that deletion to the FDPIC with supporting evidence.

The order can also cover future processing, and it extends to processors. If the controller restores compliance during the investigation, the FDPIC may instead limit itself to a warning.

Is a single complaint enough to trigger an FDPIC investigation?

▾
It can be. The FDPIC opens an investigation, on its own initiative or on a report, where there are sufficient indications that a processing operation could breach data protection rules (art. 49 para. 1 FADP). Indications are sufficient when they make the breach plausible, not merely possible.

The system-error threshold that existed under the old law is gone: a breach affecting a single person can be examined. The FDPIC may decline where the breach is minor, but it must act as soon as the breach risks seriously affecting privacy.

Reporting is free, requires no particular form, can be anonymous, and can come from a third party: a media outlet, a consumer association, a lawyer.

How do I prove consent for a contact in my marketing list?

▾
The burden of proof is on you. Art. 31 FADP provides that an infringement of personality is unlawful unless justified, in particular by consent, and it is for the controller to demonstrate that justification.

A consent log still usable two years later carries at least: the date and time of collection, the exact wording shown to the person, the channel and location (form, page, app, point of sale), the scope accepted purpose by purpose, the version of the banner or form, and any later events with their dates.

The decisive technical point: a consent platform that keeps the state only in the browser gives you nothing to produce before an authority. The proof is built server-side.

What happens if you ignore a letter from the FDPIC?

▾
Before a formal investigation there is no duty to cooperate yet: the FDPIC writes and asks questions, with no decision at the end. But not replying is precisely what leads to a formal investigation being opened. That is what happened in both 2026 cases.

Once the investigation is open, the duty to cooperate applies. The FDPIC can then order access to information, documents and the register of processing activities, access to premises, the hearing of witnesses and expert reports (art. 50 FADP), and call on cantonal police for enforcement.

Intentionally refusing to cooperate is punishable by a fine of up to CHF 250,000. In August 2025 the FDPIC filed a criminal complaint in St. Gallen against Add Conti GmbH on that ground.

Must an unsubscribe propagate to Google Ads and Meta?

▾
Yes, and this is the most frequent break we meet in audits. A contact erased from the CRM often survives in a customer list targeting audience already uploaded to an advertising platform, where it stays activatable for months.

Two other paths ignore it too: exports, data warehouse tables and the backups used to rebuild audiences, and transactional or SMS tools that keep their own list from an earlier export.

In its decision of 17 April 2026, the FDPIC described confirming a deletion while continuing to send advertising as a manifest breach of the good faith principle. Good intentions offer no protection: what is judged is the result observable by the person.

What documents does the FDPIC request during an FADP audit?

▾
The FDPIC has no fixed list, but during an investigation (Art. 49 and 50 FADP), five documents often come up:

1) The record of processing activities (Art. 12 FADP), from which companies with fewer than 250 employees are partly exempt.
2) Proof of consent choices, where you rely on consent (EU visitors, Google's policy).
3) The safeguards for data transfers outside Switzerland (Art. 16 FADP, for example the Swiss-U.S. DPF or standard clauses) and, if the processing is high-risk, an impact assessment (Art. 22 FADP).
4) Technical proof that non-essential trackers respect the visitor's choice (data protection by design and by default, Art. 7 FADP).
5) The processing agreements with your service providers (Art. 9 FADP).

Who pays the FADP fine in case of non-compliance: the company or the director?

▾
The FADP targets the natural person responsible for an intentional violation (for example the person who took the decision within the company), not automatically the director. The fine can reach CHF 250,000 and is imposed by cantonal criminal authorities; the FDPIC itself does not impose fines.

Where identifying the responsible person would require disproportionate investigation, the company can be fined up to CHF 50,000 (Art. 64 FADP). The European GDPR, by contrast, penalises the company.

What are the financial risks in case of non-compliance with the FADP?

▾
The GDPR provides for fines against companies of up to EUR 20 million or 4% of worldwide annual turnover (Art. 83 GDPR). The FADP works differently: it provides for criminal fines of up to CHF 250,000 against the responsible individuals, for intentional breaches of certain duties (information, cooperation, due diligence, professional secrecy, Art. 60 to 63 FADP).

These fines are imposed by cantonal criminal authorities; the FDPIC investigates and orders measures but does not impose fines. Indirect costs come on top: rushed remediation, reputational damage, limited advertising features.

What is the major difference between the FADP (Switzerland) and the GDPR (EU) for a website?

▾
Although very similar, the FADP (Federal Act on Data Protection) favors a risk-based and transparency approach, while the GDPR imposes a stricter framework on prior consent. However, if you are targeting European customers, you must comply with the GDPR, which is the highest standard.