4 ms·
> One could also argue it's being presented to show the opt out has teeth. (Non-technical people ascribe meaning to fantasy progress meters. A number of UI stud
by Nextgrid 5y ago
> One could also argue it's being presented to show the opt out has teeth. (Non-technical people ascribe meaning to fantasy progress meters. A number of UI studies have shown that.)
In this case, why isn't the same applied to the opt-in?
> If a legacy system were patched for GDPR, it's reasonable for the opt-out to involve more code, not less, as an extra routine undoes the defaults.
The GDPR mandates that no non-essential data processing should happen unless the user opts-in. Even if there was more code involved in making a legacy system GDPR-compliant, said code would need to be ran first (essentially applying the delay to the initial page load). Otherwise, since this consent form is overlaid on top of the existing webpage (as opposed to being on its own page with none of the trackers being loaded) this essentially means that data is being processed until the slow opt-out process completed, thus being in breach of the GDPR. In short, GDPR-compliant systems should work on the basis of "opt-in", not "opt-out". Having the delay on the opt-out proves that the system assumes the user has opted in (and thus immediately processes data that the user may not be willing to share) until told otherwise.
Also, regardless of the delay, the simple fact that the flow has a big prominent "agree and proceed" button which takes one click and then a less prominent "manage settings" which takes multiple clicks is enough for this to be in breach, at least according to the ICO's guidelines.