Cookies

Cookies help to make the website work properly and securely. Cookies also enable us to better inform you, e.g. about relevant products and services. Did you know that there are different types of cookies? And do you know what they are used for? Allow us to explain. You can also read more about other technologies, such as Local Storage, on this page.

What are cookies?

Cookies are small text files that our website or the Rabo App stores on your computer, tablet or smartphone. We use them to collect information about your website visit or about the computer, tablet or smartphone that you are using. We also store this information. Thanks to cookies, you don't have to enter the same information every time you visit the website, for example.

Why does Rabobank use cookies?

Some cookies are necessary and are always placed on your device, for example to enable online banking and use of the Rabo App. There are other cookies we use to provide you with the most personalized offer possible. You can always choose whether to consent to this.

We also use cookies to analyze your internet behaviour on our website. If you select ‘Accept’, we can share this information with other companies we work with. We use your personal data to create a profile. This is how we recognize you the next time you visit our website or the Rabo App, It also allows us to make your visit more personal by showing relevant information. If you select 'Accept', we can also make our advertising more relevant and personal outside of our website and the Rabo App. If you click the ‘Accept’ button, you can also, for example, watch videos on our website.

Your privacy is important to us; we will not sell your data.

How do I set my cookies?

You choose your own cookie preference. Basic cookies are required for a properly functioning site. If you accept all cookies, we will provide you with the most complete experience on our website and app.

Want to change your cookie settings? You can do so on this page and via online banking or the Rabo App. If you use multiple browsers, you need to adjust your cookie settings separately for each browser.

What happens to my cookie preference?

We will save your preference for ‘Decline’ or ‘Accept’. Sometimes we will overwrite your cookie preference. That happens if you are a customer and use different devices or browsers in which you make different choices.

To illustrate:

You log in to online banking on your laptop and select the cookie setting ‘Accept’. Next, you log in to the Rabo App on your smartphone and select the cookie setting ‘Decline'. The cookie setting you have last chosen will now be stored in your customer profile and then also be used for your laptop.

Different cookie settings

Rabobank uses two (2) levels of cookie settings: 'Decline' and 'Accept'. 'Decline' is the minimum level and if you select 'Accept', you accept all cookies. You can change your preference whenever you want on this page or via the Rabo App.

Cookie setting 'Decline'

With this cookie setting you accept the placing of necessary and analytical cookies. These cookies are required to use internet banking and the Rabo App securely. We use cookies to measure clicking behaviour anonymously, for example to see how many visitors have used our website or the Rabo App. This setting means that we cannot tailor offerings to your preferences.

RABO_CS
Retention period: 6 months
This cookie keeps track of the number of logged-in customers so we can distinguish between numbers of visitors and customers.

RABO_Analytics
Retention period: 6 months
We use this cookie to analyze processes or sales that start on our website. For example, what percentage of savings account purchases are successful on our website, what percentage still needs an advisor during the purchase, etc.

RABO_visitor
Retention period: 6 months
We use this cookie to keep track of what happens on our website, e.g. through which pages and in what timescale visitors reach their goal. This is required in order to improve the quality of our website. You will thereby remain anonymous.

Rabo_RC
Retention period: 1 day
This cookie ensures that the retention period for your cookie preference is maintained. The retention period is reset with each new visit, so that you do not see the cookie banner unnecessarily often in the Rabo App or on the website.

_ga, _gid,_utm
Retention period: _ga and _utm 1 year, _gid 1 day
These are Google's cookies. They enable us to track visitor statistics and link browsing behaviour on different devices. We also use the _ga cookie to perform analytics on the various websites associated with Rabobank, such as Fundr.nl. We use these analytics to improve our websites.

QPRD of XPRD, en x12, browserInfo of RABOXSRFP
Retention period: until you close the browser or Rabo App.
These cookies are necessary to ensure secure use of online banking and the Rabo App.

