3 ms·
As long as they don't have the car keys, they can go knock themselves out. Re: the more substantive legal points - there are off-the-shelf solutions (CMPs, for
by azernik 6y ago
As long as they don't have the car keys, they can go knock themselves out.
Re: the more substantive legal points - there are off-the-shelf solutions (CMPs, for example) and easy checklists for complying in the setting of a static public-facing website. The web designers and brand managers I've worked with are more than capable of meeting clear industry standards.
It's inside a web app, where customer data is on the page and in JS scopes, where the product team is essential in safeguarding customer data.
- cuu508 6y ago> there are off-the-shelf solutions (CMPs, for example) and easy checklists for complying in the setting of a static public-facing website. Consent Management Platforms, things like Cookiebot? In my experience, blocking 3rd-party HTTP requests, cookies, LocalStorage access etc. before consent is given – is easy in simple cases, but can quickly get technical and tricky.
- azernik 6y agoThe public-facing web site for non-users had damned well better be a simple case.
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- g_p 6y ago> there are off-the-shelf solutions (CMPs, for example) and easy checklists for complying in the setting of a static public-facing website. In my experience, the people implementing these often don't understand enough about the technology to be allowed to implement this. I wonder if "easy to use" tag managers are to blame, by allowing non-experts to add JS and other includes to webpages without process or scrutiny. Check a few big brand-name websites, and look at whether they place (third party) cookies before the CMP has even been interacted with. I can think of some major high street labels where the consent prompt is mere theatre.