Cookies Policy

What are cookies and how do they work?

Cookies are small information files downloaded to your device (computer or mobile phone) from the websites you visit. Cookies pose no threat to devices. When you are visiting a website your internet browser reads the cookie and provides information, for example, recognizes you as a visitor and adjusts the contents of the website to suit your needs.

What cookies does Moneynetint use?

Cookie name What is it?
DSID Google Analytics - We use other cookies with names such as DSID, FLC, AID, TAID, and exchange_uid. Other Google properties, like YouTube, may also use these cookies to show you more relevant ads.
IDE Google Analytics - We also use one or more cookies for advertising we serve across the web. One of the main advertising cookies on non-Google sites is named ‘IDE‘ and is stored in browsers under the domain doubleclick.net.
NID The NID cookie contains a unique ID Google uses to remember your preferences and other information, such as your preferred language (e.g. English), how many search results you wish to have shown per page (e.g. 10 or 20), and whether or not you wish to have Google’s SafeSearch filter turned on.
PHPSESSID The PHPSESSID cookie is native to PHP and enables websites to store serialised state data. On the Action website it is used to establish a user session and to pass state data via a temporary cookie, which is commonly referred to as a session cookie.
__cfduid Cloudflare cfduid cookie - used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. For example, if the visitor is in a coffee shop where there are a bunch of infected machines, but the specific visitor's machine is trusted (e.g. because they've completed a challenge within your Challenge Passage period), the cookie allows us to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does store any personally identifiable information.
__hssc HubSpot - Cookie for keeping track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains: the domain, viewCount (increments each pageView in a session), session start timestamp. (Expires: 30 min)
__hssrc HubSpot - Whenever HubSpot changes the session cookie, this cookie is also set. We set it simply to the value "1", and use it to determine if the user has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. (Expires: None. Session cookie)
__hstc HubSpot - The main cookie for tracking visitors. It contains: the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session) (Expires: 2 years)
__utma Google Analytics - This cookie is what’s called a “persistent” cookie, as in, it never expires (technically, it does expire…in the year 2038…but for the sake of explanation, let’s pretend that it never expires, ever). This cookie keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred. Google Analytics uses the information from this cookie to calculate things like Days and Visits to purchase.
__utmc Google Analytics - The B (__utmb) and C cookies are brothers, working together to calculate how long a visit takes. __utmb takes a timestamp of the exact moment in time when a visitor enters a site, while __utmc takes a timestamp of the exact moment in time when a visitor leaves a site. __utmb expires at the end of the session. __utmc waits 30 minutes, and then it expires. You see, __utmc has no way of knowing when a user closes their browser or leaves a website, so it waits 30 minutes for another pageview to happen, and if it doesn’t, it expires.
__utmz Google Analytics - Mr. __utmz keeps track of where the visitor came from, what search engine you used, what link you clicked on, what keyword you used, and where they were in the world when you accessed a website. It expires in 15,768,000 seconds – or, in 6 months. This cookie is how Google Analytics knows to whom and to what source / medium / keyword to assign the credit for a Goal Conversion or an Ecommerce Transaction. __utmz also lets you edit its length with a simple customization to the Google Analytics Tracking code.
_bizo_bzid Bizo.
Tracking for Bizo's business demographics data.
_bizo_cksm Bizo.
Tracking for Bizo's business demographics data.
_bizo_np_stats Bizo.
Tracking for Bizo's business demographics data. More info can be found at
http://media.bizo.com/lp/channelpartners/media/basics/Bizo%20FAQ%20Private%20Audience%20Targeting_ver3.pdf.
anj The anj cookie contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside the Platform on the Platform.
hubspotutk This cookie is used for to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. (Expires: 10 years)
icu The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown.
sess The sess cookie contains a single non-unique value: “1”. It is used by the Platform to test whether a browser is configured to accept cookies.
uuid2 This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices.

How to remove cookies from your device?

The cookies used by Moneynetint have no personal data and are not used for your identification. However, you can enable certain cookies or delete them altogether in the web browser settings.
Moneynetint acts in compliance with the legal acts regulating cookie use.
You can find more information of how to remove cookies at https://www.aboutcookies.org/how-to-delete-cookies.