Cookies

Pages in Cookies

  1. 1. Our use of cookies
  2. 2. You are here: Cookies set by our website
  3. 3. Subsite and third party cookies

2. Cookies set by our website

We limit cookies as much as possible however we do use them when we feel it will lead to improved user experience.

Disclaimer: this policy is subject to updates and changes. Users are encouraged to regularly review our policy. This scan was generated on 30 January 2025 using the CIVIC cookie site scanner and followed up by a manual check.

Detected cookies

Cookie name Domain Priority How long it lasts (expiry)
PHPSESSID www.reigate-banstead.gov.uk Medium Session
TestCookie www.reigate-banstead.gov.uk Medium Session
SESSIONCHECK my.reigate-banstead.gov.uk Medium 6 hours
SESSfsauthsession my.reigate-banstead.gov.uk Medium Session
APP_LANG my.reigate-banstead.gov.uk Medium 24 hours
_ga reigate-banstead.gov.uk Medium 1 year
_ga_6HF8FD0Y4J reigate-banstead.gov.uk Medium 1 year
AWSALB my.reigate-banstead.gov.uk Medium 7 days
AWSALBCORS my.reigate-banstead.gov.uk Medium 7 days
localtime my.reigate-banstead.gov.uk Medium Session
_gid reigate-banstead.gov.uk Medium 24 hours
_gat_UA-49006260-1 reigate-banstead.gov.uk Medium 58 seconds
SimpleSAMLSessionID my.reigate-banstead.gov.uk Medium Session
_gat reigate-banstead.gov.uk Medium 59 seconds
product my.reigate-banstead.gov.uk Medium 24 hours
AchieveFormsRedirectLink my.reigate-banstead.gov.uk Medium 24 hours
gx-pmv-tk xmap.cloud Medium 2 hours
XSRF-TOKEN whereilive.reigate-banstead.gov.uk Medium 2 hours
reigatebanstead_session whereilive.reigate-banstead.gov.uk Medium 2 hours
_ga_V9YG2SD1E0 reigate-banstead.gov.uk Medium 1 year

Functional Cookies

Functionality cookies are used to enhance the performance of a website. Without them, certain functions of the website may not be available.

Cookie name What the cookie does How long it lasts (expiry)
PHPSESSID Cookie generated by applications based on the PHP language. This is a general purpose identifier used to maintain user session variables. It is normally a random generated number, how it is used can be specific to the site, but a good example is maintaining a logged-in status for a user between pages. 60 minutes
AWSALB These cookies enable us to allocate server traffic to make the user experience as smooth as possible. A so-called load balancer is used to determine which server currently has the best availability. The information generated cannot identify you as an individual. 7 days
AWSALBCORS For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSALBCORS (ALB). 7 days
AWSELBCORS For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSELBCORS (ALB). Session
AWSELB AWS Classic Load Balancer Cookie: Load Balancing Cookie: Used to map the session to the instance. Session
AWSALBTGCORS For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSELBCORS (ALB). Session
AWSALBTG For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSELBCORS (ALB). Session
aws-csds-token Anonymous metrics validation token 1 hour
aws_lang Stores the language used with AWS. Session
aws-target-visitor-id Used to collect anonymised information about how which web pages are visited, how long users spend on pages and what users search for 1 year
aws-priv Anonymous cookie for privacy regulations 1 year

Analytics cookies

Analytical cookies help us to improve our website by collecting and reporting information on its usage.

Cookie name What the cookie does How long it lasts (expiry)
_ga ID used to identify users 1 year
_ga_* Used to identify and track an individual user session 2 years
_gid ID used to identify users for 24 hours 24 hours
_gat Used to monitor number of Google Analytics server requests when using Google Tag Manager 58 seconds
_dc_gtm_ Used to monitor number of Google Analytics server requests 1 minute
AMP_TOKEN Contains a token code that is used to read out a Client ID from the AMP Client ID Service. By matching this ID with that of Google Analytics, users can be matched when switching between AMP content and non-AMP content. 1 year
_gat_* Used to set and get tracking data 1 hour
_gac_ Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. 90 days
__utma ID used to identify users and sessions 2 years
__utmt Used to monitor number of Google Analytics server requests 10 minutes
__utmb Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server 30 minutes
__utmc Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. session
__utmz Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Analytics server 6 months
__utmv Contains custom information set by the web developer through the _setCustomVar method in Google Analytics. This cookie is updated each time new data is sent to the Google Analytics server 2 years
__utmx Used to determine whether a user is included in an A / B or Multivariate test 18 months
__utmxx Used to determine when the A / B or Multivariate test in which the user participates ends 18 months
FPAU Assigns a specific ID to the visitor. This allows the website to determine the number of specific user-visits for analysis and statistics session
FPID Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator 1 years
FPLC This FPLC cookie is the cross-domain linker cookie hashed from the FPID cookie. It’s not Http Only, which means it can be read with JavaScript. It has a relatively short lifetime, just 20 hours 20 hours
_clck Used to send data to Microsoft Clarity about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels 1 year
_clsk Used to send data to Microsoft Clarity about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels 1 day

Google Analytics

We use Google Analytics to collect information about how you use this website (reigate-banstead.gov.uk). We do this to help make sure the site is meeting your needs and to make improvements based on our findings.

Read Google's overview of privacy and safeguarding data and find out how you can opt out of being tracked by Google Analytics across all websites.

Microsoft Clarity

We use Microsoft Clarity to help us understand how users interact with the website. We do this using behavioural metrics, heat maps, and session replays provided by Microsoft Clarity to help us improve our website.

For information about how Microsoft collects and uses your data, visit the Microsoft Privacy Statement. You can control Microsoft’s use of your data for personalised advertising from Microsoft by visiting their opt-out page. You can access and clear some of your data through the Microsoft privacy dashboard.

Cookie Policy for EU/UK

We comply with GDPR and UK Data Protection regulations, requiring us to obtain cookie consent.

Marketing cookies

Occasionally we may want to use marketing cookies to help us improve the relevancy of an advertising campaign.

There are currently no marketing cookies on this site.

Your privacy

Please refer to our privacy notices for information about how we manage your information.