Cookies are tiny text files which identify your computer to E-ACT’s server as a unique user when you visit certain pages on the E-ACT website and they are stored by your Internet browser on your computer’s hard drive.
You can block cookies by activating the settings on your browser that allow you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of the E-ACT website.
If you want to find out more information about cookies, go to http://www.allaboutcookies.org or to find out about removing them from your browser, go to http://www.allaboutcookies.org/manage-cookies/index.html.
Information about the cookies E-ACT uses
You can find more information about the individual cookies E-ACT uses and the purposes for which E-ACT uses them in the table below:
|PHPSESSID||PHP Session ID||Used to identify the user’s session on the server.|
|__utmc||Google Analytics||Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.||https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage|
|__utmt||Google Analytics||Used to throttle request rate.||https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage|
|__utmv||Google Analytics||Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics||https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage|