What is a cookie?
Note that if you disable cookies entirely, Hello bank! websites may not function properly.
- Authenticating and identifying you on our websites so we can provide you the services you requested
- Keeping track of information you have provided to us — for example, remembering information you provided whenever you fill in a form
- Remembering your preferences or where you left off in your use of the Hello bank! website
- Measuring your use of Hello bank! websites so that we can improve them, tailor our websites to your likely interests
- Understanding your likely interests so we can provide you more relevant Hello bank! ads and content on non-Hello bank! websites and in non-Hello bank! apps
Cookies on this website
We have divided the cookies into three main categories depending on their purposes:
1. Functional cookies (cannot be adjusted)
These cookies are necessary for the connection with the website to be correct and efficient, and to ensure a safe online environment. Functional cookies collect anonymous data about how the site is used and which pages are important. This is used to improve the general ease of use of the website.
BNP SiteFactory is the platform that delivers content and services to the customers
This cookie stores the basic settings of the user: language, brand, edition (last category visited; e.g. private/retail banking)
Cookie to prevent Cross Site Reference Forgery and to prevent calls made from other origin.
This Cookie is added by sitefactory and used for accessing the website, without this cookie website will not work. This cookie stores no user information. The cookie makes the framework of the site work.
Technical cookie that contains a fixed value and is required by the framework. This cookie stores no user information, it makes the framework of the site work.
The first 2 caracters of the distributorId are the distributionChannelId (49 for Mobile, 52 for Web). The next two characters represent the brand ('FB' for Fortis Bank, 'KN' for Fintro) and the last three characters the application (001 for EasyBanking, 002 for Hello Bank! application). This cookie is the ID of the website and is used to differentiate between the websites of the different brands.
Cookie used to track if the cookie disclaimer message is shown to user or not. If the visitor is a first-time visitor, this cookie makes sure the banner is shown. In the new tool, the lifetime will be 6 months, so after 6 months he will see the info/banner again.
This is a technical session cookie. It is used to divert the website visits to different machines in the back-end. Not all visitors go on the same server. If a server crashes, the visit can be reverted another server. This cookie identifies which user lands on which server. It ensures equal distribution of the visitors to the servers and ensures the stability of the performance.
This cookie is used to differentiate the private banking and wealth customers and to display the private banking content to unauthenticated wealth customers. At this moment the site does not differentiate by default between private and wealth. Once the user logs in, and is wealth a wealth customer, he will see the wealth content. This is for privacy purposes of wealth clients: if someone uses the computer of a wealth client, then he will not see it is a wealth client unless he is logged in. This cookie is placed in context of privacy by design: even if authenticated, the cookie is needed, because front-end wont take the data from back-end.
Cookie used for session management
This is a security cookie set by the Firewall as a unique identifier.
This cookie creates a global session number, so it is a cookie for session management (session ID, random number to session). If someone accesses, this session has a number. This cookie is placed for communication reasons between client - website - server. This is not for logging in.
Cookie to remember the customer preference of segment.
Technical cookie used during the Login process. When a user started logging in, the logid maintains the log-in session, so the site knows that the user has logged in already. As soon as the user logged in, logid will be removed. This cookie is maintained during the phases of the log-in procedure.
This cookie is used to save clients logon profiles, it is only placed when the customer wants to save this profile. Customer profile cannot be derived directly from the cookie, only of the value when being used on the site.
This is a load balancing cookie. BNP Paribas Fortis has mutliple server parcs to garantuee availability of the site, as you can only be logged in one of them at the time we keep a cookie to sent the user to the best suited location.
This cookie enables the user to set his preference for the decimal separator in CSV file exports containing transactions (point or comma)
Until cookies are deleted
Adobe analytics is used to provide (anonymous - when opted out) aggregated statistics on navigation. This allows the bank to monitor performance of the website and improve it accordingly.
Cookie used for gathering statistics (where did a person click, where did he scroll to,…) of the website usage. These statistics are kept anonymous.
Record the portion of a page (0-100%) that the user views and passes the value into a variable on the next page view.
Cookie used for gathering statistics of the website usage. These statistics are kept anonymous
This provides a native method to get accurate and detailed timing statistics for loading events e.g. when page or functionality is loaded.
Custom Adobe Dynamic Tag Manager Cookie.
Cookie used to remember the value of a unique identifier of the transaction taking place when doing an enrolment.
This cookie is used to remember the language in which the content is displayed.
This cookie is used to remember the unique identifier of a "godfather" user in the Hello bank "Member get member" process.
This cookie is used to remember the unique identifier of a "godson" user in the Hello bank "Member get member" process.
This cookie is used to remember the Hello Connect ID of a user when he logs in on one of the Hello Bank platforms.
This cookie is used to remember which of the Hello bank platforms the user has already visited.
This cookie is used to identify a unique visitor, the cookie has the format of s_vi_* depending on the report site used.
The AMCVS cookie serves as a flag indicating that the session has been initialized. Its value is always `1` and discontinues when the session has ended.
The AMCV cookie contains the Experience Cloud visitor ID or MID. The MID is stored in a key-value pair that follows this syntax, mid|Experience Cloud ID.
This cookie is used to identify a unique visitor if the standards_vicookie is unavailable due to third-party cookie restrictions.
2. Comfortcookies (adjustable)
Comfort cookies store your personal preferences. This means that the information you receive and the offers that appear on the Hello bank! websites are relevant and match your areas of interest. They are used to make your web experience as
user-friendly as possible. If you accept these cookies, you will not need to re-enter your user name.
Clicktale is used for analysis regarding the experience on the website. It allows the bank to understand customer behaviour on the website and improve it accordingly.
This cookie is used to anonymously identify a visitor of the Website for the purpose of enabling the ClickTale software to track such visitor’s actions across the client’s website.
This cookie is used to count the number of pageviews or visits of the anonymous visitor for the purpose of enabling the ClickTale software to track the number of pageviews or visits a visitor made on the client’s website.
This cookie contains information to identify the visitor and his action for the ClickTale Experience Cloud.
This cookie is used to indicate whether a user is being recorded and by what reason (Random, Enhanced, Forced, ETR)
Contentsquare CAP is used for analysis regarding the experience on the website. It allows the bank to understand customer behaviour on the website and improve it accordingly. No personal identifiable data is stored in Contentsquare.
Includes the user ID and the latest session number. This cookie enables us to bundle all behavioural data of a visitor during one browser session. The session ID is used within Contentsquare to refer to all that data.
Includes number of pages viewed in the current session. Then, it is followed either by ".1", ".3" (to include a visitor for Session Replay recording service) or ".5" (to include a visitor for Session Replay recording service after a specific trigger).
Includes custom variables used during the visitor’s browser session (in a JSON object)
allows to exclude of a visitor from data collection
allows to record the user consent
allows to record the user’s preference to be excluded from any tracking by the solution.
Adobe Target is a tool used to personalise content seen on the website.
Medallia is a tool for conducting online surveys and collecting user feedback. This feedback enables us to improve the solutions offered by the bank.
Flag that indicate if we retrieve user based targeting data in the current session.
Tracks number of sessions user has been in the browser.
Timestamp indicating when an intercept was last declined / survey was last closed.
Timestamp indicating when a survey was last submitted.
Timestamp indicating when the user has started his session.
Tracks the number of pages the user has been in the session.
Flag indicating whether an intercept was presented in the session.
Timestamp indicating when the page was loaded. Used for time on page targeting.
Number between 0-1 used for percentage of users targeting.
Timestamp for when the last intercept was presented.
UUID for identifying a user.
Loads the specified form id.
Loads and displays the specified form id. Can pass an options object to the form.
Starts a new targeting session. Would probably be implemented in SPAs.
Returns true if there is an open survey (form) or intercept (invite).
Prerequisite - property setting isManuallyInviteTargeting: true. Triggers manual targeting evaluation.
Prerequisite - provision onsiteLogger: true. Start capturing logs for the onsite.
Prerequisite - provision onsiteLogger: true. Stop capturing logs for the onsite.
Dumps all captured logs.
3. Commercial cookies (adjustable)
By accepting commercial cookies, the contents of Hello bank! advertisements are personalised and aligned to your interests. This will happen on other sites and also on your social media. These cookies – placed by Hello bank! and third
parties – are there for commercial and social media purposes.
Third party partner
BNP Paribas Fortis and Hello Bank! use Bluekai to optimize media advertising efficiency & facilitate personalization of the websites and mobile applications. Bluekai is the industry's leading cloud-based big data platform that facilitates companies to personalize online, offline and mobile marketing campaigns with richer and more actionable information about targeted audiences.
Sets the Bluekai Unique User ID. This ID can be used to personalize the user’s experience across the domains of BNP Paribas Fortis. Additionally, data from other organizations associated with this cookie can be used to further optimize the user’s experience.
Placements (tag management)
This cookie is used as a timestamp of last logging event.
This cookie is used for orders management.
SDT ID transfers
This is the main checksum cookie.
This cookie is used to exchange tags.
This cookie remembers which datacenter is used to store the data of the respective user. This way, the closest datacenter can be used, which improves website performance.
If this cookie is set to active, the user is opted in to the Bluekai tool.
If this cookie is set to active, the user is opted out of the Bluekai tool. This cookie overrides BKAllow.
This cookie stores the offline file updates into the profile.
This cookie is the identifier of the JSON tag for Site Side Optimization (SSO).
Google Campaign Manager
Google may contact you with their advertising material. Their advertising content will be tailored to your interests on the basis of your browsing behaviour and the pages you have consulted. The cookies are also used to measure the impact of the bank’s advertising campaigns on this site. The bank doesn’t collect any financial or personal data by means of these cookies. Our third party partner may show you ads if you have visited our website. Those ads will be tailored to your interests, based on what you do online and the sites you visit. To improve our marketing content, this cookie may therefore send data to our third party parner. You can find more information about our third party partners' advertising policy and how to block the collection of your data on their respective pages.
Responsible for the cookies
The website owner, and responsible for treatment of personal data obtained by the cookies, is:
BNP Paribas Fortis SA/NV
Montagne du Parc 3
Your rights as a visitor on our website(s)
You can manage your cookies in the cookie tool. In this tool, you can manage your consent for the different categories.
Additionally, as a visitor and subject of the data retained by these cookies, you have the right to file a complaint with the supervisory authority (www.dataprotectionauthority.be).