Cookie Notice
- Home
- Cookie Notice
Introduction
To make our website and applications work properly and to provide you with the most relevant services, we use small data files which are placed on your device. This notice provides you with information about cookies and how to control them for this site and our applications.
What is a cookie?
A ‘cookie’ is a small text file that is stored on a user’s computer or mobile device when you visit a website. Cookies are then sent back to the originating site on each subsequent visit, or to another website that recognises that cookie. Cookies are useful because they allow a website to identify a user’s device, understand how people use our site and applications and which pages are most popular to enable us to serve our site visitors and application users well.
Cookies perform many functions, like letting you navigate between pages efficiently, remembering your preferences, and generally improving your experience with our services.
What cookies do we use?
We currently use cookies for Google Analytics on our website and for the live chat functionality (LivePerson Software) on our website.
Cookies used by the LivePerson software
Monitoring Cookies
| Cookie Type | Description | Storage |
| LPVID | Visitor ID as identified in LiveEngage. Identifies a browser if cookie is not deleted. | 1st party persistent. Fallback to sessionStorage per Tab. Path: parent domain /. |
| LPSID-SiteID | Current active (or last) monitoring session. | 1st party session cookie. Fallback to sessionStorage per Tab. Path: parent domain /. |
| LPSessionID | Current active (or last) monitoring session. | 3rd party HTTP only session cookie. Path: LivePerson parent domain /. |
| LPVisitorID | Visitor ID as identified in LivePerson. Identifies a browser as long as cookie is not deleted. | 3rd party HTTP only persistent. Path: LivePerson parent domain /. |
| lpLastVisit- | Last visit timestamp | localStorage. Duration: forever |
| lpTabId | Tab identifier | sessionStorage. Duration: session - same tab and domain only |
| lpPmCalleeDfs | For cross domain communication logic | sessionStorage. Duration: session - same tab and domain only |
Conversation Cookies
| Cookie Type | Description | Storage |
| LPCID-SiteId | Token for retrieving conversation data in the client only. | First party session cookie. No fallbacks. Path: parent domain /. |
| LPCKEY-SiteId | Token for retrieving conversation data in the client only. | First party session cookie. No fallbacks. Path: parent domain /. |
| LivePersonID | LivePerson chat identifier. Note: We do not currently use this data although we do store it. | Third party persistent cookie. Path: LivePerson parent domain / Note: We do not currently use this data although we do store it. |
| Storage_expiration-SiteId | timestamp for last storage usage (used for secure storage logic) | SecureStorage. Duration: 1 day |
| lpStrMap | manages storages keys (used for secure storage logic) | SecureStorage. Duration: 1 day |
|
| Handles window UI states between tabs. | SecureStorage. Duration: 1 day |
| UIConf | Stores conversation settings (features, logic etc.) | SecureStorage. Duration: 1 day |
|
| stores chat services locations | SecureStorage. Duration: 1 day |
| lpMessaging- | Stores the JWT token and authentication code in messaging scenarios for messaging window recovery on navigation and cross tabs | SecureStorage. Duration: 1 day |
| -lpuw | session state | SecureStorage. Duration: 1 day |
Cookie usage within Google Analytics
Google Analytics uses 3 Javascript libraries to measure website usage: gtag.js, analytics.js, and ga.js.
gtag.js and analytics.js cookies and cookie usage
The analytics.js JavaScript library is part of Universal Analytics and uses first-party cookies to:
- Distinguish unique users
- Throttle the request rate
When using the recommended JavaScript snippet, cookies are set at the highest possible domain level. For example, if your website address is blog.example.co.uk, analytics.js will set the cookie domain to .example.co.uk. Setting cookies on the highest-level domain possible allows measurement to occur across subdomains without any extra configuration.
| Cookie Type | Description | Storage |
| _ga | Used to distinguish users. | 2 years |
| _gid | Used to distinguish users. | 24 hours |
| _gat | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. | 1 minute |
| AMP_TOKEN | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. | 30 seconds to 1 year |
| _gac_<PROPERTY-ID> | Contains campaign related information for the user. | 90 days |
ga.js cookies and cookie usage
ga.js cookies and cookie usage
The ga.js JavaScript library uses first-party cookies to:
- Determine which domain to measure
- Distinguish unique users
- Throttle the request rate
- Remember the number and time of previous visits
- Remember traffic source information
- Determine the start and end of a session
- Remember the value of visitor-level custom variables
| Cookie Type | Description | Storage |
| __utma | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. | 2 years from set/update |
| __utmt | Used to throttle request rate. | 10 minutes |
| __utmb | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. | 30 mins from set/update |
| __utmc | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. | End of browser session |
| __utmz | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. | 6 months from set/update |
| __utmv | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. | 2 years from set/update |
Required cookies
Required cookies are those cookies necessary for the website or application to function and cannot be turned off in our systems. These cookies are usually only set in response to actions made by you that are, primarily, a request for services. That includes setting your preferences, logging in to our applications or completing forms. You can set your browser to block these cookies, but if you do, some parts of our services will not work.
Performance cookies
Performance cookies allow us to count visits to our site and determine traffic sources so we can measure and improve the performance of our website and services. These cookies allow us to gauge the popularity of pages and how visitors navigate through our services. The information collected within these cookies is used by us to analyse trends, administer our site, track user’s movements around our site and gather demographic information about our user base as a whole. We may receive reports based upon these technologies on an individual or aggregated basis.
Third party website cookies
When using our website, you may be directed to other websites. Those websites may use their own cookies. We do not have control over the placement of cookies by other websites you visit, even if our site directs you to theirs.
How to control and delete cookies
Many of the cookies used on our website and through emails can be enabled or disabled by disabling the cookies through your browser. To disable cookies through your browser, follow the instructions usually located within the “Help,” “Tools” or “Edit” menus in your browser. Please note that disabling a cookie or category of cookies does not delete an existing cookie from your browser unless you delete it manually through your browser function.
Browsing session duration
Some cookies are intended to expire at the end of a browsing session. A browsing session typically ends when you close the browser window, but this behaviour may vary depending on which browser and your browser preferences. In Chrome, for example, the “Continue where you left off” option for the “On startup” setting will prevent session cookies from being deleted, thereby extending your sessions indefinitely.
Questions?
For questions or concerns regarding our cookie usage, please email us at CompanySecretary@ewosa.com.au.