Cookies and use of personal data

When you visit dnb.no, cookies are stored on your device. They help us understand how the website is used.

Cookies are small text files that collect data about how you use the website. Some cookies are necessary and are always used to ensure that dnb.no works securely and correctly. If you give your consent, we may also use the data for the purposes described below. This helps us provide you with the best possible experience with DNB.

Change your settings

Necessary functionality

We use cookies for necessary functionality to ensure that the website works securely and as intended. These cannot be switched off.

See cookies and data for this purpose

Customer service and support when you contact us

We use information about how you use our online services to provide better support when you contact us via chat or phone. This helps us connect you with the right adviser or suggest solutions you may be able to handle yourself. By using this information, we make sure you get faster, more personalized assistance whenever you reach out to us.

See cookies and data for this purpose

Tailored content

We use data about how you use the website to provide content, offers and communication that are relevant to you across our own channels. This may include dnb.no, the online bank, the mobile bank app, SMS or newsletters.

When you consent to this purpose, the information is only used exclusively within the DNB Group to tailor content to your needs and interests. We do not share this information with other controllers outside DNB.

See cookies and data for this purpose

Relevant adverts

We share data with selected partners, acting as both processors and controllers, to deliver advertising that is relevant to you outside DNB's channels. This may include creating audience segments based on user behaviour, measuring the impact of marketing, and identifying which channels perform best. This help us ensure that the offers and information you see are more relevant for you.

See cookies and data for this purpose

Improving our products, services and channels

We use insights from the website to identify errors, improve functionality, and develop better solutions. This data helps us analyse how our services perform, understand which features are most useful, and find ways to make our services easier and faster to use.This enables us to make the website and our services more relevant and user-friendly for everyone.

See cookies and data for this purpose

About cookie settings

In the control panel above, you can choose how cookies are used on dnb.no. You can update your preferences at any time.

If you later turn off cookies, we will delete those already stored on your device. Your choices may take up to 24 hours to take effect.

Cookies for necessary functionality must be enabled for the website to work securely. These cannot be turned off.

If it has been more than one year since your last visit to dnb.no, we automatically delete your cookies. You will then need to set your preferences again during your next visit.

Manage cookies in your browser

You can change the settings in your browser to block, allow or delete cookies. If you restrict cookies, you can still use dnb.no, but some functionalities and services may work less effectively or not at all.

If you delete all cookies on your device, you will need to set your preferences again. Your choices apply only to the device and browser you are using and must be adjusted again on other devices.

How you change these settings varies between browsers. You will find guidance on your browser’s help pages.

About our cookies

Here you will find a detailed overview of the cookies we use, the type of data they collect for each purpose, and how long the data is stored. This overview may be updated and changed.

Necessary functionality

For this purpose, we collect information about the device you use, such as browser type, operating system, which pages are visited, and any error messages. Cookies for necessary functionality cannot be turned off.

