Which cookies need consent in Sweden?
On a booking page, the cookie keeping a chosen time slot and the cookie counting advertising conversions can arrive milliseconds apart. Their purposes determine how you should handle them.
Sources checkedWhich rule applies to a cookie?
Sweden’s Electronic Communications Act, chapter 9, section 28, implements the device-storage rule in Article 5(3) of the ePrivacy Directive. A site generally needs to explain the purpose and obtain consent before storing information on a visitor’s device or reading information already there. The rule can cover local storage and other technologies, including information that is not personal data.
The Act provides exceptions for storage or access needed to transmit a communication, and for what is necessary to provide a service the visitor explicitly requests. If the information is personal data, the GDPR also applies to its processing. A GDPR lawful basis on its own does not grant permission for optional device access.
The GDPR is an EU regulation. The examples here use Sweden’s implementation of the ePrivacy rules and PTS guidance. For sites serving other countries, check the relevant national rules and authority guidance as well.
Classify the purpose of each tool
| On your website | How to assess it |
|---|---|
| Booking session | A short-lived session cookie can qualify for the exception if it is genuinely needed to reserve the slot the visitor requested. Document that dependency and its lifetime. |
| Audience measurement | PTS specifically says that wanting statistics does not make a cookie necessary. Keep analytics that uses device storage inactive until the visitor chooses it. |
| Embedded training video | Check which provider requests the player makes and what it reads or stores. If it uses optional storage, show a local placeholder and explain the choice before loading it. |
For each relevant cookie, describe its purpose, provider, first- or third-party status, lifetime and the information it handles. If your site only uses justified exempt storage, explain that use. A consent prompt serves a purpose when there is an optional choice to make.
Make the first choice usable
In Sweden, PTS expects visitors to be able to accept and refuse at the same point in the same view. Give both buttons comparable prominence. Explain optional purposes in plain language, leave their switches off initially, and provide a way to choose purposes separately.
Until the visitor chooses, keep optional integrations inactive. Continuing to browse or closing a prompt does not give affirmative consent. Provide a recognisable Cookie settings link throughout the site so a returning visitor can withdraw a choice as easily as they gave it.
Check the integration on the page where it runs
Open the booking page directly in a fresh browser profile. Inspect the network and storage before any interaction, then refuse optional services. Repeat with analytics accepted. On a separate run, withdraw it and revisit the page. Include tag managers, booking plug-ins and embeds added through the CMS. One script left in its original template can still run independently of the CMP.