RaboTS of TS
Retention period: until you close the browser or Rabo App.
This cookie ensures the technical functioning of certain parts of the website, such as the web forms.

BIGipServer
Retention period: until you close the browser or Rabo App.
We use these cookies to distribute traffic across Rabobank's various computer systems.

RABOBANK_SESSIE
Retention period: until you close the browser or Rabo App.
We use this cookie to link the various requests you make to the website, such as requesting the next page, to one another. Each new visit to the website is given a new and randomly determined number.

ak_bmsc, _abck, bm_mi, bm_sv en bm_sz
Retention period: 1 hour
These cookies are used to load the site as quickly as possible and to recognize bots using Akamai.

RABO_PSL
Retention period: 6 months - reset with each request
We use this cookie to store the choice of which cookie preference you want to apply. This cookie setting is stored at profile level. Resetting the retention period prevents you from seeing the cookie banner very frequently.

krux_session
Retention period: until you close the browser or Rabo App.
We use this cookie to ensure that our partner is aware of your cookie preference. If you no longer choose 'Accept', this cookie ensures that we stop sharing the data.

Utag en utag_main
Retention period: 1 year
This cookie is used by our tag management system Tealium. This enables us to use functionalities from partners, such as visitor statistics from Google Analytics and feedback functionalities. Your web address is automatically made unrecognizable. No traceable personal data is therefore stored.

A cookie checker may also show TIQCDN. That is not a cookie. TIQCDN is Tealium's computer that contacts the tag manager.

NID
Retention period: 6 months
This cookie is used by Google to remember preferences for each page, such as the language or the number of search results per page.

RABOASD
Retention period: 6 months
This cookie remembers whether you use a Random Reader Comfort or Rabo Scanner when you do your banking.

Klantinfo
Retention period: until you close the browser or Rabo App.
If you are a Rabobank customer, this cookie contains your name. Your name will be shown in online banking and the Rabo App.

CHAT_SESSIE
Retention period: until the end of the chat
We use this cookie during your chat session. It will be deleted at the end of the chat.

RABOLANG
Retention period: 5 years
We use this cookie to store your preferred language.

RABOTHM
Retention period: 5 years
We use this cookie to store your preferred theme.

Preferred issuer
Retention period: 1 year
We use this cookie during a ‘betaalverzoek’ to store the bank that you have chosen for paying a ‘betaalverzoek’, so you don't have to look up your bank each time.

PR_PAID
Retention period: 90 days
This cookie keeps track of whether you have already paid a ‘betaalverzoek’. That enables us to help you avoid paying the same ‘betaalverzoek’ more than once.

rfa_login_method
Retention period: 6 months
This cookie is placed when you receive an invitation to log in from your mortgage advisor. We use it to keep track of which login method you used. This enables us to show you the correct login method when you return to the site.

Split.IO
You may come across a reference to 'Split.IO' in various places in the Rabo App. We use it to test optimizations in the app. Split.IO does not affect the banking you are accustomed to doing with the Rabo App.

Piano Analytics
Retention period: 13 months
We use this cookie to analyze customer behavior across the website and app. The tool allows us to gain a good understanding of what our customers are doing within our digital environments.

_pcid, _pctx en pa_user: Contains Piano visitor and context id

pa_privacy, _pprv en _cookie_test: Contains customer's consent

RABOBT

Retention period: 120 days after last Rabo Scanner use
This cookie is used to optimize the Rabo Scanner flow.

Third-party cookies
Sometimes you will see cookies that have nothing to do with Rabobank. For example, Mindspark is a common cookie that you'll see when you use this company's toolbars or extensions. These types of cookies are usually placed because you have downloaded free software. The way to delete these cookies differs for each cookie, as does the cookie’s retention period.

Tip: Use a search engine to find tips on these cookies and how to remove them.

Cookie setting ‘Accept’

