Cookie Policy

Axepta BNP Paribas (‘we,’ ‘us’) uses cookies and other trackers (hereinafter ‘cookies’) on this website (hereinafter ‘the Website’). The cookies ensure that the Website works properly and facilitate, among other things, the login process. By using cookies, Axepta BNP Paribas can also enhance your online experience. Cookies are also utilized to customize the content and/or advertisements on the Website or other (non-) Axepta BNP Paribas websites according to your personal needs and preferences.

By not accepting cookies, you prevent Axepta BNP Paribas and its partners from optimizing your online experience. Moreover, some parts of the Website may not function ideally. By accepting cookies, you agree that we use cookies as stated in this cookie policy. If you wish, you can always change your cookie preferences in the cookie management tool accessible through the website footer.

All details about the cookies used on this Website can be found in this cookie policy. This policy also explains the purposes for which these cookies are used, who places them, how you can manage or delete them, and what your rights are as a visitor to the Website.

1. What is a cookie?

Cookies are small text, image, or software files that your web browser stores on your device when you use websites and applications. The term ‘device, as used in this cookie policy, refers to computers, smartphones, tablets, and all other devices used for internet browsing.

Cookies can be either: (i) session-specific, meaning they are removed from your device once the browser session is closed; or (ii) permanent, meaning they remain on your device until deleted. Refer to Chapter 3 for more information on session-specific and permanent cookies.

Cookies perform several useful functions, such as:

  • Authenticating and identifying you on our websites and/or applications, so we can provide you with the requested services;
  • Improving the security of the website and/or applications, including preventing fraudulent use of login credentials and protecting user data from unauthorized access;
  • Sending you personalized advertising, particularly based on your browser history and online preferences;
  • Monitoring your use of our websites and/or applications to improve them;
  • Enhancing your user experience by customizing the content of the website and/or applications to match your interests, so that we and our partners (see Chapter 3) can provide you with more relevant advertisements and content from Axepta BNP Paribas on websites and in applications unrelated to Axepta BNP Paribas;
  • Remembering the information you provided to us (e.g., automatically filling in forms with data you previously provided to us for faster login);
  • Tracking your preferences and settings (e.g., language, time zone, etc.) or where you left off in your use of Axepta BNP Paribas websites and/or applications.

2. What information can be stored in a cookie?

The information stored by cookies on your device may include, depending on the retention period:

  • The webpages you visited on that device;
  • The advertisements you clicked on;
  • The browser you are using;
  • Your IP address;
  • And any other information you provided on the visited websites and/or in our applications.

Cookies may contain personal data. When you choose which types of cookies to allow on your device, these cookies can be placed directly by us (first-party cookies) or by one of our partners (third-party cookies).

When we use cookies that collect personal data, this collection and the associated processing activities are covered by our Data Protection Declaration.

If you consent to the installation of third-party cookies on your device, our partners (See Chapter 3) have access to the information they contain (such as your browsing statistics when analyzing third-party cookies) in accordance with our Privacy Statement and that of our partners.

3. What cookies do we use and for what purpose?

We have categorized the cookies on this Website into three main categories based on their purposes:

1. Strictly Necessary Cookies (mandatory)

These cookies cannot be refused if you want to visit the Website. That’s good because they ensure the stability and proper, secure operation of the Website. They are placed only by us and collect anonymous data.

For example, when you visit the website for the first time, you will be prompted to choose your language so that the web pages will automatically open in that language.

Google recaptchaThis cookie is used to distinguish between humans and bots._GRECAPTCHAThis is beneficial for the website, allowing us to generate valid reports on the use of our website.179 days
WebserverRegisters which server cluster serves the visitor.ApplicationGatewayAffinityThis is used in the context of load balancing to optimize the user experience.Session
WebserverDescription: This cookie is used in the context of task assignment.ApplicationGatewayAffinityCORSThis optimized the response rate between the visitor and the site, by distributing the traffic tax across multiple network links or serversSession
SalesforceContent submitted via the contact form is linked to Salesforce through an API connection to ensure synchronization and optimal follow-up.  Persistent

2. Comfort Cookies (with your consent)

Comfort cookies allow us to personalize the Website for you and display targeted information that may be useful to you. These cookies also enable us to understand your behavior on the Website. They are placed only by us and collect your personal preferences.

