Cookie
Policy
EFFECTIVE OCTOBER 13, 2026
About cookies
Cookies are small text files which are downloaded to your device when you visit a website or application. The website or application may retrieve these cookies from your web browser (e.g. Internet Explorer, Mozilla Firefox or Google Chrome) each time you visit, so they can recognise you, remember your preferences and provide you with a more secure online experience.
Generally, cookies are very useful and are a common method used by almost every website you visit because they help to make your online experience as smooth as possible. For security reasons, many websites will not function at all without the use of cookies (or other similar technologies, such as “web beacons” or “tags”).
Cookies generally do not hold any information to identify an individual person, but are instead used to identify a browser on an individual machine. Sometimes cookies can collect certain data that can be considered as personal data (e.g. when performance or marketing cookies are concerned). Please check our Privacy Policy to learn how your personal data is managed.
If you prefer, you can restrict, block or delete cookies by changing your browser settings but that may mean that you won’t have the best possible user experience.
For more information about cookies and their impact on you and your browsing visit www.allaboutcookies.org.
If you are still looking for more information on how we use cookies then you can contact us via email at dpo@infinum.com.
Cookies we use
We use two types of cookies:
First-party cookies – cookies that are set by Infinum when you use our site
Third-party cookies – cookies that are set by an organization other than the Infinum when you use our site
Furthermore, we divide cookies by:
Required / Essential cookies – These cookies are essential in helping you to make use of the features and services we offer on the infinum.com website. Without these cookies, the services you want to use cannot be provided. These cookies do not gather information about you that could be used to identify you, and they do not monitor or remember where you have been on the internet.
Performance cookies – Performance cookies help us to understand how our customers use our site, so we can keep our products and services relevant, easy to use and up to date. For example, we can see which products and services are most popular, identify when and where errors occur, and test different versions of a page in order to provide an improved online experience. We will use these cookies only if you give us your consent.
Sometimes, the services we use to collect this information may be operated by other companies on our behalf. They may use similar technologies to cookies, known as “web beacons” or “tags”. These are anonymous and, as they are only used for statistical purposes, they do not contain or collect any information that identifies you.
Targeting cookies – We have relationships with carefully selected and monitored suppliers (third parties) who may also set cookies during your visit. The purpose of these cookies is “behavioral advertising” (also known as “behavioral targeting” or “remarketing”), which is a means of showing you relevant products and services based on what you appear to be interested in. Although these cookies can track your visits around the web they don’t know who you are. Without these cookies, online advertisements you encounter will be less relevant to you and your interests. We will use these cookies only if you give us your consent.
Managing cookies
Most internet browsers allow you to erase cookies from your computer hard drive, block all cookies (or just third-party cookies) or warn you before a cookie is stored on your device.
Please note, if you choose to block all cookies, our site will not function as intended and you might not be able to use or access some services we provide.
In the next chapter we will explain how you can delete cookies inside your browser. Please keep in mind that we will still use required cookies for the basic functionality of the Infinum website.
You can manage the usage of cookies on our website by clicking here.
You can also find further information about cookies and the steps you can take to protect your privacy on the internet through Your Online Choices website.
How to manage cookies in Google Chrome
This guide is telling you how to remove the cookies in Google Chrome depending on the device.
Windows and MacOS users
Open Chrome.
In the top right corner of the browser you will see three dots, which indicates a settings menu.
Scroll down to the bottom of the page and click on “Advanced.”
Click on the section “Clear browsing data.”
Under the “All cookies and site data” section, you can customize which cookies to delete based on a specific time range and other options. Finally, you can complete the deletion by clicking “Clear data.” You can also clear your cache, which is where your computer stores previously viewed websites so they can be loaded faster on future visits.
Android users
On your Android phone or tablet, open the Chrome app.
To the right of the address bar, tap on “More,” or what looks like three dots, and then select “Settings.”
Tap on the “Privacy” category and then select “Clear browsing data.”
Here you can personalize your selections for which cookies to delete by selecting a specific time range.
Once you have made your selections, you can then check “Cookies and site data.” Uncheck all the other items.
Tap “Clear data.”
iOS users
On your device, launch the Chrome app
At the top right, tap on the three dots, scroll down and then select “Settings.”
Under settings, tap “Privacy” then “Clear browsing data.”
Select “Cookies, site data,” and uncheck all other items.
Tap on “Clear browsing data.”
Then select “Done.”
How to manage cookies in Firefox
This guide is telling you how to remove the cookies in Firefox depending on the device.
Windows and MacOS users
Open Firefox on your computer.
In the upper right-hand corner of the browser, click the “menu bars,” which look like three parallel lines, and click the “Privacy” tab.
Here you can select “Clear your recent history.”
Be sure that only “Cookies” is checked, and then select the time frame for which you would like to delete your cookies. If you want to delete all cookies, select “Everything.”
Double check your selections to make sure that other items you want to keep are not selected, and then hit “Clear now.”
Android users
Some instructions may vary based on the type of phone you have and what version of Firefox it is running. Look for the menu icon (three bars) located at the top right corner. On older Android devices you’ll have to press the hardware menu key and then tap “More.”
Go to the “Settings” menu.
On the settings menu, look for “Privacy & security” and select “Clear private data.”
You will then be taken to a list of what can be cleared where you can select “Cookies & active logins.”
After you have made your selection, tap the “Clear data” button to finalize deleting cookies.
iOS users
Open Firefox.
Click on the “menu bars,” which looks like three parallel lines in the lower right-hand corner of the browser window.
Select “Settings.”
Scroll down to “Privacy.”
Select “Clear private data.”
Make sure only “Cookies” is selected, then tap on “Clear private data.”
How to manage cookies in Safari
This guide is telling you how to remove the cookies in Safari depending on the device.
MacOS users
Open Safari.
Select “Preferences” from the dropdown Safari menu.
Click on “Privacy,” then on “Manage Website Data.”
Click on “Remove all” from the dropdown menu.
iOS users
Go into the Settings menu on your device.
Scroll down to “Safari,” then “Advanced,” then “Website Data”
Tap on “Clear history and website data” to clear cookies.
How to manage cookies in Internet Explorer
This guide is telling you how to remove the cookies in Internet Explorer running Windows 10, Windows 8.1, Windows 7 on PC.
Launch Internet Explorer.
Select “Tools” from the menu, select the “Safety” menu, and then select “Delete browsing history.”
Make sure that the “Cookies and website data” checkbox is selected, and then click on “Delete.”
How to manage cookies in Microsoft Edge
This guide is telling you how to remove the cookies in Edge browser on PC.
Launch Microsoft Edge
Go to the “more” menu and select “Settings.”
Scroll to “Clear browsing data,”
Select “cookies and saved website data” and then select clear.
Required cookies
| Cookie | Type | Provider | Expiry | Description |
|---|---|---|---|---|
| gdpr | First-party | Infinum | 365 days | Stores which cookie categories the visitor has accepted, so that the consent box is not shown again on the next visit. |
| gdpr-accept-date | First-party | Infinum | 365 days | Stores the date on which the visitor made their cookie choice. |
| esForms-country | First-party | Infinum | 15 days | Stores the visitor’s country in order to display appropriate currencies on the forms. |
| es-storage, es-storage-<ID> | First-party | Infinum | Persistent (browser storage) | Stores website interface state in the browser so that the website works as intended. |
| rc::a | Third-party | Google (reCAPTCHA) | Persistent (browser storage) | Used by Google reCAPTCHA to distinguish humans from bots on our forms. |
| rc::c | Third-party | Google (reCAPTCHA) | Session | Used by Google reCAPTCHA to distinguish humans from bots on our forms. |
| __cf_bm | Third-party | Cloudflare (set by embedded services such as HubSpot, LinkedIn, G2 and X) | 30 minutes | Cloudflare bot management cookie used to distinguish human from automated traffic. Essential for security and preventing malicious requests. |
| _cfuvid | Third-party | Cloudflare (set by embedded CodeSandbox content) | Session | Cloudflare cookie used for rate limiting and bot protection. |
| cf_clearance | Third-party | Cloudflare (set by embedded CodeSandbox content) | 1 year | Stores the result of Cloudflare’s security check so that the visitor is not asked to repeat it. |
| AEC | Third-party | 6 months | Ensures that requests within a browsing session are made by the user and not by other sites. This cookie prevents malicious sites from acting on behalf of a user without that user’s knowledge. | |
| CONSENT | Third-party | 2 years | Stores the visitor’s consent state for Google services embedded on the website. |
Performance cookies
| Cookie | Type | Provider | Expiry | Description |
|---|---|---|---|---|
| _ga | Third-party | Google Analytics | 400 days | Used by Google Analytics to distinguish visitors and to keep track of site usage for the site’s analytics reports. |
| _ga_<ID> | Third-party | Google Analytics 4 | 400 days | Used by Google Analytics 4 to persist session state and to calculate session data. The name contains the measurement ID of the website. |
| __hstc | Third-party | HubSpot | 180 days | Stores the visitor’s ID, the timestamps of the first, last and current visit and the number of visits. Used by HubSpot for analytics. |
| hubspotutk | Third-party | HubSpot | 180 days | Keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts. |
| __hssc | Third-party | HubSpot | 30 minutes | Used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __hssrc | Third-party | HubSpot | Session | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. |
| hs-cta-interactions#cta | Third-party | HubSpot | Persistent (browser storage) | Stores the visitor’s interactions with HubSpot call-to-action elements. |
| _clck | Third-party | Microsoft Clarity | 1 year | Persists the Clarity user ID and preferences, so that later visits are attributed to the same user ID. |
| _clsk | Third-party | Microsoft Clarity | 1 day | Connects multiple page views by a visitor into a single Clarity session recording. |
| CLID | Third-party | Microsoft Clarity | 1 year | Identifies the first time Clarity saw this user on any site using Clarity. |
| MR | Third-party | Microsoft | 1 week | Indicates whether to refresh MUID. |
| SM | Third-party | Microsoft | Session | Used in synchronizing the MUID across Microsoft domains. |
| bugsnag-anonymous-id | Third-party | Bugsnag | Persistent (browser storage) | Anonymous identifier used by the error monitoring service to count how many visitors are affected by an error. |
| NRBA_SESSION | Third-party | New Relic | Persistent (browser storage) | Used by New Relic browser monitoring to track the performance of a session. |
| AMP_<ID> | Third-party | Amplitude (set by embedded CodeSandbox content) | 1 year | Used for analytics of the embedded CodeSandbox content. |
| AMP_TEST | Third-party | Amplitude (set by embedded CodeSandbox content) | Session | Used for analytics of the embedded CodeSandbox content. |
| AMP_unsent_<ID> | Third-party | Amplitude (set by embedded CodeSandbox content) | Persistent (browser storage) | Temporarily stores analytics events of the embedded CodeSandbox content that have not been sent yet. |
Targeting cookies
| Cookie | Type | Provider | Expiry | Description |
|---|---|---|---|---|
| _gcl_au | Third-party | Google Ads | 90 days | Used by Google Ads to store and track conversions after a visitor has clicked on one of our ads. |
| IDE | Third-party | Google (DoubleClick) | 1 year | Used by Google DoubleClick to register and report the visitor’s actions after viewing or clicking one of the advertiser’s ads, with the purpose of measuring the efficacy of an ad and to present targeted ads to the visitor. |
| NID | Third-party | 6 months | Used by Google to remember the visitor’s preferences and to show personalised advertising. | |
| SID, HSID | Third-party | 2 years | Used by Google to display personalized advertisements on Google sites, based on recent searches and previous interactions, and to protect visitor data from unauthorized access. | |
| SSID | Third-party | 2 years | Enables Google to collect user information for videos hosted by YouTube. | |
| APISID, SAPISID | Third-party | 2 years | Used by Google to personalise advertisements on websites based on recent searches and interactions. | |
| __Secure-1PAPISID, __Secure-1PSID | Third-party | 2 years | Used for targeting purposes to build a profile of the website visitor’s interests in order to show relevant and personalised Google advertising. | |
| __Secure-3PAPISID, __Secure-3PSID | Third-party | 2 years | Builds a profile of website visitor interests to show relevant and personalized ads through retargeting. | |
| __Secure-ENID | Third-party | 1 year | Stores digitally signed and encrypted data from the unique Google ID and the most recent login time. It can also be used for targeting purposes to display relevant and personalized advertising content. | |
| SEARCH_SAMESITE | Third-party | 5 months | Used for the correct sending of data to Google. | |
| images | Third-party | Google (gstatic.com) | Session | Tracking pixel loaded from Google that is used for advertising purposes. |
| _fbp | Third-party | Meta (Facebook) | 90 days | Facebook pixel cookie used to identify visitors for personalized advertising. |
| _fbc | Third-party | Meta (Facebook) | 90 days | Stores the identifier of the Facebook ad click that brought the visitor to the website. |
| lastExternalReferrer, lastExternalReferrerTime | Third-party | Meta (Facebook) | Persistent (browser storage) | Used by the Meta pixel to store the last external referrer of the visitor and the time of the visit. |
| multiFbc | Third-party | Meta (Facebook) | Persistent (browser storage) | Stores Facebook ad click identifiers for ad measurement. |
| _rdt_uuid | Third-party | 90 days | Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor’s preferences. | |
| _rdt_em | Third-party | 90 days | Used by the Reddit pixel for advertising measurement and matching. | |
| AnalyticsSyncHistory | Third-party | 30 days | Used to store information about the time a sync with the lms_analytics cookie took place. | |
| bcookie | Third-party | 1 year | Used by LinkedIn for tracking the use of embedded services. | |
| li_gc | Third-party | 180 days | Stores the visitor’s cookie consent state for the current domain. | |
| lidc | Third-party | 1 day | Used by LinkedIn for tracking the use of embedded services. | |
| lang | Third-party | Session | Set by LinkedIn when a web page contains an embedded LinkedIn element. | |
| UserMatchHistory | Third-party | 30 days | Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor’s preferences. | |
| li_adsId | Third-party | Persistent (browser storage) | Used by the LinkedIn Insight Tag for advertising measurement. | |
| MUID | Third-party | Microsoft | 1 year and 24 days | Identifies unique web browsers visiting Microsoft sites. Used for advertising, site analytics and other operational purposes. |
| ANONCHK | Third-party | Microsoft | 10 minutes | Indicates whether MUID is transferred to ANID, a cookie used for advertising. |
| dd_anonymous_id | Third-party | Dreamdata | 1 year | Anonymous identifier used by Dreamdata to attribute marketing activity to revenue. |
| dd_user_id | Third-party | Dreamdata | Session | Identifier of a known user, used by Dreamdata for marketing attribution. |
| ajs_anonymous_id | Third-party | Dreamdata | 1 year | Anonymous visitor identifier used by the Dreamdata analytics script. |
| ajs_user_id | Third-party | Dreamdata | Session | Identifier of a known user used by the Dreamdata analytics script. |
| __tld__ | Third-party | Dreamdata | Session | Temporary test cookie used by the Dreamdata analytics script to detect the top-level domain. |
| dreamdataio.*, dd_user_traits, ajs_user_traits, ajs_group_id, ajs_group_properties | Third-party | Dreamdata | Persistent (browser storage) | Store visitor traits and queued events of the Dreamdata analytics script. |
| g2tracking | Third-party | G2 | Persistent (browser storage) | Used by G2 to track visitors’ interest in products for buyer intent analytics. |
| __ptq.gif | Third-party | HubSpot | Session | Tracking pixel used by HubSpot to register visits for advertising and marketing purposes. |
| YSC | Third-party | YouTube (Google) | Session | Registers a unique ID to keep statistics of what videos from YouTube the visitor has seen. |
| VISITOR_INFO1_LIVE | Third-party | YouTube (Google) | 180 days | Tries to estimate the visitor’s bandwidth on pages with integrated YouTube videos. |
| __Secure-YNID, __Secure-YEC, __Secure-BUCKET, __Secure-ROLLOUT_TOKEN | Third-party | YouTube (Google) | 180 days (__Secure-YEC: session) | Used by YouTube to store the visitor’s preferences and to personalize and measure video content and advertising. |
| LAST_RESULT_ENTRY_KEY | Third-party | YouTube (Google) | Session | Used by YouTube to store the last search result entry of the embedded player. |
| TESTCOOKIESENABLED | Third-party | YouTube (Google) | 1 day | Used by YouTube to check whether the browser accepts cookies. |
| yt-icons-last-purged, YtIdbMeta#databases, LogsDatabaseV2:V#||LogsRequestsStore, ServiceWorkerLogsDatabase#SWHealthLog | Third-party | YouTube (Google) | Persistent (browser storage) | Used by the embedded YouTube player to store its settings in the browser. |
| i/jot/embeds | Third-party | X (syndication.x.com) | Session | Tracking pixel used by embedded X posts. |
| _bit | Third-party | Bitly | 180 days | Used by Bitly for link tracking and analytics. |
| signedIn | Third-party | CodeSandbox | Session | Used by embedded CodeSandbox content to store the sign-in state of the visitor. |
| __test__, CodeSandboxApp#sandboxes, CodeSandboxApp#local-forage-detect-blob-support | Third-party | CodeSandbox | Persistent (browser storage) | Used by embedded CodeSandbox content to store its state and to test browser storage features. |