[Enforcement library](/enforcement)

# Coop and Meny apps: a red Accept all button and tracking on legitimate interest drew serious criticism

Denmark's data protection authority, Datatilsynet, closed two inspections of grocery apps. It issued serious criticism of Coop Danmark and Dagrofa (Meny app) for using phone location data in scan-and-pay without a valid legal basis, criticized Coop's cookie consent because a red "Accept all" button next to a white "Accept selected" button nudged users, criticized Dagrofa's single bundled marketing consent that also covered sharing with partners, and issued serious criticism of Dagrofa for collecting in-app activity through cookies and similar tracking technologies on legitimate interest instead of consent. No fine was imposed.

## Key facts

- **Regulator or court:** Datatilsynet (Danish Data Protection Agency)
- **Jurisdiction:** Denmark
- **Framework:** GDPR Articles 4(11) and 6(1)
- **Record date:** 2026-11-02
- **Procedural status:** Decisions issued: serious criticism and criticism; no fine; both companies asked to report on corrective measures

Denmark's data protection authority looked inside two supermarket apps. Coop's consent screen made "Accept all" red and "Accept selected" white, which the regulator called nudging. Meny tracked in-app activity without asking, and bundled several marketing purposes, including sharing with partners, into a single consent.

[Start a free scan](/run-free-codebase-scan)

- **Regulator**: Datatilsynet (Danish Data Protection Agency)
- **Case numbers**: 2025-41-0136 (Coop Danmark A/S); 2025-41-0137 (Dagrofa ApS)
- **Apps**: "Coop. Scan&Betal & gode priser" (Coop app); "Meny Danmark" (Meny app)
- **Law**: GDPR Article 6(1) and Article 4(11)
- **Stage**: Decisions dated 3 August 2026 (Dagrofa) and 2 November 2026 (Coop); press release 10 November 2026
- **Amount**: No fine; serious criticism and criticism
- **Source review**: 11 November 2026

## The problem

In July 2025 Datatilsynet opened inspections of how grocery chains process personal data in their shopping apps, a planned focus area for 2025. It selected Coop Danmark's Coop app and Dagrofa's Meny app ([Coop decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/nov/coop-danmark-as-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps); [Dagrofa decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/aug/dagrofa-aps-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps)).

Both apps used the phone's built-in location data to work out which store a shopper was in for scan-and-pay. Coop also used location to show content and marketing for the nearest store. Dagrofa collected users' in-app interactions through cookies and similar technologies for statistics, improvements, troubleshooting and games, relying on legitimate interest. The consent screens for marketing were also examined.

## What the regulator found

| Company | Finding | Level |
| --- | --- | --- |
| Coop and Dagrofa | Location data for scan-and-pay had no valid legal basis. It was not necessary, because a QR code at the store entrance would do, so consent was required (Article 6(1)) | Serious criticism |
| Coop | Location data used for marketing (whether the user was within 200 meters of a Coop store, later the nearest store) could not rely on legitimate interest; consent was required | Serious criticism |
| Coop | Marketing cookie consent was invalid: "Accept all" was red and "Accept selected" was white, which the regulator found nudged users to accept everything (Articles 6(1)(a) and 4(11)) | Criticism |
| Dagrofa | One combined consent covered several marketing purposes, including disclosure to partners such as social media; users could not choose purposes, and the first layer did not clearly say data went to partners | Criticism |
| Dagrofa | In-app interactions collected with tracking technologies for statistics, improvements, troubleshooting and games could not rely on legitimate interest; consent was required | Serious criticism |

The regulator accepted other processing, such as membership administration, Coop's climate-footprint consent and Dagrofa's analysis. Sources: [Coop decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/nov/coop-danmark-as-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps), sections 1 and 3; [Dagrofa decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/aug/dagrofa-aps-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps), sections 1 and 3.

## Technical issue

- **Consent screen design:** in the Coop app, "Accept all" was highlighted in red and "Accept selected" was white. Coop updated the screen after its first response on 15 August 2025; the decision assesses the version that existed then.
- **Bundled consent:** the Meny app used one checkbox for email and push marketing, and its partner sharing (target audiences plus a first-party ID such as a CDP ID or hashed email sent to ad networks and social media) was only explained through the privacy policy link.
- **Tracking without consent:** the Meny app collected user behavior and app interactions, IP address and device metadata through cookies or similar technologies on legitimate interest.
- **Device location:** both apps read the phone's location to identify the store, although a QR code alternative existed.

**Inth's technical interpretation:** give Accept and Reject or Accept selected the same visual weight, ask for each purpose separately, and say on the first screen when data goes to partners. In-app analytics SDKs that go beyond what the app needs to work should wait for consent, just like web trackers.

Sample:

```ts
// Unequal buttons and analytics on legitimate interest
showBanner({ acceptAll: { color: 'red' }, acceptSelected: { color: 'white' } });
analytics.init(); // runs before any choice

// Equal choices, one purpose at a time, SDK gated on consent
showBanner({ acceptAll: { style: 'primary' }, rejectAll: { style: 'primary' },
  purposes: ['measurement', 'marketing', 'partner-sharing'] });
if (consent.has('measurement')) analytics.init();
```

