Cookies, beacons and similar technologies
We use the following cookies on our website:
|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.|
Cookies for third parties
When you visit a page on our site with content embedded from third parties, for example, Google Analytics, HubSpot or Bizo, cookies may be downloaded onto your device. We do not set or control these cookies and they can change at any time without Sreda Money knowledge. If you are concerned about the types of cookies that may be downloaded you can check the third party websites for more information about these cookies.
Below are the known cookie names for third party services:
|DSID||By Google – 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||By Google – 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.|
|__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.|
|__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.|
|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|
|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.|
Please note, however, that some services may not function properly without cookies and if you disable them, the services or any part of services may no longer be available to you.
Please note that our social networking accounts are governed by the cookies policy of the respective social media network.