With this setting, the website and Rabo App are completely tailored to your personal use and preferences. You thereby give us permission to share your browsing behavior both with us and with our partners. This refers to companies inside and outside Europe with whom we work to build a customer profile about you. We and our partners use this customer profile to show personalized ads. We may also inform you about relevant products and services on Rabobank.nl, in the Rabo App and on other websites.

We place additional cookies. We also use these to exchange information with third parties with whom we work. We use this information to build a profile to tailor the content of websites outside our own website to your situation. Here is a list of cookies by organization.

RABO_UT
Retention period: 6 months
We use this cookie to make a distinction between visitors and customers. If you are a customer and you log in, we use this cookie to show you the correct content, e.g. your own accounts in the Rabo App.

Google DoubleClick
Retention period: no more than 2 years

Test_cookie, _gcl_au, IDE, ID or id. These cookies are used to display personalized Rabobank ads based on previous visits to our website.

Bing Ads
These cookies are used to display personalized Rabobank ads based on previous visits to our website.

_uetvid or MUID: 390 days

_uetsid: 1 day

C cookie: 28 days

uid cookie: 60 days

Facebook
Facebook places various cookies. They are all used to improve Rabobank's advertising offering on Facebook.
Retention periods:

Act, p or presence and the empty facebook cookie (this cookie has no name): until you close the browser or Rabo App.

Csm, c_user, fr, s and xs cookies: 2 months

_fbp or _glc_au cookie: 3 months

datr or lu: 11 months

sb: 2 years

RLCDN
These cookies are used to display personalized Rabobank ads based on previous visits to our website.
Retention periods:

rlas3 cookie: 1 year

pxrc cookie: 2 months

LinkedIn
LinkedIn places various cookies. These cookies help to improve Rabobank's advertising offering on LinkedIn, the lang cookie to use your preferred language, and the bcookie to make it possible to share information from us via LinkedIn.
Retention periods:

lang: until you close the browser or Rabo App.

AnalyticsSyncHistory and UserMatchHistory: 30 days

bcookie, BizoID and BizoUserMatchHistory: 6 months

lidc: 1 day

lissc cookie: 1 year

bscookie: 1 year

li_gc: 2 years

li_sugr: 90 days

li_adsid: 90 days

Twitter
Retention period: 1.5 years
Twitter also places various cookies.

Pid and Guest_id cookies enable the sharing of information from us via Twitter.

Twid, muc, muc_ads and personalization_id are used to improve Rabobank's advertising offering on Twitter.

Snapchat
Snapchat places various cookies. These cookies help to improve Rabobank's advertising offering on Snapchat.
Retention periods:

sc_at: 3 months

scevent.min.js: 3 months

_scid: 13 months

_scid_r: 13 months

X-AB: 1 day

_schn1: 1 day

Salesforce
Retention period: 6 months
_kuid_ or e_cookie is used to create your personal advertising profile for Rabobank. This is done by tracking browsing behaviour on external websites and social media. If you also log in to online banking or the Rabo App, we use that information to recognize you. These cookies enable us to show you relevant (advertising) campaigns.

Pinterest
Retention period: 1 year
_pinterest, _pinterest_ct_ua, _epik, and _pin_unauth. These cookies are all used to improve Rabobank's advertising offering on Pinterest.

Blueconic
We use this cookie to create your personal advertising profile for Rabobank. This is done by tracking browsing behaviour on external websites and social media. If you also log in to online banking or the Rabo App, we use that information to recognize you. These cookies enable us to show you relevant (advertising) campaigns.
Retention periods:

BCSessionID: Contains a unique random ID number for your personal advertising profile.
Retention period: 1 year

BCTempID: Contains a temporary unique random ID number for your personal advertising profile. This ID will be deleted after the BCSessionID cookie has been created.
Retention period: 10 minutes

BCRefusedObjectives: Defines the user's withdrawn consent so that BlueConic no longer collects data.
Retention period: 1 year

AWSALB and AWSALBCORS: used for load balancing Amazon Web Services
Retention period: 7 days

