Cookie Policy

This site is operated by Whybrow, 2 De Grey Square, De Grey Road, Colchester, Essex CO4 5YQ. For more information about how we handle your personal data, please see our Privacy Policy.

www.whybrow.net (our website) uses cookies to distinguish you from other users of our website, gather website visitor data and allow us to optimise website content and marketing. These cookies help us to provide you with a good experience when you browse our website and also allow us to improve our site.

Use of cookies by Whybrow

Cookies are small text files that are placed on your computer by websites that you visit. They are widely used in order to make websites work, or work more efficiently, as well as to provide information to the owners of the site. Some cookies are set by us directly, while others are set by third parties (such as Google) who provide services that we use on our site. The tables below explain the cookies we use and why.

Necessary Cookies

Strictly necessary cookies enable the website to function properly. Without them, the site will either not work at all or will not work correctly. These cookies do not track any personal data of visitors and can be set without consent, in accordance with the GDPR directive.

Cookie Name Description Retention Period
propertyhive_recently_viewed Used by the PropertyHive plugin to store a list of properties recently viewed by the visitor, enabling the website to display personalised recently viewed listings. Session

 

Analytics Cookies

Analytics cookies are used to track website visitors and their user behaviour. This data is then used to improve the way the website works and in turn, used to improve user experience.

Cookie Name Description Retention Period
_ga ID used to identify users. 1 year
_ga_EXBV37Y7EF Used to identify and track an individual user session in Google Analytics 4. 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
_gat_* Used to set and get tracking data. 1 hour
_dc_gtm_ Used to monitor number of Google Analytics server requests. 1 minute
_gac_ Contains information related to marketing campaigns of the user. Shared with Google Ads when the Google Ads and Google Analytics accounts are linked together. 90 days
AMP_TOKEN Contains a token code 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
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 year
FPLC A cross-domain linker cookie hashed from the FPID cookie. Used for linking analytics data across domains. 20 hours
__utma ID used to identify users and sessions. 2 years
__utmb Used to distinguish new sessions and visits. Updated every time data is sent to the Google Analytics server. 30 minutes
__utmc Used with older versions of Google Analytics to distinguish between new sessions and visits at the end of a session. Session
__utmt Used to monitor number of Google Analytics server requests. 10 minutes
__utmv Contains custom information set by the web developer. 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
__utmz Contains information about the traffic source or campaign that directed the user to the website. 6 months

 

Marketing Cookies

Marketing and advertising cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user.

Cookie Name Description Retention Period
_gcl_au Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. 3 months
_gcl_dc Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. 3 months
__gsas Provides ad delivery or retargeting. 3 months
__gpi Collects information on user behaviour on multiple websites to optimise the relevance of advertisement on the website. 1 year
__gpi_optout Collects information on user behaviour on multiple websites to optimise the relevance of advertisement on the website. 13 months
GED_PLAYLIST_ACTIVITY Improves targeting and advertising within the website. Session
ACLK_DATA Used to help improve advertising. Targets advertising based on what’s relevant to a user, to improve reporting on campaign performance. 5 minutes

 

When you first visit our website, you will be presented with a cookie consent banner that allows you to accept or decline non-essential cookies. You can change your cookie preferences at any time by clicking the cookie settings icon displayed on our website.

How to refuse the use of cookies

You may also refuse the use of cookies by selecting the appropriate settings in your browser. However, if you do this you may lose some useful functionality such as personalisation and ‘keep me signed in’ and ‘remember me’ features, and if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our site. You can find more information about cookies, including more detail on how to refuse them in individual browsers, at www.allaboutcookies.org and www.youronlinechoices.eu.

Contact us

If you have any questions about our use of cookies or wish to exercise any of your data protection rights, please contact our Data Protection Officer:

Ewan Dodds, BSc FRICS (Data Protection Officer)
Whybrow
2 De Grey Square, De Grey Road
Colchester, Essex CO4 5YQ
Email: Info@whybrow.net
Tel: 01206 577667

This policy was last updated on 25 February 2026.

 

This field is for validation purposes and should be left unchanged.