Cookies
Information about the cookies we store on your computer
This site uses cookies. A cookie is a text file that identifies your computer to our server. Unless you are signed in, cookies in themselves do not identify the individual user, just the computer used. You have the opportunity to set your computer to accept all cookies, to notify you when a cookie is issued, or not to receive cookies at any time. The way in which you do this depends upon the web browser which you use. Please refer to the "Help" function for your browser or visit www.allaboutcookies.org. If you accept cookies, they may remain on your computer, unless you delete them. Please note that turning off cookies may limit your use of our website and website services.
Cookies used by this site:
__KBCookie__/...
Note that the name of this cookie contains the path to your presense (eg __KBCookie__/thurrock/fis/ This cookie lasts for the current session.It stores a shortlist ID, which is passed to the server to get the current session shortlist.
__KBLoggedIn__
This cookie lasts for the current session.It stores a simple true/false for whether or not you have successfully logged in.
kbroker_presence_controller
Max-Age : 1 yearThis cookie stores the user's response to the cookie consent message.This cookie is also used to store the Accessibility settings (contrast mode and / or text size) if they are set. NOTE: on the old wireframe, default Accessibility settings are written to this cookie on first page load.
JSESSIONID
This cookie lasts for the current session.It is generated by the Tomcat Servlet container, and used for session management for HTTP protocol. Since HTTP is a stateless protocol there is no way for a Web Server to relate two separate requests coming from the same client and Session management is the process to track user session using different session management techniques like Cookies and URL Rewriting.The cookie stores a generated ID that is read by the server in subsequent HTTP requests.
PHPSESSID
This cookie lasts for the current session.It is generated by the web server, and used for session management for HTTP protocol. Since HTTP is a stateless protocol there is no way for a Web Server to relate two separate requests coming from the same client and Session management is the process to track user session using different session management techniques like Cookies and URL Rewriting.The cookie stores a generated ID that is read by the server in subsequent HTTP requests.
Google Analytics Cookies
|
__utmb |
lasts 30 minutes |
used to track how long you stay on a site – when a visit starts and approximately ends |
|
__utmz |
lasts 6 months |
used to track where a visitor came from |
|
__utmc |
last for current session |
used to track how long you stay on a site – when a visit starts and approximately ends |
|
__utmt |
lasts 10 minutes |
Used to throttle request rate |
|
__utma |
lasts 2 years |
tracks each user’s amount of visits, and the time of the first, the previous, and the current visit |
After first loading, several targeted advertising cookies are then written by Google
ShareThis Cookies
|
__stid |
lasts 1 year |
monitors “user-activity”, e.g. Web pages viewed, navigation from page to page, time spent on each page etc.The ShareThis service only personally identifies you if you have separately signed up with ShareThis for a ShareThis account and given them your consent. |
|
__stidv |
lasts 1 year |
monitors “user-activity”, e.g. Web pages viewed, navigation from page to page, time spent on each page etc.The ShareThis service only personally identifies you if you have separately signed up with ShareThis for a ShareThis account and given them your consent.
|