Take-Aways (AI)
  • FDPIC publishes updated coo­kie gui­de­lines, ver­si­on 1.1, with Del­ta­view to the ori­gi­nal ver­si­on on Octo­ber 6, 2025.
  • Amend­ment: Pro­por­tio­na­li­ty of non-essen­ti­al coo­kies is rela­ti­vi­zed; the stan­dard is the pro­ce­s­sing pur­po­se set by the controller.
  • Gui­de­lines address loca­ti­on data: high iden­ti­fi­ca­ti­on risk, pos­si­ble pro­fil­ing, DPIA obli­ga­ti­on for sen­si­ti­ve inferences.
  • New: Note on paywalls; FDPIC plans awa­re­ness-rai­sing cam­paign and fur­ther super­vi­so­ry steps.

Today, on Octo­ber 6, 2025, the FDPIC published an updated ver­si­on of his coo­kie gui­de­lines dated Janu­ary 22, 2025 published (in addi­ti­on our con­tri­bu­ti­on at that time). The cur­rent ver­si­on is ver­si­on 1.1. Initi­al ver­si­on can be down­loa­ded here (PDF).

This is an unusu­al approach by the FDPIC, but a wel­co­me one. If gui­de­lines are adapt­ed, this allo­ws the public to make cons­truc­ti­ve comm­ents. Inte­re­sted par­ties can thus put for­ward their posi­ti­ons wit­hout having to go to court, even if – as was pre­vious­ly the case – they do not have the oppor­tu­ni­ty to com­ment on a draft.

The main chan­ge con­cerns pro­por­tio­na­li­ty. The old ver­si­on of the gui­de­lines made a blan­ket state­ment, unneces­sa­ry coo­kies are gene­ral­ly dis­pro­por­tio­na­te. The cur­rent ver­si­on moves away from this par­ti­cu­lar­ly cri­ti­ci­zed position:

  • It still says that unneces­sa­ry coo­kies vio­la­te the prin­ci­ple of proportionality.
  • Howe­ver, refe­rence is now made to the pre­vious defi­ni­ti­on of the neces­sa­ry cookies.
  • The­re, the gui­de­lines now right­ly sta­te that it is is the per­son respon­si­ble for set­ting the pro­ce­s­sing pur­po­seand that the pro­por­tio­na­li­ty of the Mea­su­red against this pur­po­se:

Which coo­kies and simi­lar tech­no­lo­gies are tech­ni­cal­ly neces­sa­ry to ensu­re the func­tion­al fea­si­bi­li­ty of the desi­red pro­ce­s­sing depends on the pur­po­se that the con­trol­ler is pur­suing with a spe­ci­fic data pro­ce­s­sing and can­not be ans­we­red in gene­ral terms.

In other words, the gui­de­lines no lon­ger imply that non-essen­ti­al coo­kies vio­la­te per­so­nal privacy.

The gui­de­lines now also expli­ci­t­ly address Loca­ti­on data (but wit­hout defi­ning them – the indi­ca­ti­on of a coun­try or a city can­not be under­s­tood as a loca­ti­on date):

  • When coll­ec­ting loca­ti­on data that leads to move­ment pro­files, a “high pro­ba­bi­li­ty of iden­ti­fi­ca­ti­on of per­sons” must be assu­med “in practice”.
  • Depen­ding on the dura­ti­on and radi­us, the coll­ec­tion of geo­lo­ca­ti­on data could lead to high-risk pro­fil­ing if this data alo­ne or in com­bi­na­ti­on with other data leads to pre­cise move­ment pro­files that allow con­clu­si­ons to be drawn about key aspects of the user’s per­so­na­li­ty. This is also pos­si­ble by com­bi­ning impre­cise loca­ti­on data.
  • Move­ment pro­files can lead to “sen­si­ti­ve con­clu­si­ons about pri­va­cy” through the eva­lua­ti­on of repea­ted­ly visi­ted loca­ti­ons (e.g. doctor’s and lawyer’s offices). This may requi­re a DPIA.
  • In the case of apps for bil­ling pas­sen­ger trans­por­ta­ti­on, the coll­ec­tion of loca­ti­on data is dis­pro­por­tio­na­te and requi­res consent.

At the end the­re is also a new note on Paywalls.

In the com­mu­ni­ca­ti­on on the update, the FDPIC announ­ced his inten­ti­on to car­ry out an “awa­re­ness-rai­sing cam­paign aimed at a wider audi­ence” and then to initia­te the “neces­sa­ry super­vi­so­ry steps in accordance with the guidelines”.