A common type of cookie notification

Share, analyze, and explore game data with enthusiasts
Post Reply
arzina544
Posts: 31
Joined: Sun Dec 15, 2024 4:34 am

A common type of cookie notification

Post by arzina544 »

Image 2. A common type of cookie notification, which abuses default settings by presenting acceptance of cookies as the only choice. Company name/logo have been removed for privacy reasons.

You can imagine that presenting consent as the default option has far-reaching consequences for the number of visitors who agree to the cookie settings shown. Incidentally, this is of course exactly the reason why it is now necessary for visitors to actively agree to cookies. However, the way in which this 'active consent' is filled in by many companies is not in accordance with the spirit of the GDPR, as can be seen from the following examples.

The 'hidden option'
The majority (80%) of the websites I examined make use of default consent in some way. This often takes the form of a button that allows you to give direct consent for all types of cookies. For example, Figure 2 shows a specific variant of a default, a hidden option , where accepting the cookies is presented as the only choice ( Goldstein et al., 2008 ). This infringes on people's free choice, because it gives the impression that there is no other choice.

Moreover, scientific research shows that the influence of this practice is quite strong. Not showing an opt-out button on the first page leads to 22-23% more consent ( Nouwens et al., 2020 ).

No free choice
More generally, I noticed that refusing permission laos telegram data in the vast majority of cases takes more effort and/or time than accepting cookies. This also makes a choice less 'free'. There are roughly two flavors to distinguish here.

Refusing consent can be done directly in the notification itself, but this is more difficult than accepting the cookies.
Refusal cannot be done in the notification itself, but only by personalizing settings.
Flavor 1
In image 2 you see an example of the first 'flavor':

Image


Refusing consent is less obvious. It is not a button, but a hyperlink in small letters.
Refusing requires more cognitive effort, as you have to actively read and search the fine print.
Refusing requires more physical effort. You have to click precisely on a small piece, instead of a large button.
Clicking on a button is a behavior that we are more used to and that is therefore easier.
All these differences make refusing cookies more difficult to implement than accepting the automatically selected settings ( Fogg, 2009 ).

Flavor 2
In image 3 you see an example of the second 'flavor'.
Post Reply