Terms and conditions Cookies Policy Card supplement to the terms and conditions Website Terms Privacy notice Complaints Policy Anti-Bribery and Corruption Policy Safeguarding Risk appetite statement ESG Policy

Cookie Policy

October 2026

PURPOSE

This Cookie Policy describes how Bilderlings Pay Limited (“we” or “us” or “our” or “Bilder”) uses cookies and similar technologies on www.bilderlings.com (the website) and portal.bilderlings.com/account.bilderlings.com (the portal) when the user (you) visits the website or the portal (when signing up and using internet banking).

1. WHAT ARE COOKIES AND SIMILAR TECHNOLOGIES?

Cookies are small text files (typically made of letters and numbers) that are downloaded to your browser or your device by websites that you visit. They act as a kind of “memory” of your interactions with websites and related services, allowing those service providers to recognize you and respond appropriately.

Cookies and similar technologies can be classified as:

First-party cookies are set by or on behalf of the website you are visiting and associated with that website’s domain; or
Third-party cookies are set by a domain other than the website you are visiting, for example by certain analytics, advertising, or other third-party services.

You can find more detailed information about the specific cookies and similar technologies we use, their purposes, and how long they are stored in Appendix A at the end of this Policy.

2. WHAT COOKIES ARE USED AND WHAT ARE THEIR PURPOSES?

Cookies are designed to make the interaction between users and websites easy, convenient and fast. Websites use cookies predominantly in order to save time and make the browsing experience of a user more efficient. Where required by applicable law, we will obtain your consent before using cookies or similar technologies. Certain technologies may be used without consent where an exception under applicable law applies, including where they are strictly necessary to provide a service requested by you. You can later adjust your cookie preferences at any time via our Cookies Settings page.

Bilder uses the following categories of cookies:

Strictly necessary cookies - these are the cookies that are required for the necessary operation of our services and are always on. They include, for example, cookies that enable you to log into secure areas of our website and/or the portal.

Analytical cookies - used to recognise and count the number of visitors and to see how visitors move around our website and/or the portal when they are using it. This helps us to improve the way our website and/or the portal works, for instance, by ensuring that users are finding what they are looking for easily.

Marketing cookies - these cookies record your visit to our website and/or the portal, the pages you have visited and the links you have followed. We will use this information to make our website relevant to your interests. We may also share this information with third parties for this purpose.

Cookies can also be categorized by their duration of storage:

Session cookies - temporary cookies that are stored in your browser only for the duration of your browsing session and are normally deleted when you close your browser. For example, they may be used to maintain a secure session while you use online banking services.
Persistent cookies - cookies that remain stored on your device after you close your browser, for a specified period or until they are deleted. They may be used, for example, to remember your preferences, recognise returning visitors, maintain security, or collect statistical information about the use of a website.

For a full list of the cookies and similar technologies we use, organised by category, please see Appendix A.

3. MANAGING COOKIES

You can manage your cookie preferences at any time through our Cookie Settings banner. You can also manage or delete cookies through your browser settings. Deleting or clearing cookies may also remove your previously saved preferences (including any opt-outs), meaning you may need to update your cookie choices again.

Each browser is different, so we recommend checking the ‘Help’ section in your browser (or your mobile device’s user manual) to learn how to change your cookie settings.

4. USING SOCIAL MEDIA VIA OUR SERVICES

Our website contains links to third-party websites, including our LinkedIn page. When you follow these links, the relevant third parties may use cookies and similar technologies in accordance with their own privacy and cookie policies.

5. PRIVACY NOTICE

For more information about how we use information collected by cookies and other tracking technologies, please refer to our Privacy Notice which is available on our website. This Cookie Policy should be read together with our Privacy Notice, which explains how Bilderlings Pay Limited processes personal data. If we change cookies that are currently in use, we will update this Cookie Policy. An updated version of Cookie Policy will be available on our website.

APPENDIX A: used cookies and similar technologies[cite: 2]

