Cookies being used on our site
A European Union directive requires us to gain the consent of our users to download cookies on to their machines.
There are various methods we could use to get consent. For example, we could use ‘pop-ups’ prompting users to tick a box to confirm they give permission for us to download cookies on their machine. However, a user choosing not to download a cookie would be prompted with this request on every page. This is because there would be no way of storing their answer, this is what cookies are for.
Alternatively, we could use an online form that all users must complete before using the website.
There are two primary types of ‘cookie’ used on websites:
These are cookies that are stored on your computer to track repeat visits and site navigation. They are primarily used to help speed up or enhance your experience of services or functions offered on the site.
Temporary cookies (or session cookies)
These cookies are deleted when you shut down your browser.
Websites typically use temporary cookies to ensure that you are recognised when you move from page to page within one site and that any information you have entered is remembered during that particular visit.
Due to their important role of enhancing/enabling usability or site processes, disabling cookies may prevent users from using certain websites. Should you wish to disable cookies, however, you can find out how at: www.allaboutcookies.org/manage-cookies
Cookies on our site
|www.southglos.gov.uk||ASP.NET_SessionId||This cookie is essential to be able to use our website. It is created as soon as you visit our website, and stores a unique identifier for your session. This session cookie is not persisted on your hard disk and expires as soon as you leave the website.|
|Inovem e-consultations, e-petitions and groups||Inclusionware_Logon||Once you have logged on with username and password, so you don’t have to do it for every Web page you request from our service|
|Inovem e-consultations, e-petitions and groups||Inclusionware_rememberme||Once you have logged on with username and password, to make it easier to log in again if you choose ‘Remember me’. This cookie remembers if you want to be remembered.|
|SiteAnalyze||nmstat||This cookie is used to help record your use of this website. It is used to collect statistics about site usage such as when you last visited the site. This information is then used to improve the user experience on our website. This SiteAnalyze cookie contains a randomly generated ID used to recognise your browser when you read a page. The cookie contains no personal information and is used only for web analytics.|
|Google Analytics||__utma||This cookie is typically written to the browser upon the first visit to your site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits your site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to your site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure.|
|Google Analytics||__utmb||This cookie is used to establish and continue a user session with your site. When a user views a page on your site, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on your site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on your site for longer than 30 minutes. You can modify the default length of a user session with the _setSessionCookieTimeout() method.|
|Google Analytics||__utmc||This cookie is no longer used by the ga.js tracking code to determine session status.Historically, this cookie operated in conjunction with the __utmb cookie to determine whether or not to establish a new session for the user. For backwards compatibility purposes with sites still using the urchin.js tracking code, this cookie will continue to be written and will expire when the user exits the browser. However, if you are debugging your site tracking and you use the ga.js tracking code, you should not interpret the existence of this cookie in relation to a new or expired session|
|Google Analytics||__utmz||This cookie stores the type of referral used by the visitor to reach your site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within your own site. The cookie is updated with each page view to your site.|
|Google Analytics||__utmv||This cookie is not normally present in a default configuration of the tracking code. The __utmv cookie passes the information provided via the _setVar() method, which you use to create a custom user segment. This string is then passed to the Analytics servers in the GIF request URL via the utmcc parameter. This cookie is only written if you have added the _setVar() method for the tracking code on your website page.|
|Google Analytics||__utmx||This cookie is used by Website Optimizer and only set when the Website Optimizer tracking code is installed and correctly configured for your pages. When the optimizer script executes, this cookie stores the variation this visitor is assigned to for each experiment, so the visitor has a consistent experience on your site. See the Website Optimizer Help Center for more information.|
|Snap surveys||Some of the interactive on-line surveys we publish on our website use the SNAP software.A Cookie is sometimes set in the survey which saves a small text file, called a Cookie, on a respondent’s computer so that they will be unable to complete any further copies of the questionnaire until the cookie expires, thereby preventing multiple questionnaires from the same respondent.Or some surveys may be set up so they can be completed in several sessions (not all in one go) in this case partially complete responses are saved using cookies on the respondents computer, therefore cookies would need to be enabled to allow saving of the survey and then subsequently completing the survey again on the same computer at a later date. For information about SNAP surveys see www.snapsurveys.com|
|Inovem e-consultations, e-petitions and groups||SpiderUserPrefs||To remember your selections or preferences that you’ve already made when looking at information or using a service|
|Inovem e-consultations, e-petitions and groups||CFTOKEN (random number)||In completing a task, to enable you to complete the task without re-entering information already given, linking you to your (anonymous) session on the server|
|Inovem e-consultations, e-petitions and groups||JSESSIONID (random number)||In completing a task, to enable you to complete the task without re-entering information already given, linking you to your (anonymous) session on the server|
|Inovem e-consultations, e-petitions and groups||CFID (random number)||In completing a task, to enable you to complete the task without re-entering information already given, linking you to your (anonymous) session on the server|
|Socitm||socitm_exclude_me7||This cookie is set on a user’s machine when they decline our web satisfaction survey, and prevents the survey appearing again in any subsequent visits.|
|Homechoice||ASPSESSIONID (random number)|
|Capita||JSESSIONID||Capita are the company which handle and manage our Online Payments. The version we currently run is ????, and this only uses one cookie called JSESSIONID.Capita state that Version 7 onwards of this product purely uses ‘session cookies’. These are necessary for the application to work as they hold information when the user moves between pages. They do not hold any personally identifiable or sensitive data and are only temporary, and should be deleted by the browser when the user leaves the web-site.Essentially they hold a ‘one-off key’ which identifies data held on the server throughout the payment. Once the payment is complete, the server data linked to the random number no longer exists, regardless of whether the cookie has been deleted or not. The session cookie is only temporary and should be deleted by the browser when the user leaves the web-site.|
|School admissions||ASPSESSIONID (random number)|
Is there anything wrong with this page?