HotjarTool to track visitor behavior on the website_hjSessionUser_{site_id}  Set when a user first lands on a page. Retains the Hotjar user ID unique to that site. Ensures data from subsequent visits to the same site is attributed to the same user ID. JSON data type.365 days
  _hjidSet when a user first lands on a page. Retains the Hotjar user ID unique to that site. Ensures data from subsequent visits to the same site is attributed to the same user ID. UUID data type.365 days
  _hjFirstSeen  Identifies the first session of a new user. Used by recording filters to identify new user sessions. Boolean true/false data type.Session
  _hjUserAttributesHash  User attributes sent via Hotjar Identity API are cached during the session. Allows us to know when an attribute has changed and needs updating. Hash data type.Session
  _hjCachedUserAttributesStores user attributes sent via Hotjar Identity API when the user is not in the sample. Collected attributes are stored on Hotjar servers only if the user interacts with a Hotjar Feedback tool. JSON data type.Session
  _hjViewportIdStores user viewport data, such as size and dimensions. UUID data type.Session
  _hjSession_{site_id}  Contains current session data. Ensures subsequent requests in the session window are attributed to the same session. JSON data type.30 minutes
  _hjSessionTooLargeEnsures Hotjar stops collecting data if a session becomes too large. Automatically determined by a signal from the WebSocket server if the session size exceeds the limit. Boolean true/false data type.Session
  _hjSessionRejectedIf present, set to ‘1’ for the duration of a user’s session when Hotjar has refused the session connection to our WebSocket due to server overload. Applied in extremely rare situations to prevent serious performance issues. Boolean true/false data type.Session
  _hjSessionResumedSet when a session/recording reconnects to Hotjar servers after a connection interruption. Boolean true/false data type.Session
  _hjLocalStorageTestChecks if the Hotjar Tracking Code can use local storage. If possible, sets a value of 1. Data stored in _hjLocalStorageTest has no expiration time but is almost immediately removed after creation. Boolean true/false data type.Less than 100ms.
  _hjIncludedInPageviewSampleSet to determine if a user is included in the data sample defined by your site’s page view limit. Boolean true/false data type.30 minutes
  _hjIncludedInSessionSampleSet to determine if a user is included in the data sampling defined by your site’s daily session limit. Boolean true/false data type.30 minutes
  _hjAbsoluteSessionInProgressUsed to detect a user’s first page view session. Boolean true/false data type.30 minutes  
  _hjTLDTest  Attempts to store the _hjTLDTest cookie for various URL substring alternatives until it fails. Allows trying to determine the most common cookie path to use, rather than the page hostname. Indicates that cookies may be shared between subdomains (where applicable). After this check, the cookie is deleted. Boolean true/false data type.Session
  _hjRecordingEnabled  Set when a recording starts. Read when the recording module is initialized to see if the user is already recording in a particular session. Boolean true/false data type.Session
  _hjRecordingLastActivitySet in session storage instead of cookies. Updated when a user recording starts and when data is sent via the WebSocket (the user performs an action recorded by Hotjar). Numeric value data type (timestamp).Session
