Cookie Policy
The Evology Website uses cookies to distinguish you from other users of Our site. This helps Us to provide you with a good experience when you browse Our site and also allows Us to improve Our site.
A cookie is a small file of letters and numbers that We store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.
We use the following cookies:
- Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website, use a shopping cart or make use of e-billing services.
- Analytical/performance cookies. They allow Us to recognise and count the number of visitors and to see how visitors move around Our site when they are using it. This helps us to improve the way Our site works, for example, by ensuring that users are finding what they are looking for easily.
- Functionality cookies. These are used to recognise you when you return to Our site. This enables Us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).
Use of cookies on our website
Please see below a list of all cookies we use along with an explanation about them:
Necessary Cookies
| Name | Duration | Description |
| cookieyesID | 1 year | CookieYes sets this cookie as a unique identifier for visitors according to their consent. |
| cky-consent | 1 year | The cookie is set by CookieYes to remember the users’s consent settings so that the website recognizes the users the next time they visit. |
| cookieyes-necessary | 1 year | CookieYes sets this cookie to remember the consent of users for the use of cookies in the ‘Necessary’ category. |
| cookieyes-functional | 1 year | CookieYes sets this cookie to remember the consent of users for the use of cookies in the ‘Functional’ category. |
| cookieyes-analytics | 1 year | CookieYes sets this cookie to remember the consent of users for the use of cookies in the ‘Analytics’ category. |
| cookieyes-performance | 1 year | CookieYes sets this cookie to remember the consent of users for the use of cookies in the ‘Performance’ category. |
| cookieyes-advertisement | 1 year | CookieYes sets this cookie to remember the consent of users for the use of cookies in the ‘Advertisement’ category. |
| cky-action | 1 year | This cookie is set by CookieYes and is used to remember the action taken by the user. |
| cookieyes-other | 1 year | CookieYes sets this cookie to remember the consent of users for the use of cookies in the ‘Other’ category. |
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| __hssc | 30 mins | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __RequestVerificationToken | session | This cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks. |
| JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
Evology Parking App
| x-ms-cpim-trans | session | Used for tracking the transactions (number of authentication requests to Azure AD B2C) and the current transaction. |
| x-ms-cpim-cache:{id}_n | session | Used for maintaining the request state. |
| x-ms-cpim-csrf | session | Cross-Site Request Forgery token used for CRSF protection. |
| x-ms-cpim-sso:{Id} | session | Used for maintaining the SSO session. This cookie is set as persistent, when Keep Me Signed In is enabled. |
Functional Cookies
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| __hssc | 30 mins | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __RequestVerificationToken | session | This cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks. |
| JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
Analytical Cookies
| Name | Duration | Description |
| _ga | 1 year 1 month 4 days | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site’s analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website’s performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| _hjFirstSeen | 30 mins | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
| _hjAbsoluteSessionInProgress | 30 mins | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
| _gat_UA-* | 1 minute | Google Analytics sets this cookie for user behaviour tracking. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| __hstc | 5 months 27 days | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| _fbp | 3 months | Facebook sets this cookie to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising after visiting the website |
| _gcl_au | 3 months | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
| _hjSessionUser{site_id} | 1 year | A Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID |
| _hjSession_ | 30 minutes | The session cookie is a server-specific cookie that cannot be passed to any machine other than the one that generated the cookie. The session cookie allows the browser to re-identify itself to the single, unique server to which the client had previously authenticated. |
Performance cookies
| Name | Duration | Description |
| _gat | 1 minute | Google Universal Analytics sets this cookie to restrain request rate and thus limit data collection on high-traffic sites. |
Advertisement cookies
| Name | Duration | Description |
| fr | 3 months | Facebook sets this cookie to show relevant advertisements by tracking user behaviour across the web, on sites with Facebook pixel or Facebook social plugin. |
How to manage cookies
Managing your cookies is different depending on the web browser you are using. For full details on how to manage your cookies please follow the instructions from the web browser manufacture directly.
These links are to third party sites, over which we have no control. No liability can be claimed if they are inaccurate.
Please bear in mind that if you do this, certain personalised features of this website cannot be provided to you.