Skip to content

Does your website need a cookie banner and a privacy policy?

The rules tightened on 1 January 2025. What an ordinary business website in Norway needs, when you need consent and when the banner only gets in the way.

PrivacyUpdated 6 min read

A person reading through and signing a document at a desk

Two businesses on the same street each make their own mistake.

The bakery has a cookie banner that covers half the screen on a phone. You have to press 'accept' to see the opening hours. Their website sets no cookies at all. The banner is there because they were told that 'everyone has to have one'.

The electrician two doors down has Google Analytics on the site, no banner and no privacy policy, and has never heard a word about it.

Both think they've done it right. One annoys its customers for no reason. The other has a real problem.

What changed on 1 January 2025

Norway got a new Electronic Communications Act (ekomloven). The most important change for anyone running a website: consent to cookies must now meet the requirements for valid consent under the GDPR.

In practice, the old tricks are out. A banner where 'accept all' is a big coloured button and 'reject' is small grey print isn't a free choice. A sentence saying 'by using this website you accept the use of cookies' isn't consent at all.

The Norwegian Data Protection Authority (Datatilsynet) and the Norwegian Communications Authority (Nkom) supervise this together. The first fine under the new law came as early as February 2025, and that spring Datatilsynet published guidance with ten concrete tips. All three are in Norwegian, and the guidance is worth half an hour if you use tracking tools.

The rule is simpler than the banner makes it look

You need consent to store or read information on a visitor's device, with one exception: what is strictly necessary to deliver the service the visitor has asked for.

Strictly necessary is a short list. The basket in an online shop. Logging in. Remembering that someone has already answered the cookie question.

Everything else needs the visitor to say yes first. Analytics tools too, even if all you want to know is how many people visited. Analytics tools above all, because that's where most small websites have their only problem.

Three questions that decide whether you need a banner

Do you use an analytics tool that sets cookies? Google Analytics does. Then you need consent before it loads: not after, and not at the same time.

Do you embed anything from another service? A YouTube video, Google Maps, a booking system, a Facebook feed. Content like that usually sets its own cookies the moment it loads, and that happens in your name, on your site.

Do you have tracking pixels from advertising? The Meta pixel, Google Ads conversion tracking, LinkedIn Insight. Same answer.

If the answer to all three is no, you probably don't need a banner. That's the answer for more businesses than you'd think: a bakery or a hair salon that shows opening hours, prices and a booking form usually has nothing on the site that needs consent.

Then your banner isn't only unnecessary. It's harmful: you're asking customers for something you don't need, and teaching them that your site is an obstacle.

A privacy policy is something else

These two get mixed up all the time. The cookie banner is about what's stored on the visitor's device. The privacy policy is about what you do with information about people, wherever it comes from.

If you have a contact form, you're processing personal data. A name and an email address are personal data. Visitors must then be able to find out who is responsible, what the data is used for, how long it's kept and what rights they have.

That applies even if your website doesn't set a single cookie. So the bakery from the start doesn't need a banner, but it probably does need a privacy policy.

In some trades, the form itself is a reason to read the policy again. A dental clinic or a skin clinic gets health information in the free-text field without asking for it, and that's a special category of personal data with stricter requirements.

Your form is the part people forget

A contact form doesn't feel like data processing. It feels like an email.

But the submissions are stored somewhere, and they stay there for a long time. We've seen inboxes still holding enquiries from 2019, with phone numbers and everything people wrote in the free-text field. Nobody decided they should be kept forever. Nobody decided anything at all, and that's the problem.

Set a deletion deadline, write it in the policy and stick to it. Our own privacy policy follows the same pattern, if you want to see how that looks in practice. We show what the form itself can look like, with an example, in the guide to making a website for your business.

What Sitekit does about this

We automate the technical part. You still decide the purposes and review the text: your business is the data controller, and that can't be handed over to software.

This happens by itself:

  • The privacy policy is generated from what your website does, in every language you have, and updated when you add a form or embed something.
  • The consent banner only appears when the site needs it. If you have no tracking and nothing embedded from a third party, visitors see no banner.
  • Embedded content only loads after consent, and the box says who the content comes from. 'This video loads from YouTube' is informed consent. 'This site uses cookies' isn't.
  • Form submissions are deleted automatically after 90 days.
  • Analytics use neither cookies nor third-party scripts. Unique visitors are counted with a statistical method that stores nothing that identifies the individual: you learn how many, not who.

That last point is why many Sitekit websites need no banner at all. You find out which pages are visited and where the traffic comes from without asking anyone's permission, because you take nothing you'd need permission for.

The cheapest banner is the one you don't need

Start by counting: how many third parties does your website load? For most small businesses, the answer is one or two, and both came in because someone added them without thinking about it.

Remove what you don't use. You're then left with a simpler question, and often with a banner you can delete.

The site gets faster into the bargain. Every third party is another server the browser has to wait for, and that's one of the reasons we go through in why your website is slow.

This isn't legal advice, and if you deal with health information or large amounts of customer data, you should talk to someone who knows the field. But for an ordinary business website with a contact form and a wish to know how many people visited, it's entirely possible to get this right without bothering a single visitor.

See the privacy and SEO features that come included. If you're still at the start with the website itself, what it costs, how a free website can look professional and why nobody finds it on Google are the three questions people ask us most.

Your website is one description away

Write a few sentences about your business, and you have somewhere to start.