Vendor	Name	Description	Duration
Adobe	mbox	Present when the Target migration setting is enabled. Allows Adobe Target mbox cookie to be set through the Web SDK.	Session
Adobe	at_check	Temporary value used to verify whether the browser allows cookies to be read and written.	Session
Adobe	com.adobe.reactor. core.maxFrequency. RL542c74cc6981 4459a92ba94178 7bb6cb.day	The value is set by default by Adobe Launch. It is stored locally on the client and is never collected.	Lifetime
Adobe	com.adobe.reactor. core.maxFrequency. RL728039db19604 475bf40a117c8a1c 744.visitor	The value is set by default by Adobe Launch. It is stored locally on the client and is never collected.	Lifetime
Adobe	com.adobe.reactor. core.maxFrequency. RLf2ab1727a5244 181a6695e6f5eda9 ad2.day	The value is set by default by Adobe Launch. It is stored locally on the client and is never collected.	Lifetime
Adobe	com.adobe.reactor. core.visitorTracking. cookiesMigrated	The value is set by default by Adobe Launch. It is stored locally on the client and is never collected.	Lifetime
Adobe	com.adobe.reactor. core.visitorTracking. pagesViewed	The value is set by default by Adobe Launch. It is stored locally on the client and is never collected.	Lifetime
Adobe	com.adobe.reactor. core.visitorTracking. sessionCount	The value is set by default by Adobe Launch. It is stored locally on the client and is never collected.	Lifetime
Adobe / AWS	AWSALB	Used for CMS documents on domaincontent.dnb.no, and to maintain session persistence.	1 week
Adobe / AWS	AWSALBCORS	Used for CMS documents on domaincontent.dnb.no, and to maintain session persistence.	1 week
DNB	consentData	Stores the consent choices given for the device.	1 day or 365 days
DNB	portal_persistent	Stores a device identifier used server-side for various settings.	3 years – can be deleted and then recreated by DNB
DNB	deviceInfo	Used as part of securing the authentication session.	Session
DNB	dnbnorsession	Issued for each session and used to ensure a consistent experience across both open and logged-in sessions.	Session
DNB	env	Used to distinguish between different environments.	Session
DNB	dnbnorlanguage	Stores the language preference for dnb.no to ensure the same language is used throughout the session.	Session
DNB	SRCookie	Used to help secure logged-in sessions.	Session
DNB	portal_scriptable	Holds the context of the current user and helps ensure a consistent experience across both open and logged-in sessions, and supports compliance with anti-money laundering (AML) requirements.	Session
DNB	portal_non_scriptable	Holds the context of the current user and helps ensure a consistent experience across both open and logged-in sessions, and supports compliance with anti-money laundering (AML) requirements.	Session
DNB	srSessionCookie	Used to help secure logged-in sessions.	Session
DNB	SRUserCookie	Used to help secure logged-in sessions.	Session
DNB	fp	Used to ensure a consistent experience across both open and logged-in sessions.	Session
DNB	atc	Used to help secure logged-in sessions.	Session
DNB	sric	Used to help secure logged-in sessions.	Session
DNB	party_id	Used to help secure logged-in sessions.	Session
DNB	com.adobe.dnb.partyId.hash	Stores a hashed version of the customer ID. The value is kept locally only for comparison and is never collected.	Lifetime
DNB	dnb-accordion-r-state-main	Stores the customer’s most recently used logged-in device.	Lifetime
DNB	gj.cache	Used to store information from a mortgage form.	Lifetime
DNB	ndisgsv*	Used to help secure logged-in sessions. * indicates that the name may include a suffix.	Lifetime
DNB	abracadabra	Controls whether an information message about the new corporate online bank is displayed. Used only to show the message on a first-time visit.	Lifetime
DNB	navigation-state-*	Common functionality that web applications can use to temporarily store application state that is needed to restore the correct flow after a user is redirected during an intermediate step, such as BankID authentication. The full name is prefixed with navigation-state-, while the remainder of the name depends on the specific application using the functionality.	Session
DNB / Akamai	lottery	Used for serving CMS-hosted documents from domaincontent.dnb.no.	1 hour
DNB / Nucleus Web Platform	newNettbankUser	DNB is developing a new online bank. This cookie indicates whether the user has visited the new online bank during the session.	Session
Dynatrace	rxVisitor	Contains a visitor identifier used to correlate sessions.	Session
Dynatrace	dtCookie	Tracks a visit across multiple requests.	Session
Dynatrace	dtSa	Serves as temporary storage for actions that span multiple pages. It is used to retain user action names, such as “Click on Login”, across different pages. This is necessary because each page load restarts the JavaScript code, meaning all contextual information must be stored in cookies.	Session
Dynatrace	rxvt	Specifies the session timeout.	Session
Dynatrace	dtPC	Used by Dynatrace to ensure that performance data (beacons) are sent to the correct server and can be linked to the appropriate session. It contains a session ID and technical information that makes it possible to correlate user actions with system performance. It is stored only for the active session and is deleted when the browser is closed.	Session
Dynatrace	ruxitagent_, ruxitagentjs_	Used by Dynatrace to monitor the stability and performance of client services, enabling the detection of technical errors and issues. The * indicates that the name may vary with different suffixes.
Dynatrace	rxvisitid	Backup of a Dynatrace cookie.	Session
IBM WAS ND	*SessionID	Session-tracking cookies used to maintain state across different HTTP requests. * indicates that the cookie name may appear with multiple prefixes, depending on the connection context.	Session
IBM WebSEAL	IV_JCT*	Ensures correct resource resolution for dynamically generated URLs within the IBM Webseal platform. * indicates that the cookie name may include a suffix.	Session
IBM Webseal	PD-S-SESSION-ID	Master Webseal cookie used for session management.	Session
NetScaler	NSC_MC_*_443	Used by Citrix NetScaler to maintain load-balancing persistence, ensuring that a user’s subsequent requests are routed to the same backend server during a session. The * indicates that the name may appear with multiple prefix variations depending on the connection context.	Session

