Absolutely. It is a disrespectful, shameful lie by the authors of the site.
GA was the only way to get a simple page count view without setting up a database or a backend system before we switched to serverless cloud step function lambda craziness.
Seems like a passion project, and they just wanted to know if their work was used. I give people the benefit of the doubt on all of this when it's a small site.
It would be nice if people read and meant something even if they copied it from somewhere.
Do you want to know how many human years my last company had to devote to regulation? We could have built a hundred startups with all that effort.
I'm not saying GDPR right to be forgotten and data dump/portability isn't important, but it comes with a steep cost that everyone pays everywhere. So much time and money was spent on it. Easily billions of dollars.
And the cookie stuff? How useful has that been?
ePrivacy and GDPR compliance are cheap. Trying to rules-lawyer them to keep illegal business models going, while dodging regulatory scrutiny, is expensive.
Try running a business that has to maintain GDPR compliance and KYC / AML / FINRA compliance. That is not cheap.
Building compliance is not building for your customers direct asks and requirements. Especially software that does not originate in the EU. How many startups are building data export to comply with data export regulations?
I spent nearly a year plumbing through complex microservices to satisfy GDPR at my last company. We collected an enormous amount of PII and KYC data from payments processing, and there were so many downstream services impacted. And I was just one engineer from amongst dozens of impacted teams that had to deal with it.
Regulatory compliance is not free.
Regulatory compliance is frictionful.
I'm not saying regulation is bad, but that it is a cost of doing business and a tax on engineering. Especially for startups looking to go toe to toe with bigger incumbents that have already paid for compliance and that can afford to pay fees to ignore compliance to go fast.
GDPR-compliance in a greenfield project is cheaper than dirt, up until someone makes a GDPR request, at which point it's slightly more expensive than dirt because you had to take 15 minutes out of your day to satisfy the request. By your third or fourth GDPR request, it's perhaps worth taking time to implement an automated flow, but having that many customers is a lovely problem to have!
But my point is orthogonal to liking the regulation.