How we use Cookies

Cookies in use

Tracking and analytics cookies

Google Universal Analytics

We use Google Analytics to collect statistical data about our visitors. We collect this information in a way that does not identify you and the data is not shared with anybody else.

Name Purpose
_ga This helps us count how many people visit our website by tracking if you’ve visited before. By default it is set to expire after 2 years
_gat This is used to manage the rate at which page view requests are mades. It expires after 10 minutes.

Information on how to opt out of being tracked by Google Analytics across all websites and Google's use of cookies can be found on Google Analytics Opt-out and Google privacy pages.

Hotjar

We use Hotjar to help us understand user behaviour while on our websites and to provide some website features, like feedback forms or surveys. All visitor information is kept anonymous. Hotjar does not track or record visitors which have cookies disabled. 

Name Description
_hjIncludedInSample This is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.
_hjShownFeedbackMessage This records if you have used the feedback widget so the introductory message isn't shown again

Full technical information about the cookies used by Hotjar and what they do can be found in their online documentation 

Payments pages (payments.oxford.gov.uk)

Cookies used on our payments site are essential for it working correctly.

Name Description
anite_eforms_session,  anite_eforms_session_hash To store customers transactions in the shopping basket when making a series of payments. Expires immediately

Planning pages (public.oxford.gov.uk)

Name Description
.JSESSIONID A session cookie used for storing and retrieving values for a user. The information stored is kept server side and only the unique ID stored in the actual cookie will be sent back and forth between the user and the server. The information stored on the server will remain in the server's memory until the session expires.
ASP.NET_SessionId When you navigate to the site, the server establishes a unique session for you that lasts for the duration of your visit. For each session, ASP.NET maintains session state information where applications can store userspecific information. ASP.NET must track a session ID for each user so that it can map the user to session state information found on the server. By default, ASP.NET uses a nonpersistent cookie to store the session state.The information stored on the server will remain in the server’s memory until the session is either explicitly removed or expired (by default a session expires after 20 minutes of inactivity). The cookie itself contains no personal information.

Consultation pages (consultation.oxford.gov.uk)

Cookies used on these pages are necessary in order to provide the service that is requested by the visitor.

Name Description
.JSESSIONID This cookie contains a session key that allows our application to give you an individual user session and remember who you are (if you have logged in) and where you are in any workflow (eg. answering a multi-page questionnaire). It expires at the end of a session
ECONSLOGON If you have logged in with a username and password, this cookie only stores a unique token that our application uses to identify who you are. It does not store any information that anyone else could use to identify you. This cookie can persist even after the browser has been closed if you tick the 'keep me logged in' checkbox when you log in, allowing you use the application without having to log in again.
ECONSUSERPREFS This cookie remembers any viewing preferences (eg. how many rows to show on a table etc) so you don't have to set them each time you view information in the application.

Visit our consultation system cookies page for more details 

Council meetings and agenda pages (mycouncil.oxford.gov.uk)

Name Description
ASP.NET_SessionId When you navigate to the site, the server establishes a unique session for you that lasts for the duration of your visit. For each session, ASP.NET maintains session state information where applications can store userspecific information. ASP.NET must track a session ID for each use

3rd Party Cookies

3rd party cookies are cookies set with a different domain than that of the website you are on. We do not have any control over the way that these websites use your data. You should read their respective privacy policies carefully to find out what happens to any data that these services collect when you use them.