Customer service and support when you contact us

For this purpose, we collect information about your activity on the website. This may include clicks, logins, the device and browser you use, your operating system, time of visit, products you have viewed, how much time you spent on a page, and how you use features such as calculators or application forms.

Vendor	Name	Description	Duration
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_identity	Stores an encoded version of the ECID (Experience Cloud ID). This cookie is set and used by the Adobe Web SDK as a device identification cookie, enabling it to recognise the same user across multiple sessions. It is created when the user visits the page.	365 days
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_cluster	Stores the Edge Network region that serves the current user’s requests. This region is used in the URL path so that the Edge Network can route the request to the appropriate location. If a user connects with a different IP address or in a different session, the request will again be routed to the nearest region.	30 minutes
Adobe	s_ivc	Used by Adobe to store a unique visitor ID and a timestamp. This supports the tracking and analysis of user behaviour on the website, for example by identifying new visitors and understanding how they interact over time.	365 days
Adobe	s_vnc365	The cookie is a first-party cookie used by Adobe to store the visitor’s visit count over a 365-day period. This helps identify visit patterns and understand user behaviour over time, which is valuable for website analytics and optimisation.	365 days
Adobe	com.adobe.dnb.page. previous	Stores the previously visited page.	Session
Adobe	com.adobe.dnb. page.previousTemp	Stores the second previously visited page.	Session
Adobe	com.adobe.dnb. partyId.id	Stores a customer identifier.	Session
Adobe	com.adobe.dnb. partyId.timestamp	Stores the time elapsed since the customer identifier was set.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingPage	Stores the initial page visited.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingTime	Stores the time elapsed since the visit to the landing page.	Session
Adobe	com.adobe.reactor. core.visitorTracking. trafficSource	Stores the source page the user came from before entering the DNB page.	Session
Adobe	persistedprevious Page	Stores the second most recently visited page.	Session
Adobe	previousPage	Stores the previously visited page.	Session
DNB	com.adobe.dnb. ECID.historical	The first ECID assigned to this device.	Lifetime
DNB	com.adobe.dnb. partyId.count	The number of customer IDs associated with this device.	Lifetime

Tailored content