HEM
Retention period: 180 days
If you select the cookie setting ‘Accept’, we will store an encrypted version of your email address in this cookie. By doing so, we personalize your visit to our website and other websites and apps. If you have indicated in Rabo Online Banking that you do not wish to receive personalized offers from us, we will ensure that you do not receive them through third parties either. Examples of third parties are social media, search engines and other web pages.

Before storing your email address, we will convert it into an untraceable code, also known as a 'hash'. This hash is extra secured so that others have no use for it.

Local Storage

We use HTML5 Local Storage to store data. This works much the same as cookies. That's why we’ve included an explanation here.

With Local Storage, you decide how long the browser or your device retains the data. This depends on your browser or device settings and whether and how often you clear the history.

Usbl
We use this data for the feedback forms on our website. This enables us to improve the website based on information that you provide in such a form. We always retain this information.

Kxrabobank_* and _kxrabobank_*
We use this to create advertising profiles. We do this using our partners’ services. In our partner's environment, we use this data to group visitors with a particular profile to make advertising as personalized as possible. We only store this if you have given permission for ‘Accept’.

utm_ and glicd
If you visit the website from an advertisement, we store Google campaign parameters (utm variables and the gclid) under the title campaignParameters. We share the campaign code gclid with GoogleAds in order to be able to bid for ad space more efficiently. We also use this information to measure the success of a campaign so that we can manage the effectiveness of our marketing channels. This specific Local Storage information is deleted from the Storage at the end of a session (when the browser window is closed).

u_sclid
This items stores an unique ID for Snapchat to be able to identify unique visitors.

<meeting_id>_uuid
We use this item to store the customer's unique appointment number in the video call. This unique appointment number helps to store the history of the call and link it to the right customer.

<meeting_id>_ guest_name
We use this item to display your entered visitor name to the other participants during the video call.

<meeting_id>_ videoinput; <meeting_id>_audioinput; <meeting_id>_audiooutput
We use these items to store which camera, microphone and speaker are selected for the input and output of the video call.

<meeting_id>_ device_check_completed; <meeting_id>_ failed_devices; <meeting_id>_ missing_devices
We use this item to see whether or not you successfully passed the last device check and if a device was missing during this last check. If the device check was successful, we will skip the next device check and you will be sent directly to the waiting room or video room.

<meeting_id>_ facing_mode
We use this item to remember which camera is used on a mobile device (the front or back). When the video room reopens, this information will still be available to us.

<meeting_id>_audio_muted; <meeting_id>_ video_muted; <meeting_id>_audio_muted
These items are used to remember and display whether the audio, camera and/or microphone are switched off or not.

<meeting_id>_recording_in_progress
This item is used to see if a call is being recorded or not.

<meeting_id>_ meeting_view
This item is used to save the display of other guests on your screen. It records whether the current view is a grid view or focused view.

<meeting_id>_ meeting_token
This item is used to store the call access code.

<meeting_id>_ remote_joined_once
This item is used to indicate whether a participant already previously entered the call. This prevents multiple repeat notifications from being displayed during the call when a participant re-enters the call.

chat_history_<meeting_id>_<userid>
This item is used to save the chat messages when the video room is reloaded.

<meeting_id>_background_mutation
This item is used to remember whether the blur background feature was on during the call.

<meeting_id>_set_review
This item is used to remember whether the customer successfully completed the reviews. It prevents the customer from seeing the review questions on screen again when reopening the video call.

yt-player-headers-readable
This item is used to determine the optimal video quality based on the visitor's device and network settings.

yt-remote-connected-devices, yt-remote-connected-devices, yt-remote-device-id
These items store the user's video player preferences with embedded Youtube video.

yt.innertube::nextId and yt.innertube::requests
These items store a unique ID to keep statistics of the YouTube videos that the visitor has watched.

experiment-uuid
This item is used to identify users.

lastExternalReferrer, lastExternalReferrerTime
These items are used by Meta to recognize from which website a user originates.