It may not be a pure nonsense. It might be that according to GDPR the company is eligible for some data use but according to telecommunication law needs still consent to even send this data.
Example: company X analyses their traffic on the backend by aggregating logs per user in a anonymised way because they want to know how many users in a given country uses their product Y. They can do it without any consent as the data is in their system anyway and it is a legitimate interest to know facts about their own product.
Now they want to enrich this by tracking whether the user clicked a homepage banner or a footer link in order to open that product page. This tracking is made on the browser with javascript by sending an AJAX request with a click event. This is still valid for GDPR but not for telecom law that says (German example from TTDSG) you’re not allowed to send anything from a user device unless it’s required for service or you have consent.
Then this kind of consent would make sense.
In the OP example I go with bullshit though. It’s most likely pretending to be compliant while breaking the law.
ICastFist@programming.dev 4 months ago
Does the GDPR have anything on button colors? Because what I see more often is the “accept all” button visually distinct, while the “reject” or “confirm” button being very muted, almost blending with the background
Doxin@pawb.social 4 months ago
Sliiightly more debatable, but you’re not supposed to emphasize one over the other iirc. Go read the GDPR, for legalese it’s surprisingly readable.
Honytawk@lemmy.zip 4 months ago
Yes
Declining needs to be as easy as accepting. So if one button is bigger or is easier to spot (like a different colour or font) then it isn’t compliant with GDPR.