3 ms·
> GDPR compliance can be extremely expensive to implement I always find this argument a bit skewed. Yes, it is expensive if your site has more js than content
by raverbashing 7y ago
> GDPR compliance can be extremely expensive to implement
I always find this argument a bit skewed.
Yes, it is expensive if your site has more js than content and if your business model is to overtrack and overprofile your readers
On the other hand a static page is GDPR compliant. Doesn't seem to be too expensive to implement.
- wetpaws 7y agoTheir site, their rules
- Nextgrid 7y agoBeing in your house and under your rules doesn’t give you the right to break the law.
- kube-system 7y agoA static page is very cheap to implement, if the implementation has no other context. Large organizations have implementation costs and considerations outside of IT, however. I’m sure they could also change their revenue model, but that costs exponentially more than just changing the website to be a static page.
- jimmaswell 7y agoThe GDPR compliance of a static page can be debatable depending on how you interpret it, if Apache is logging accesses.
- raverbashing 7y agoYes but logging is logging To be very honest even if you keep the logs it is extremely unlikely just logging, even with full IPs is a "material" violation of GDPR unless your static page/file is extremely specific (You can also expire or fully anonymize the logs before keeping them)