Vendor	Name	Description	Duration
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_identity	Stores an encoded version of the ECID (Experience Cloud ID). This cookie is set and used by the Adobe Web SDK as a device identification cookie, enabling it to recognise the same user across multiple sessions. It is created when the user visits the page.	365 days
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_cluster	Stores the Edge Network region that serves the current user’s requests. This region is used in the URL path so that the Edge Network can route the request to the appropriate location. If a user connects with a different IP address or in a different session, the request will again be routed to the nearest region.	30 minutes
Adobe	s_ivc	Used by Adobe to store a unique visitor ID and a timestamp. This supports the tracking and analysis of user behaviour on the website, for example by identifying new visitors and understanding how they interact over time.	365 days
Adobe	s_vnc365	The cookie is a first-party cookie used by Adobe to store the visitor’s visit count over a 365-day period. This helps identify visit patterns and understand user behaviour over time, which is valuable for website analytics and optimisation.	365 days
Adobe	com.adobe.dnb.page. previous	Stores the previously visited page.	Session
Adobe	com.adobe.dnb. page.previousTemp	Stores the second previously visited page.	Session
Adobe	com.adobe.dnb. partyId.id	Stores a customer identifier.	Session
Adobe	com.adobe.dnb. partyId.timestamp	Stores the time elapsed since the customer identifier was set.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingPage	Stores the initial page visited.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingTime	Stores the time elapsed since the visit to the landing page.	Session
Adobe	com.adobe.reactor. core.visitorTracking. trafficSource	Stores the source page the user came from before entering the DNB page.	Session
Adobe	persistedprevious Page	Stores the second most recently visited page.	Session
Adobe	previousPage	Stores the previously visited page.	Session
DNB	com.adobe.dnb. ECID.historical	The first ECID assigned to this device.	Lifetime
DNB	com.adobe.dnb. partyId.count	The number of customer IDs associated with this device.	Lifetime

Relevant adverts

Vendor	Name	Description	Duration
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_identity	Stores an encoded version of the ECID (Experience Cloud ID). This cookie is set and used by the Adobe Web SDK as a device identification cookie, enabling it to recognise the same user across multiple sessions. It is created when the user visits the page.	365 days
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_cluster	Stores the Edge Network region that serves the current user’s requests. This region is used in the URL path so that the Edge Network can route the request to the appropriate location. If a user connects with a different IP address or in a different session, the request will again be routed to the nearest region.	30 minutes
Adobe	s_ivc	Used by Adobe to store a unique visitor ID and a timestamp. This supports the tracking and analysis of user behaviour on the website, for example by identifying new visitors and understanding how they interact over time.	365 days
Adobe	s_vnc365	The cookie is a first-party cookie used by Adobe to store the visitor’s visit count over a 365-day period. This helps identify visit patterns and understand user behaviour over time, which is valuable for website analytics and optimisation.	365 days
Adobe	com.adobe.dnb.page. previous	Stores the previously visited page.	Session
Adobe	com.adobe.dnb. page.previousTemp	Stores the second previously visited page.	Session
Adobe	com.adobe.dnb. partyId.id	Stores a customer identifier.	Session
Adobe	com.adobe.dnb. partyId.timestamp	Stores the time elapsed since the customer identifier was set.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingPage	Stores the initial page visited.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingTime	Stores the time elapsed since the visit to the landing page.	Session
Adobe	com.adobe.reactor. core.visitorTracking. trafficSource	Stores the source page the user came from before entering the DNB page.	Session
Adobe	persistedprevious Page	Stores the second most recently visited page.	Session
Adobe	previousPage	Stores the previously visited page.	Session
DNB	com.adobe.dnb. ECID.historical	The first ECID assigned to this device.	Lifetime
DNB	com.adobe.dnb. partyId.count	The number of customer IDs associated with this device.	Lifetime

Adform Some of the information collected by this provider is used to personalise advertisements and measure the effectiveness of advertising. Privacy Policy Adform Information about cookies used by Adform
Vendor	Name	Description	Duration
Adform	uid	Assigns a unique ID to the user to track and target advertisements across websites.	60 days
Adform	cid	Helps measure the effectiveness of specific advertising campaigns.	60 days
Adform	tid	Tracks which ads have been shown and whether a conversion has occurred.	60 days
Adform	adtrc	Tests whether the user’s browser supports Adform cookies.	60 days
Adform	C	Used to store information about whether the user has accepted or declined the use of cookies.	60 days
Adform	TPC	Determines whether third-party cookies are allowed in the user’s browser.	60 days
Adform	GCM	Used to match the user’s profile with segments across various advertising platforms.	60 days
Adform	CM14	Identifies the user across different advertising partners for more targeted advertising.	60 days

