Skip to content

Cookies Policy

Last updated June 2023

To make the Edenred Payment Solutions website work properly, we sometimes place small data files called cookies on your device.


What are Cookies?

A cookie is a small text file that a website stores on your computer or mobile device when you visit the site.

First-party cookies are cookies set by the website you’re visiting. Only that website can read them. In addition, a website might potentially use external services, which also set their own cookies, known as third-party cookies.

Persistent cookies are cookies saved on your computer and that are not deleted automatically when you quit your browser, unlike a session cookie, which is deleted when you quit your browser.

Every time you visit the Edenred Payment Solutions website, you will be prompted to accept or refuse cookies.

The purpose of cookies is to enable the website to remember your preferences (such as language, etc.) for a certain period of time or to establish anonymised statistics about the browsing experience on the website.


How do we use cookies?

The Edenred Payment Solutions website uses first-party cookies that are set and controlled by Hubspot (

There are two types of first-party cookie that we use:

  1. Visitor preferences

These are set by us and only we can read them. They remember if you have agreed to or refused our Cookie Policy.

  1. Analytics

We use these cookies purely for internal research on how we can improve the service we provide for all our users. The cookies simply assess how you interact with our website, the total time you spend on our website, the time you spend on each page and in what order those pages were visited.

The analytics cookies registered the following information as well:

  • The geographic location of the website visitor
  • What browser and operating system are being used
  • Screen size and whether Flash or Java is installed
  • The referring site

All this information is collected from you as an anonymous user (the data gathered does not identify you personally).

Also, this data is not shared with any third parties or used for any other purpose. The anonymised statistics could be shared with contractors working on communication projects under contractual agreement with Edenred Payment Solutions.

However, you are free to refuse these types of cookies via the cookie banner you’ll see on the first page you visit.




Cookie type and duration

NESSESSARY COOKIES These are essential cookies that do not require consent.


E.G.Cookiebot or Google etc

This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.

This cookie is set when you give visitors the choice to opt out of cookies.

It contains the string "yes" or "no".


6 months



This cookie can be set to prevent the tracking code from sending any information to HubSpot.

It contains the string "yes".


6 months



This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.

It contains the string "yes" or "no".


7 days



This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.

It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.


It expires at the end of the session.



When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.

The cookie name is unique for each password-protected page.

It contains an encrypted version of the password so future visits to the page will not require the password again.

14 days



This cookie is used to determine and save whether the chat widget is open for future visits.

It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity.

If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes.

It contains a boolean value of True if present.

30 minutes



This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.

It contains a boolean value of True or False.

1 day



This cookie is set when visitors log in to a HubSpot-hosted site.

It contains encrypted data that identifies the membership user when they are currently logged in.

7 days



Length of visit

20 minutes



This cookie is used to ensure that content membership logins cannot be forged.

It contains a random string of letters and numbers used to verify that a membership login is authentic.

It expires at the end of the session.



This cookie is used to save a visitor’s selected language choice when viewing pages in multiple languages.

It is set when a visitor selects a language from the language switcher and is used as a language preference to redirect them to sites in their chosen language in the future if they are available.

It contains a colon delimited string with the ISO639 language code choice on the left and the top level private domain it applies to on the right. An example will be "".

2 years



This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. Learn more about Cloudflare cookies (

It expires at the end of the session.



This cookie is set by HubSpot's CDN provider and is a necessary cookie for bot protection. Learn more about Cloudflare cookies (

30 minutes

ANALYTICS COOKIES These are non-essential cookies controlled by the cookie banner. If you're a visitor to a site supported by HubSpot, you can opt out of these cookies by not giving consent.



The main cookie for tracking visitors.

It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).

6 months



This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.

It contains an opaque GUID to represent the current visitor.

6 months



This cookie keeps track of sessions.

This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.

It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.

30 minutes



Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.

If this cookie does not exist when HubSpot manages cookies, it is considered a new session.

It contains the value "1" when present.

It expires at the end of the session.

If you are logged in to HubSpot, HubSpot will set additional authentication cookies. Learn more about cookies set in the HubSpot product. You can also see whether a contact accepted these cookies in their timeline.

FUNCTIONALITY COOKIES This is the cookie used for the chatflows tool. If you're a visitor, this allows you to chat with a representative on the site.



This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser.

With the Consent to collect chat cookies setting turned on:

  • If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history.

  • The messagesUtk cookie will be treated as a necessary cookie.

When the Consent to collect chat cookies setting is turned off, the messagesUtk cookie is controlled by the Consent to process setting in your chatflow.

HubSpot will not drop the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted.

This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped for will not apply to the visitor when they visit, and vice versa. 

It contains an opaque GUID to represent the current chat user.

6 months

Chatflow cookie consent text

With the Consent to collect chat cookies setting enabled, HubSpot will prompt visitors for consent to drop a cookie in their browser before the start a chat or when they attempt to the leave the page during a chat conversation. This cookie is used to interact with website visitors and provide a visitor's chat history.

If you choose to display the banner before the visitor starts a chat and the visitor does not give consent, they will not be able to start the chat.

If you choose to display the banner upon exit intent, however, the visitor can start the chat, but if they don't consent to cookies before navigating away from the page, the chat widget will reset and the conversation will end.

With this setting disabled, a visitor can start a chat and give consent to process their information via the Consent to process setting

Visitors can also accept or decline cookies on the HubSpot cookie banner if it is enabled on your pages. 

  • If a visitor accepts the cookie when they start a chat, but then clicks Decline on the HubSpot cookie banner, the cookie will be removed. 

  • If a visitor clicks Decline on the HubSpot cookie banner before starting a chat, HubSpot will not drop a cookie or prompt them to consent to cookies in the chat widget. 

Advertisement cookies

Advertisement cookies are ad pixel cookies (such as Facebook, LinkedIn and Google) that you can opt to install using the HubSpot ads tool.

If you have the Facebook pixel code installed on your website, Facebook may set a cookie in a visitor's browser.

If you use the HubSpot ads tool to select and install your Facebook pixel on pages with the HubSpot tracking code, HubSpot will link the placing of that pixel code to the cookie notification banner. If you require opt-in consent via this banner, the Facebook pixel will not be able to set any cookies until the visitor has have opted in. 

If you manually placed the pixel code on pages (e.g., by editing your site header HTML), HubSpot will not be able to control the visitors Facebook is able to set cookies on.

For additional information, refer to Facebook's business tools terms and Facebook's cookie consent guide

Cookies from third-party systems 

HubSpot cannot control cookies placed by third-party scripts on your website. When a visitor accepts cookies via the HubSpot consent banner, they consent to HubSpot's cookies only.

However, you can put code in place to know when a visitor has accepted or declined HubSpot cookie tracking, then send that information to your third-party system. Learn more about using HubSpot's consent banner for third-party scripts

You can also scan for and block cookies on HubSpot pages using the cookie scanning feature (beta). After a domain has been scanned, you can block specific cookies. This will stop these cookies from being dropped on a visitor's device until they consent to them via cookie banner. Learn more about the cookie scanning feature (beta).


How can you manage cookies?

You can manage/delete cookies as you wish.

Removing cookies from your device

‍You can delete all cookies that are already on your device by clearing the browsing cache/history of your browser. This will remove all cookies from all websites you have visited.

Be aware though that you may also lose some saved information (e.g. saved login details, site preferences).

Managing site-specific cookies

For more detailed control over site-specific cookies, check the privacy and cookie settings in your preferred browser.

Blocking cookies

‍You can set most modern browsers to prevent any cookies being placed on your device, but you may then have to manually adjust some preferences every time you visit the site.