COOKIE POLICY
COOKIES AND OTHER ONLINE IDENTIFIERS
Our websites: costpocket.com, wizard.finance and costpocket.ee like most others, uses cookies to collect information. This Policy describes which personal data will be processed during your visit and use of CostPocket website.
Cookies are data files containing small amounts of information which are placed on your computer or other devices through your web browser when you visit our website. This is then sent back to our website by your browser and is used to “remember” your computer or device.
To make full use of our website and book services online, cookies need to be enabled on your web browser. If you do not accept cookies, or you decide to disable cookies on your computer later, then certain features on our website may not work as intended. You will still be able to browse our website, but your user experience may suffer.
We also use other online identifiers, which are data files containing small amounts of information similar to cookies. However, instead of saving these data files to your computer or other device through your web browser, these data files are saved on CostPocket’s servers.
HOW DO WE USE COOKIES AND OTHER ONLINE IDENTIFIERS?
Generally, we use cookies and other online identifiers to:
- to recognise customers and understand and facilitate their browsing and order behaviour
- to complete subscriptions and orders and fulfil transactions
- for technical purposes relating to the operation of our website and navigation
- to improve our website and application and your experience ordering services online
- to provide you with personalised content and targeted updates
- to meet our contractual obligations to third parties and manage the relationship with our partners.
WE COLLECT THE FOLLOWING INFORMATION
Some cookies collect information about browsing and order behaviour when you visit our website. This includes information about pages viewed, orders/ subscriptions placed, documents uploaded and your journey around a website.
Mandatory cookies:
Cookie Name | Expiration Time | Description |
---|
__zlcstore | Persistent | Zendesk chat, user input cookie, CRITERION B |
__zlcmid | 1 year | Zendesk chat, user input cookie, CRITERION B |
__cfduid | 1 year | CloudFlare. Load balancing, CRITERION A |
_gcl_au | 90 days | Google Analytics |
_ga | 1 year | Used to distinguish users. |
_gid | 24 hours | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_. |
AMP_TOKEN | 30 seconds to 1 year | 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. |
_gac_ | 90 days | Contains campaign related information for the user. |
_fbp | 90 days | Facebook Advertising |
fr | 90 days | Facebook Advertising |
Non-essential cookies. Added on consent:
Cookie Name | Expiration Time | Description |
---|
cookies | localStorage | Set to 'accepted' on consenting |
_hjid | Session | Hotjar id |
_hjRecordingLastActivity | Session | This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). |
_hjTLDTest | Session | When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. |
_hjIncludedInPageviewSample | 30 minutes | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. |
_hjIncludedInSessionSample | 30 minutes | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit. |
_hjAbsoluteSessionInProgress | 30 minutes | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
MANAGING AND/ OR DISABLING COOKIES
You have different options to manage the cookies on your computer or device.
You can change your browser settings to prevent cookies from being accepted. If you want to disable cookies you need to change your website browser settings. This will depend on the browser you use and your browser’s 'help' menu should tell you how to disable cookies or change your cookie settings.
You can also delete cookies stored in your browser by using the functions in your browser. This will not disable cookies or prevent your browser from collecting them in the future. Deleting cookies on one browser or one device does not automatically clear them on another.
Depending on which cookies you disable, the website may not operate properly if cookies are not accepted. However, you will still be able to browse around our website, although some functions will not be available, for example, you will not be able to order our services, set up a new account or access an existing one.
POLICY UPDATES
This Policy was last updated in 25. Aug 2020.