Google Some of the information collected by this provider is used to personalise advertisements and measure the effectiveness of advertising. Privacy Policy Google Information about cookies used by Google Ads European privacy requirements at Google
Vendor	Name	Description	Duration
Google Ads	NID	Used to personalise search ads and other advertisements by remembering user preferences and displaying more relevant ads.	6 months
Google Ads	GCL_AU	Used to measure ad clicks and conversions. Tracks when a user clicks an ad and later completes an action considered a conversion.	90 days
Google Ads	IDE	Used to deliver targeted ads on third-party websites, as well as to measure ad effectiveness and personalise advertising.	13 months
Google Ads	Test cookie	Checks whether the browser allows cookies.	15 minutes

Microsoft Ads

Some of the information collected by this provider is used to personalise advertisements and measure the effectiveness of advertising.

Information about cookies used by Microsoft Ads

Snapchat

Some of the information collected by this provider is used to personalise advertisements and measure the effectiveness of advertising.

Information about cookies used by Snapchat

TikTok

Some of the information collected by this provider is used to personalise advertisements and measure the effectiveness of advertising.

Information about cookies used by Tiktok

Improving our products, services and channels

Vendor	Name	Description	Duration
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_identity	Stores an encoded version of the ECID (Experience Cloud ID). This cookie is set and used by the Adobe Web SDK as a device identification cookie, enabling it to recognise the same user across multiple sessions. It is created when the user visits the page.	365 days
Adobe	kndctr_2B764D045B DC6C450A495D9 0_AdobeOrg_cluster	Stores the Edge Network region that serves the current user’s requests. This region is used in the URL path so that the Edge Network can route the request to the appropriate location. If a user connects with a different IP address or in a different session, the request will again be routed to the nearest region.	30 minutes
Adobe	s_ivc	Used by Adobe to store a unique visitor ID and a timestamp. This supports the tracking and analysis of user behaviour on the website, for example by identifying new visitors and understanding how they interact over time.	365 days
Adobe	s_vnc365	The cookie is a first-party cookie used by Adobe to store the visitor’s visit count over a 365-day period. This helps identify visit patterns and understand user behaviour over time, which is valuable for website analytics and optimisation.	365 days
Adobe	com.adobe.dnb.page. previous	Stores the previously visited page.	Session
Adobe	com.adobe.dnb. page.previousTemp	Stores the second previously visited page.	Session
Adobe	com.adobe.dnb. partyId.id	Stores a customer identifier.	Session
Adobe	com.adobe.dnb. partyId.timestamp	Stores the time elapsed since the customer identifier was set.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingPage	Stores the initial page visited.	Session
Adobe	com.adobe.reactor. core.visitorTracking. landingTime	Stores the time elapsed since the visit to the landing page.	Session
Adobe	com.adobe.reactor. core.visitorTracking. trafficSource	Stores the source page the user came from before entering the DNB page.	Session
Adobe	persistedprevious Page	Stores the second most recently visited page.	Session
Adobe	previousPage	Stores the previously visited page.	Session
DNB	com.adobe.dnb. ECID.historical	The first ECID assigned to this device.	Lifetime
DNB	com.adobe.dnb. partyId.count	The number of customer IDs associated with this device.	Lifetime

Controller responsibility

DNB Bank ASA is a joint controller for the processing of personal data together with certain other companies in the DNB Group, as several companies use dnb.no as their website. DNB Bank ASA is responsible for safeguarding your rights and is your main point of contact if you have questions about how we process your data.

Questions about your privacy settings?

Do you have questions about cookies, your rights, or how we process personal data?

You can contact our customer service on +47 915 04800 or via chat in the online or mobile bank app. Most issues can be resolved quickly in a single conversation.

If you are not satisfied after speaking with us, you can submit a request via our complaints portal or send a letter to:

DNB Bank ASA
Kort- og bankreklamasjoner (Card and Banking Complaints)
PO Box 4750
7469 Trondheim, Norway.

You can also contact our Data Protection Officer at personvernombudet@dnb.no.

Last updated

This text was last updated on 4 December 2025.