## Timeline

| Date | Event |
| --- | --- |
| 3 July 2025 | Datatilsynet tells Coop and Dagrofa they have been selected for inspection |
| 14 and 15 August 2025 | First responses from Dagrofa and Coop; Coop later updates its consent screen |
| October 2025 | Meny's scan-and-pay feature is phased out; Coop changes how it uses location for marketing |
| 3 August 2026 | Decision on Dagrofa (Meny app) |
| 5 October 2026 | Deadline for Dagrofa to report on corrective measures |
| 2 November 2026 | Decision on Coop (Coop app) |
| 4 November 2026 | Deadline for Coop to report on corrective measures |
| 10 November 2026 | Datatilsynet publishes a press release on both decisions |

## Outcome

Datatilsynet issued serious criticism and criticism and asked both companies to explain the measures they are taking to bring the processing into line with the rules. According to the press release, both companies accepted the criticism and have started specific measures ([Datatilsynet press release](https://www.datatilsynet.dk/presse-og-nyheder/nyhedsarkiv/2026/nov/alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps)). No fine was imposed.

## What it cost

| Item | Amount | Source |
| --- | --- | --- |
| Fine | None | [Coop decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/nov/coop-danmark-as-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps); [Dagrofa decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/aug/dagrofa-aps-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps) |
| Orders | Report on corrective measures; obtain valid consent for location data, marketing and app-interaction tracking | [Coop decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/nov/coop-danmark-as-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps); [Dagrofa decision](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/aug/dagrofa-aps-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps) |

## Why it matters

- **Color counts.** A regulator found a red "Accept all" next to a white alternative enough to make consent invalid.
- **Apps are not exempt.** In-app analytics and game tracking collected with SDKs needed consent, as with the app tracker in [CNIL v. Fnac](/enforcement/cnil-fnac).
- **One checkbox is not consent to everything.** Bundling marketing purposes and partner sharing into a single consent failed the specificity test.
- **Less intrusive options matter.** Because a QR code could identify the store, using phone location without consent was not necessary.

Related pages: [Unequal choices or identity checks](/enforcement/issues/unequal-choices-or-identity-checks), [Notice, consent scope and assent](/enforcement/issues/notice-consent-scope-and-assent), [Consent before collection](/enforcement/issues/consent-before-collection), [GDPR and ePrivacy cookies](/enforcement/laws/gdpr-and-eprivacy-cookies).

## How Inth catches this

- **Consent banner**: Can show Accept and Reject with equal weight, ask for each purpose separately, name partner sharing on the first layer, and hold analytics and marketing until the matching purpose is accepted.
- **Website audit**: Loads web pages and records which tracking requests fire before a choice and after a refusal, so you can see whether a refusal actually stops them.

### Out of reach

- Inth does not control whether an app reads device location, it does not judge banner design for you, and it cannot decide whether legitimate interest applies to a given processing purpose.

Consent records with the exact wording shown, choice, purpose, country and policy version.

[Start a free scan](/run-free-codebase-scan)

## Checks for your own systems

Your ticks stay on this page. Inth does not save or send them.

### In the repository

- [ ] List every analytics, marketing and game SDK in your app and note the legal basis each one relies on.
- [ ] Confirm SDKs that go beyond core app functions start only after the matching consent.

### In the consent screen

- [ ] Check that Accept all, Reject all or Accept selected have the same size, color and prominence.
- [ ] Make sure each marketing purpose, including sharing with partners, can be chosen separately and is named on the first layer.

### With the people responsible

- [ ] Ask product whether device location is read, and whether a less intrusive option such as a QR code or manual store choice would work.
- [ ] Agree who reviews consent screen design changes before release.

## Sources and limits

- [Datatilsynet press release, 10 November 2026 (Danish)](https://www.datatilsynet.dk/presse-og-nyheder/nyhedsarkiv/2026/nov/alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps) (opened 11 November 2026)
- [Datatilsynet decision on Coop Danmark A/S, 2 November 2026, case 2025-41-0136 (Danish)](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/nov/coop-danmark-as-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps) (opened 11 November 2026)
- [Datatilsynet decision on Dagrofa ApS, 3 August 2026, case 2025-41-0137 (Danish)](https://www.datatilsynet.dk/afgoerelser/afgoerelser/2026/aug/dagrofa-aps-alvorlig-kritik-af-brug-af-lokationsdata-i-indkoebsapps) (opened 11 November 2026)

The decisions are in Danish; quotations and button labels are Inth's translations. Whether the companies sent their reports, and what they said, is not public in these sources.

Source review: 11 November 2026. This page describes the cited record and procedural stage. It does not audit the company's current systems. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.

## Related cases

[Every case in the Enforcement library](/enforcement)