Strictly necessary[cite: 2]
bilderlings.com[cite: 2]
Cookie/technology identifier[cite: 2]	Purpose[cite: 2]	Retention[cite: 2]	Service Provider[cite: 2]
Cookie Consent[cite: 2]	Stores the user's cookie consent state for the current domain[cite: 2]	1 year[cite: 2]	Usercentrics[cite: 2]
cf clearance[cite: 2]	Security cookie. Stores proof that the visitor's browser passed a Cloudflare security challenge.[cite: 2]	1 year[cite: 2]	Cloudflare[cite: 2]
portal.bilderlings.com / account.bilderlings.com[cite: 2]
bilderlings_last_request_v1[cite: 2]	Helps to track and automatically ends session for inactive users (show user inactivity warning modal).[cite: 2]	session[cite: 2]	Bilder[cite: 2]
bilderlings_sticky_v1[cite: 2]	Used to tie current user session to a specific backend server during load balancing.[cite: 2]	session[cite: 2]	Bilder[cite: 2]
bilderlings_token_v1[cite: 2]	Used to identify current user after fully authenticated (after TFA).[cite: 2]	session[cite: 2]	Bilder[cite: 2]
bilderlings_user_v1[cite: 2]	Used to identify current user[cite: 2]	session[cite: 2]	Bilder[cite: 2]
portal_sid[cite: 2]	Used to identify the current user before fully authenticating (during TFA).[cite: 2]	session[cite: 2]	Bilder[cite: 2]
portal_language[cite: 2]	Used to persist selected user interface language.[cite: 2, 3]	1 year[cite: 2]	Bilder[cite: 2]
cf_clearance[cite: 3]	A cf_clearance cookie proves to Cloudflare that the visitor is a verified human and has passed Cloudflare's client-side verifications.[cite: 3]	1 year[cite: 3]	Cloudflare[cite: 3]
iidt[cite: 3]	This cookie allows to collect data to identify browsers, for security, fraud prevention and authentication purposes.[cite: 3]	1 year[cite: 3]	Fingerprint[cite: 3]
_vid_t[cite: 3]	This cookie collects signals that help to identify visitors, for security, fraud prevention and authentication purposes.[cite: 3]	1 year[cite: 3]	Fingerprint[cite: 3]
i18nextLng[cite: 3]	Used to persist selected user interface language.[cite: 3]	Persistent[cite: 3]	Bilder[cite: 3]
CookieConsent[cite: 3]	Stores the user's cookie consent state for the current domain[cite: 3]	1 year[cite: 3]	Usercentrics[cite: 3]
intercom-device-id-*[cite: 3]	Identifier for each unique device that interacts with the Messenger. Used by Intercom to determine the unique devices interacting with the Intercom Messenger to prevent abuse.[cite: 3]	270 days[cite: 3]	Intercom[cite: 3]
intercom-session-*[cite: 3]	Identifier for each unique browser session. It gives the user access to their previous conversations and identifies them in the Messenger.[cite: 3]	7 days[cite: 3]	Intercom[cite: 3]
intercom-id-*[cite: 3]	Allows the website to recognize the visitor, in order to optimize the chat-box functionality.[cite: 3, 4]	270 days[cite: 3]	Intercom[cite: 3]
Analytical[cite: 4]
bilderlings.com[cite: 4]
Cookie/technology identifier[cite: 4]	Purpose[cite: 4]	Retention[cite: 4]	Service Provider[cite: 4]
_ga[cite: 4]	Installed by Google to distinguish individual visitors and calculate site usage metrics.[cite: 4]	2 years[cite: 4]	Google[cite: 4]
_ga_#[cite: 4]	Used by Google Analytics to maintain session state, track page views, and monitor user navigation during a single visit.[cite: 4]	2 years[cite: 4]	Google[cite: 4]
landinPage[cite: 4]	Remembers the initial page URL you visited upon entering the website. This allows the website to maintain your context during your active session, ensuring that multi-step features, such as account registration and onboarding forms, function correctly.[cite: 4]	Persistent[cite: 4]	Google[cite: 4]
utm[cite: 4]	Remembers where you came from-like an email link, a social media post, or a specific ad-so we know which marketing campaigns brought you to our site[cite: 4]	Persistent[cite: 4]	Google[cite: 4]
portal.bilderlings.com / account.bilderlings.com[cite: 4]
AMP *[cite: 4]	The user session cookie contains metadata the SDK needs to function correctly[cite: 4]	1 year[cite: 4]	Amplitude[cite: 4]
AMP_remote_config_*[cite: 4]	Keeps tracking analytics configuration[cite: 4]	Persistent[cite: 4]	Amplitude[cite: 4]
AMP_TLDTEST[cite: 4]	On initialization, the SDK creates a cookie with AMP TLDTEST prefix to find a subdomain that supports cookie storage.[cite: 4, 5]	Session[cite: 4]	Amplitude[cite: 4]
AMP_TEST[cite: 5]	The SDK writes a cookie with the AMP_TEST prefix when it loads to check if cookies or local storage are enabled and functional in the user's browser.[cite: 5]	Session[cite: 5]	Amplitude[cite: 5]
AMP_diagnostics_*[cite: 5]	Used by Amplitude's SDK to support diagnostics, troubleshooting and monitoring of SDK operation, such as determining whether diagnostic data should be collected or controlling diagnostic/telemetry behaviour.[cite: 5]	Session[cite: 5]	Amplitude[cite: 5]
SEARCH SAMESITE[cite: 5]	This cookie is used for the correct sending of data to Google.[cite: 5]	1 year[cite: 5]	Google[cite: 5]
ga[cite: 5]	Installed by Google Analytics to distinguish individual visitors and calculate site usage metrics.[cite: 5]	2 years[cite: 5]	Google[cite: 5]
_ga_*[cite: 5]	Used by Google Analytics to maintain session state, track page views, and monitor user navigation during a single visit.[cite: 5]	2 years[cite: 5]	Google[cite: 5]
Marketing[cite: 5]
bilderlings.com[cite: 5]
Cookie/technology identifier[cite: 5]	Purpose[cite: 5]	Retention[cite: 5]	Service Provider[cite: 5]
_fbp[cite: 5]	Set by Facebook to connect your visit here with their ad network. It lets us see if our Facebook ads are actually working and helps Facebook show you relevant ads when you're using their apps.[cite: 5, 6]	3 months[cite: 5]	Meta (Facebook)[cite: 5]
_gcl_au[cite: 6]	It is a cookie that comes from Google Tag Manager or Google AdSense. It holds a code that connects the way you use Google Ads with what you do, on our website. This helps the people who run the website see how well their ads are working, learn about how visitors move around the site and watch for when things go like purchases or sign-ups.[cite: 6]	3 months[cite: 6]	Google[cite: 6]
_gcl_ls[cite: 6]	It is a browser Local Storage key created by Google Tag Manager or Google's Conversion Linker to store ad tracking identifiers directly on your device. It acts as a persistent record of how you arrived at a website after clicking a Google Ad, ensuring the advertiser knows which campaign drove your visit.[cite: 6]	Persistent[cite: 6]	Google[cite: 6]
lastExternal Referrer[cite: 6]	Detects how the user reached the website by registering their last URL-address.[cite: 6]	Persistent[cite: 6]	Meta (Facebook)[cite: 6]
lastExternal Referrer Time[cite: 6]	Detects when the user reached the website by registering time.[cite: 6]	Persistent[cite: 6]	Meta (Facebook)[cite: 6]
pagead/1p-user-list/#[cite: 6]	Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites.[cite: 6, 7]	Session[cite: 6]	Google[cite: 6]
test_cookie[cite: 7]	Used to check if the user's browser supports cookies.[cite: 7]	1 day[cite: 7]	Google[cite: 7]
portal.bilderlings.com / account.bilderlings.com[cite: 7]
_ Secure-1PAPISID[cite: 7]	This Google cookie is used for advertising and targeting purposes, including building a profile of a website visitor's interests and supporting the delivery of relevant and personalised Google advertising.[cite: 7]	1 year[cite: 7]	Google[cite: 7]
Secure-1PSID[cite: 7]	Used by Google for advertising and targeting purposes, including building a profile of a visitor's interests to support relevant and personalised advertising.[cite: 7]	1 year[cite: 7]	Google[cite: 7]
_ Secure-1PSIDCC[cite: 7]	Used by Google primarily in connection with security and advertising functionality, including maintaining the integrity of Google's services and supporting personalised advertising.[cite: 7]	1 year[cite: 7]	Google[cite: 7]
_Secure-3PAPISID[cite: 7]	Used by Google for advertising and targeting purposes, including building a profile of a visitor's interests to support relevant and personalised advertising.[cite: 7, 8]	1 year[cite: 7]	Google[cite: 7]
Secure-3PSID[cite: 8]	Used by Google for advertising and targeting purposes, including building a profile of a visitor's interests and supporting relevant and personalised advertising.[cite: 8]	1 year[cite: 8]	Google[cite: 8]
Secure-3PSIDCC[cite: 8]	Used by Google for advertising, targeting and related measurement/personalisation functions, including supporting the delivery of relevant advertising.[cite: 8]	1 year[cite: 8]	Google[cite: 8]
_Secure-3PSIDTS[cite: 8]	Used by Google in connection with advertising and measurement functions, including recognising and maintaining relevant state associated with a browser or Google service interaction.[cite: 8]	1 year[cite: 8]	Google[cite: 8]
SSID[cite: 8]	Used by Google to support personalisation and advertising, including recognising a browser and helping display relevant or personalised advertising on Google services.[cite: 8]	1 year[cite: 8]	Google[cite: 8]
DV[cite: 8]	Used by Google to support advertising and retargeting activities, including the delivery and measurement of relevant advertising.[cite: 8, 9]	1 year[cite: 8]	Google[cite: 8]
AEC[cite: 9]	Used by Google to detect spam, fraud and abuse and to help ensure that advertising impressions and interactions are valid and attributable to legitimate users.[cite: 9]	1 year[cite: 9]	Google[cite: 9]
_gcl_au[cite: 9]	It is a cookie that comes from Google Tag Manager or Google AdSense. It holds a code that connects the way you use Google Ads with what you do, on our website. This helps the people who run the website see how well their ads are working, learn about how visitors move around the site and watch for when things go like purchases or sign-ups.[cite: 9]	3 months[cite: 9]	Google[cite: 9]
pagead/1p-user-list/#[cite: 9]	Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites.[cite: 9]	Persistent[cite: 9]	Google[cite: 9]
_fbp[cite: 9]	Set by Facebook to connect your visit here with their ad network. It lets us see if our Facebook ads are actually working and helps Facebook show you relevant ads when you're using their apps.[cite: 9]	3 months[cite: 9]	Meta (Facebook)[cite: 9]
lastExternal Referrer[cite: 9]	Detects how the user reached the website by registering their last URL-address.[cite: 9, 10]	Persistent[cite: 9]	Meta (Facebook)[cite: 9]
lastExternal Referrer Time[cite: 10]	Detects when the user reached the website by registering time.[cite: 10]	Persistent[cite: 10]	Meta (Facebook)[cite: 10]
_gcl_ls[cite: 10]	It is a browser Local Storage key created by Google Tag Manager or Google's Conversion Linker to store ad tracking identifiers directly on your device. It acts as a persistent record of how you arrived at a website after clicking a Google Ad, ensuring the advertiser knows which campaign drove your visit.[cite: 10]	Persistent[cite: 10]	Google[cite: 10]
APISID[cite: 10]	A Google cookie used to identify a browser and support Google's advertising, personalization, measurement, and security functions, including in connection with embedded Google services.[cite: 10]	1 year[cite: 10]	Google[cite: 10]
HSID[cite: 10]	Used as a Google security and authentication cookie to help protect Google accounts and services against fraudulent or unauthorised activity.[cite: 10]	1 year[cite: 10]	Google[cite: 10]
IDE[cite: 10]	Used by Google advertising services to serve, personalise and measure advertisements on websites outside Google's own services.[cite: 10]	1 year[cite: 10]	Google[cite: 10]
NID[cite: 10]	Used by Google to remember user preferences and, depending on the user's settings, to support personalised functionality and advertising for signed-out users.[cite: 10, 11]	6 months[cite: 10]	Google[cite: 10]
SAPISID[cite: 11]	Used by Google to support authentication, personalisation and advertising-related functionality across Google services.[cite: 11]	1 year[cite: 11]	Google[cite: 11]
SID[cite: 11]	Used primarily for Google account authentication and security, helping protect Google services and user data against fraudulent or unauthorised access.[cite: 11]	1 year[cite: 11]	Google[cite: 11]
SIDCC[cite: 11]	Used by Google as a security cookie to protect Google services and user data against unauthorised access, fraud and abuse.[cite: 11]	1 year[cite: 11]	Google[cite: 11]
test_cookie[cite: 11]	Used to check if the user's browser supports cookies.[cite: 11]	1 day[cite: 11]	Google[cite: 11]
Secure-ENID[cite: 11]	Used by Google to remember user preferences and other information and, depending on the context and settings, to support analytics and personalised Google services. It can also support detection and resolution of service-related issues.[cite: 11]	1 year[cite: 11]	Google[cite: 11]

Legal Documents

What our lawyers have asked us to tell