Common mistakes on websites
- Part
- 9 of 10
- Course
- A six-week GDPR curriculum for small companies
Common Mistakes on Websites
Websites are a topic worth expanding on. Time and time again I see websites of small business owners getting things wrong. I don't blame them. A lot of them use drag-and-drop website builders, and those things are great to get a simple website going. But they also make it easy to mess things up in ways that go unnoticed.
Incorrectly Used Cookies
Let's start with cookies, because that's the topic that first comes to mind when you think "website" and "GDPR".
Cookies are text files stored in your browser by the website you're visiting. They can have any kind of data in there, from random tracking identifiers used to record what you're doing online, down to things like your choice of language to read the website in. The ePrivacy Directive (2025) [1] is the thing that made everyone suddenly put cookie banners on their websites a few years ago. It dictates that you need to explain in plain language what cookies you use on your website, what you use them for, and what data they track.
You need to explain all your cookies. But you only need a cookie banner if you have cookies that aren't considered "strictly necessary". Cookies, the GDPR, and the ePrivacy Directive (2025) [2] gives the example of an online shopping cart. It's not possible to implement a shopping cart without cookies and so it's considered strictly necessary. That means if you only use cookies for your shopping cart, you do need to explain them in your privacy policy, but you don't need a cookie banner.
Any cookies outside of "strictly necessary" ones need a cookie banner in addition to an explanation in the privacy policy. This isn't news for you at this point, but again: As with anything GDPR, you want to make sure that your users are well informed, and that it's easy for them to revoke consent again.
Missing Privacy Policy
You need a privacy policy, cookies or not. If you have a website, you're already processing your user's personal data such as IP addresses, what browser they're using, when they're accessing the website, and on what kind of device. You need to explain that in your privacy policy, and that's tough to do without one.
Directly Linked Google Fonts
A thing I see a lot on websites is owners embedding fonts from Google Fonts, but instead of hosting the font files themselves, they just link directly to Google.
If you do that, the browser of every visitor to your website automatically connects to Google's servers to download the font files. And similar to every request coming to your website, every request going to Google's servers includes a lot of personal data. Not only is this completely unnecessary - it's not hard to host font files with your own website the same way you do with pictures, for example - but business owners aren't even aware that they're sending personal data to Google and skip out on getting a DPA or even mentioning any of this in their privacy policy.
Directly Embedded Google Maps
Same thing as with Google Fonts: If you use one of those drag-and-drop website builders, they often provide you with the ability to easily embed Google Maps on their website. Super easy to do, and it looks great!
And if you don't make it so that the user has to opt-in, or don't have a DPA with Google, or don't explain this whole thing in your privacy policy, then it's a violation of the GDPR.
For maps specifically I run my own servers that I then provide to my customers. That way the whole thing is perfectly GDPR compliant without needing any opt-in or extra mentioning in the privacy policy. Why? Well, under the hood Google Maps is just a service that provides images of maps.
The whole globe is turned into "tiles". And when a user wants to see a specific part of the map, the website loads the images of the wanted tiles from the "tile server". It's the same as loading your logo on your website!
But when you're using an external service for this, you're making the user's browser download images from a third party instead of from your own server. And that's the same issue as with Google Fonts. But if you're already running your website with me, adding an embedded map doesn't change anything in terms of personal data processed. You're just adding more pictures to your website, that's all.