In this article I share a short and concise step-by-step plan to check and adjust your cookie settings. Because do the technical settings match the message that visitors receive? And how do you adjust these settings, if necessary or desirable? That can be quite difficult in some cases.
In my previous article Stop those dubious cookie notifications I made a plea for user-friendly cookie notifications, where it is just as easy for visitors to refuse cookies as to accept them. This article was written from the visitor's point of view, and thus about how cookie notifications look on the front end.
Consider how your cookie notification should look. Weigh up different interests here.
Can cookies be measured automatically under the law and which ones?
What would you like to measure and which cookies are very important for your company?
Which cookie settings are the most customer-friendly and/or best suited to the interests of your visitors?
It is possible that your optimal cookie notification and cookie settings are different from what you currently use on your website. Read more about the characteristics of a customer-friendly cookie indonesia telegram data notification here . Weigh these interests against each other and think about how you would like your cookie notification to look on the front end. Use the example from my previous article or a (free) tool to easily design and use a notification. There are several tools available to do this, such as Cookiebot .
Step 2: check relevant legislation
If you want to adjust your cookie settings to comply with the law, it is important that you know under which law your website falls. This is a tricky point. For example, you would expect a Dutch website to fall under Dutch law (the GDPR), and an American website under American law, but unfortunately it is not always that simple.
Because it's not just about where your visitors are now, but also about where your visitors come from. Or, in other words, it's about the ' application of the criterion of targeting' . This means that a website falls under the legislation of the visitors it is targeting. An American website that attracts many Dutch visitors falls under the GDPR, despite the fact that the website itself is hosted in America.