LW IT Solutions
20 articles in this category
Follow this category by RSSPrivacy becomes tangible in small technical details: a script loading, a cookie being set or data sent to a server. Here I explain how to follow those processes and make deliberate choices about them.
The posts cover consent banners, Consent Mode v2, script blocking, server-side processing and data masking. The focus is on implementation: what happens in the browser, what happens on the server, and which setting changes which behaviour?
The ePrivacy Regulation was withdrawn, the Digital Omnibus would move the cookie rules into the GDPR, and the Council has already cut one of its two articles. Exactly one of these three strands binds a website today, and it is the oldest.
A consent banner is a dialogue drawn on top of a page, not a barrier in front of it. Whether anything is actually held back is decided elsewhere – and that decision is visible in the delivered source, before anyone clicks.
Technical tutorial on implementing privacy-compliant synthetic session stitching in WordPress v7.0.2 and Server-Side GTM without persistent cookies or GDPR violations.
Technical tutorial on securing WordPress v7.0.2 installations against unauthorized script injections and tracking pixels by enforcing strict Content Security Policy (CSP) headers.
A June 2026 release note has Floodlight tags in server-side Tag Manager transmitting unconsented requests server to server, joined with browser signals where a GCLID is present. The join is a real improvement; the transmission is the part worth reading twice.
Germany’s consent management regulation has been in force since April 2025 and the first recognised service was registered in October 2025. The mechanism is complete – and integrating it remains voluntary for every website, which is the one edge the whole construction depends on.
The CNIL’s final recommendation of 14 April 2026 puts email tracking pixels under Article 5(3) ePrivacy, and the FAQ of 22 July closes the remaining exemption: collecting the IP address or user agent forfeits it. B2B is included, and the grace period ended on 14 July.
Safari 26’s advanced fingerprinting protection degrades high-entropy interfaces, blocks long-lived script-written storage and hides query parameters and document.referrer – but only for scripts on a list nobody can inspect. That qualifier is the whole mechanism.
An email address in a URL reaches the property before anyone notices, and no report flags it. One Data API query lists every page path, six patterns find the leaks – and the data already stored needs a different remedy from the leak itself.
The Privacy Sandbox status page now carries the same phrase eight times. Sorting the list by what each technology asked of the browser shows where the line actually runs – and it is not between first party and third party.
English
Deutsch
Polski
