Nödvändiga cookies

Cookie name Cookie name
Domain Domain
Expire time Expire time
Description Description
Session Session

This cookie is used to prevent the browser from sending this cookie along with cross-site requests.

{product_domain}.{application_name}.application.input {product_domain}.{application_name}.application.input

This cookie is used to send customer input to sub application. Example of cookie: insurance.vehicle.application.input

bolagskod bolagskod

Custom cookie

CallGuide.config_services_9.0.0_J0zKjqJt9 CallGuide.config_services_9.0.0_J0zKjqJt9
Session Session

Cookie used by Telia chat.

TS01780576 TS01780576
Session Session

The BIG-IP ASM system validates these cookies returning from the clients to ensure that the cookies are not modified. WAF/F5.

.EPiForm_BID .EPiForm_BID
90 days 90 days

This cookie is for distinguishing one browser from other browsers that a visitor is using while surfing the internet. If a user visits an Episerver site for the first time, Episerver Forms automatically assigns a random GUID to the visitor's browser. The GUID is stored in a cookie and when it has expired, Episerver Forms creates a new one the next time the user visits the website.

.EPiForm_VisitorIdentifier .EPiForm_VisitorIdentifier
90 days 90 days

This cookie is used to identify who is interacting with the application.

__RequestVerificationToken __RequestVerificationToken
Session Session

This is an anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery. It holds no information about the user and is destroyed on closing the browser.

ASP.NET_SessionId ASP.NET_SessionId
Session Session

ASP. Net_SessionId is a cookie which is used to identify the users session on the server. The session being an area on the server which can be used to store session state in between http requests. 

EPiForm_{FormGUID}_{VisitorIdentifier} EPiForm_{FormGUID}_{VisitorIdentifier}
90 days 90 days

To keep track of which forms a user is interacting with and if they are either completed or uncompleted, Episerver Forms uses a cookie name progressive cookie. The format of the cookie key is 'EPiForm_{FormGUID}_{VisitorIdentifier}'. FormGUID is the primary key of a form instance. Each form instance is given a GUID as unique identifier right after it is created and VisitorIdentifier is the value of the cookie .EPiForm_VisitorIdentifier mentioned above. A sample progressive cookie key is EPiForm_1g9kfad5z-d9bb-964f-a165-7086772895e_0f8fad5b-d9cb-469f-a165-70867728950e:admin

kaka_ok kaka_ok
8 years 8 years

Custom cookie for checking if the user has accepted the cookie banner. (this should be removed after OneTrust)

Funktionella cookies

Cookie name Cookie name
Domain Domain
Expire time Expire time
Description Description
450 days 450 days

Security cookie that protects user data from unauthorized access.

votingcookie.list votingcookie.list

This cookie is used for the voting on FAQs on

6 hours 6 hours

This cookie is used to save the user's preferences and other information. This includes in particular the preferred language, the number of search results to be displayed on the page as well as the decision as to whether the Google SafeSearch filter should be activated or not.

Prestanda- och analyscookies

Cookie name Cookie name
Expire time Expire time
_ga _ga
730 days 730 days

This cookie name is associated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

0 days

Analytical cookie used to distinguish users, set by Google Analytics which we use to collect data about number of visits and user journey. Google Analytics writes various cookies to send data associated with your users. Beginning September 2017, analytics.js started writing the _gac cookie to store campaign information in order to provide Google Ads with a more reliable way to measure the interactions customers have with your business. Analytics writes campaign information to the _gac cookie when a user opens a page on your site via a URL that employs Google Ads auto-tagging.

_gcl_dc _gcl_dc
90 days

This cookie is used by Google Analytics to understand user interaction with the website.

_gid _gid
1 days

This cookie is used to group the user behavior together for each user. Structure of its value is very similar to _ga cookie.

365 days

Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.


This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

90 days