Adobe AnalyticsAdobe Analytics is used to provide global statistics on navigation. If comfort cookies are not accepted, all data is anonymously tracked. This allows the bank to monitor and improve the website’s performance if necessary._sdsat_enrolment_ID      Used to remember the value of a unique identifier for the transaction occurring during enrollment. 
  _sdsat_languageThis cookie is used to remember the language in which the content is displayed.1 year
  _sdsat_zid    Custom Adobe Dynamic Tag Manager cookie. 
  AMCV_F46824205476152E0A4C98A2%40AdobeOrgThe AMCV cookie contains the Experience Cloud visitor ID or MID. The MID is stored in a key-value pair following this syntax: mid | Experience Cloud ID. To learn more about the privacy policy of Adobe Experience Cloud or to opt out, see Adobe Privacy Policy.2 years
  AMCVS_F46824205476152E0A4C98A2%40AdobeOrgThe AMCVS cookie acts as a flag indicating that the session has been initialized. Its value is always ‘1’ and is removed when the session ends.Session
  dpmDPM (Data Provider Match) informs internal Adobe systems that a call from the Adobe Experience Cloud ID Service is requesting a visitor ID. This only happens when the AMCV cookie (containing an Experience Cloud ID) is not set.180 days
  s_ccThis cookie is set and read by the JavaScript code to determine if cookies are enabled (simply set to ‘True’). This cookie is a session cookie that expires when the browser is closed. Without this cookie, we cannot perform performance analysis of the website (what was visited and what was not).Session
  s_ecidThe ECID cookie contains the Experience Cloud ID (ECID) or MID. The MID is stored in a key/value pair with the following syntax: s_ecid=MID|Experience Cloud ID. This cookie is placed by the customer’s domain after the customer sets the AMCV cookie. The cookie aims to allow permanent ID tracking in the first-party status and is used as a reference ID in case the AMCV cookie expires. Refer to AMCV cookie for more information. For details on the privacy policy of Adobe Experience Cloud or to opt out, see Adobe Privacy Policy.2 years
  _fid      This cookie is used to identify a unique visitor if the standard s_vi cookie is not available due to third-party cookie restrictions.2 years
  s_pcCookie used for collecting statistics (where a user clicked, where they scrolled, etc.) about website usage. These statistics remain anonymous.1 year
  s_ppnRecords the portion of a page (0–100%) that the user views and converts this value into a variable on the display of the next page.Session
  s_pprt      Cookie used for collecting statistics about website usage. These statistics remain anonymous.Session
  s_ppvThese cookies are set by the Adobe Analytics plugin “getPercentPageViewed” and are used to measure a visitor’s scrolling activity to see how much they view of a page before moving to another page.Session
  s_ptcThis cookie provides a ‘native’ method to obtain accurate and detailed time statistics for loading events, e.g., when a page or functionality is loaded.Session
  s_sq      This cookie is placed and read by the JavaScript code when the ClickMap and Activity Map features are enabled. It contains information about the previous link clicked by the user. It is used to track visits to websites (how often the website was visited) to create a ‘trail’ of the followed path. We do not know who the visitor is (anonymous cookie), but we know the path of the visit.Session
  s_vi_*This cookie is used to identify a unique visitor, and the cookie has the format of s_vi_ depending on the reporting site used.2 years

3. Marketing Cookies (with your consent)

These cookies ensure that you receive relevant information and personalized offers on social media, our websites, and other websites or applications. These cookies are placed by us, but also by other companies.

For example, if you were searching for new car insurance online on the Website, you may view car insurance offers and other relevant information on social media, our websites and other websites or applications.

FacebookFacebook event tag_fbpUsed by Facebook to deliver a range of advertising products, such as real-time bidding from external advertisers.3 months
Pageviewfr3 months
Google Campaign ManagerGoogle may contact you with their advertising material. Their ad content is tailored to what interests you, based on your browsing behavior and the pages you have consulted. The cookies are also used to measure the impact of advertising campaigns on this website. Axepta BNP Paribas does not collect financial or personal data with these cookies. We can show you ads if you have visited our website. These ads are tailored to what interests you, based on what you do online and the websites you visit. To improve our marketing content, this cookie may send data to our external partner. You can find more information about the advertising policies of our external partners and how to stop collecting your data on their respective pages.Google( days
30 days
Meta (Facebook, Instagram)( days
Bing( months


4. Cookies Responsible

The owner of the website, and the entity responsible for processing your personal data stored in cookies, is:

Axepta BNP Paribas Benelux
Montagne du Parc 3
1000 Brussels

5. How can you manage your cookie choices?

You can manage the way cookies are used on the website by:

  • Managing your cookie preferences in the cookie management tool, accessible at the bottom of the website. In this tool, you can change your preferences at any time, revoke or grant your consent for various editable categories of cookies.
  • Configuring the privacy settings of your browser (see your browser’s help function to learn more about controlling cookies).
  • Checking third-party websites: this allows you to find out how to manage cookie preferences on other websites and applications – see Chapter 3 for more information on third-party cookies.

Please note that your consent is not required for the use of strictly necessary cookies for the proper functioning of the website. Therefore, the option ‘strictly necessary cookies’ is checked, as required in our cookie management tool and is not optional.

By refusing or disabling certain types of cookies or categories of cookies – for example, comfort cookies – we may not be able to optimize your user experience on our websites and/or in our applications.

By default, we retain your cookie choices regarding the device you have used for a maximum of 180 days. If you wish to change your cookie preferences, you can update your choices at any time via  this link. In any case, we ask you to make a choice again every 180 days.

6. Your rights as a visitor to our website

Refer to our Privacy Statement accessible via the footer of the website for more information about Axepta BNP Paribas Benelux as the data controller of personal data and your rights as data subjects.

As a visitor and subject of the data stored by these cookies, you also have the right to file a complaint with the Belgian Data Protection Authority:

Update your cookie preferences: