Cookies

What are cookies?

A cookie is a small text file that a website saves on your computer or mobile device when you visit the site.

Cookies enable the website to remember your actions and preferences (such as login, language) over a period of time, so you don't have to keep re-entering them whenever you come back to the site or browse from one page to another.

As is common practice with almost all professional websites, this site uses cookies.

This page describes what information they gather, how we use it and why we sometimes need to store these cookies. We will also share how you can prevent these cookies from being stored however this may downgrade or 'break' certain elements of the sites functionality.

For more general information on cookies see the Wikipedia article on HTTP Cookies.

How do we use cookies on the Bizoneo website?

The Bizoneo website runs on the Wandsoft content management system.

  1. The Wandsoft platform runs on Adobe ColdFusion Server
  1. Wandsoft cookies
    • Function: e-Commerce and Customer Relationship Management
    • Names: 
      • COOKPRIVACY: Kept forever - Anonymous - Used to track acknowledgement of cookie banner.
      • wsuser_id: Kept forever - Prevention of contact duplication. No tracking is performed.
      • WS_DEL, WS_DD, WS_DT, WS_SHOP, WS_C, WEZIK, : Anonymous - 3 hours from start of shopping. The Wandsoft shopping cart set these and they are deleted after the purchase is complete
      • LG: Anonymous - Kept forever. Website language.
      • TRZ: Anonymous - Kept forever. Affiliate / referral cookie
      • WSMPHONE: Anonymous - Desktop/Mobile preference when viewing the site on a mobile device
      • No opt-out is offered.
         
  2. Google Analytics
    • Function: User analytics. Google analytics are used to collect anonymised data on how visitors use webpages.
    • Name(s): _utma, _utmb, _utmc, _utmt, _utmz
      • __utma: 2 years from set/update. 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.

      • __utmt: 10 minutes. Used to throttle request rate.__utmb30 mins from set/updateUsed 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.

      • __utmc: End of browser session. 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.

      • __utmz: 6 months from set/update. 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.

      • __utmv: 2 years from set/update. 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.

      • http://www.google.com/intl/en/policies/privacy/

How to control cookies

You can control and/or delete cookies as you wish in your browser. You can delete all cookies that are already on your computer and you can set most browsers to prevent them from being placed. If you do this, however, you may have to manually adjust some preferences every time you visit our site and some services and functionalities may not work.