FUSE ASSURANCE SOLUTIONS LIMITED – COOKIE POLICY

 

WHAT DO COOKIES DO

Cookies collect anonymous data about how visitors use our site, which is then used to help improve the site. Example data collected includes the number of site visitors, where visitors come to the site from and pages visited.

WHAT ARE COOKIES

A cookie is like a memory for a computer, a cookie is a small file containing a string of characters that is sent to your computer when you visit a website. When you visit the site again, the cookie allows that site to recognise your browser. Cookies may store user preferences and other information. You can configure your browser to refuse all cookies or to indicate when a cookie is being sent. However, some website features or services may not function properly without cookies.

Cookies are incredibly useful – they allow modern websites to work the way people have come to expect with every increasing level of personalisation and rich interactive functionality.

HOW WE USE COOKIES

We collect information about your computer, including your IP address, operating system and browser type, for system administration and in order to create reports. This is statistical data about our users’ browsing actions and patterns and does not identify any individual.

The cookies in use on our site include Google Analytics. Google Analytics is a web analytics tool that helps website owners understand how visitors engage with their website. Google Analytics customers can view a variety of reports about how visitors interact with their website so that they can improve it.

Like many services, Google Analytics uses cookies to track visitor interactions as in our case, where they are used to collect information about how visitors use our site. We then use the information to compile reports and to help us improve our site.

Cookies contain information that is transferred to your computer’s hard drive. These cookies are used to store information, such as the time that the current visit occurred, whether the visitor has been to the site before and what site referred the visitor to the web page.

GOOGLE ANALYTICS COOKIES EXPLAINED

Google Analytics collects information anonymously. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen.
It reports website trends without identifying individual visitors. You can opt out of Google Analytics without affecting how you visit our site – for more information on opting out of being tracked by Google Analytics across all websites please visit Google page

Google Analytics supports three JavaScript libraries (tags) for measuring website usage: gtag.jsanalytics.js, and ga.js. The following sections describe how each use cookies.

gtag.js and analytics.js – 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, gtag.js and analytics.js set cookies on the highest level domain they can. 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 users to be tracked across subdomains without any extra configuration.

Note: gtag.js and analytics.js do not require setting cookies to transmit data to Google Analytics.

gtag.js and analytics.js set the following cookies:

Cookie NameExpiration TimeDescription
_ga2 yearsUsed to distinguish users.
_gid24 hoursUsed to distinguish users.
_gat1 minuteUsed to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.
AMP_TOKEN30 seconds to 1 yearContains 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_<property-id>90 daysContains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out.

ga.js – 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

By default, this library sets cookies on the domain specified in the document.host browser property and sets the cookie path to the root level (/).

This library sets the following cookies:

Cookie NameDefault Expiration TimeDescription
__utma2 years from set/updateUsed 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.
__utmt10 minutesUsed 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.
__utmcEnd of browser sessionNot 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.
__utmz6 months from set/updateStores 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.
__utmv2 years from set/updateUsed 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.

Customisation

The following methods can be used to customise how cookies are set:

Read the Tracking Multiple Domains guide to learn how to configure ga.js to measure user interaction across domains.

urchin.js – cookie usage

Historically, Google Analytics provided a JavaScript measurement library named urchin.js. When the newer ga.js library launched, developers were encouraged to migrate to the new library. For sites that have not completed the migration, urchin.js sets cookies identically to what is set in ga.js. Read the ga.js cookie usage section above for more details.

Overall, cookies help us provide you with a better website, by enabling us to monitor which pages you find useful and which you do not. A cookie in no way gives us access to your computer or any information about you, other than the data you choose to share with us.

OTHER TRACKING TECHNOLOGIES

Cookies are the most well-known and common type of web tracking technologies. However, many websites, advertisers, and analytic tools use other types of technologies to track users or monitor website performance. We also use Pixels (Web Beacons)

A web beacon, often referred to as a pixel tag, is a clear GIF or web bug, usually no more than 1-pixel x 1-pixel transparent image, that is placed on a website or in an email to monitor the behaviour of the user visiting the website or receiving the email. They are often used in combination with cookies.

Web beacons work by sending information along with the request to the web server with the image. For example, when the browser connects to a site with the web beacon, the browser requests the web server to download the image – included in this request can be details such as IP address, type of browser, time of access, or previously set cookies.

Sites generally use web beacons to understand how users travel on the site and use this information to give more personalised content or make browsing more efficient and easier.

If cookies are turned off, web beacons will not be able to track a user, however, they can still be used to account for anonymous visits.

We use several Facebook Pixels on our website, a Facebook pixel is an analytics tool that consists of a code that we can put on our website. The pixel fires to track site visitors. It collects data that helps us track conversions from Facebook ads, optimise ads, build targeted audiences for future ads, and remarket to people who have already taken action on our website.

ACCEPTING OR OPTING OUT OF COOKIES

You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but you can usually modify your browser setting to decline cookies if you prefer. This may prevent you from taking full advantage of the website. You will be prompted on your first visit to our website with a pop-up on screen alerting you, letting you know that we use cookies on this website at this point you have the choice to accept or decline cookies.

LINKS TO OTHER WEBSITES

Our website may contain links to other websites of interest. However, once you have used these links to leave our site, you should note that we do not have any control over that other website. Therefore, we cannot be responsible for the protection and privacy of any information which you provide whilst visiting such sites and such sites are not governed by this privacy statement. You should exercise caution and look at the privacy statement applicable to the website in question.

CHANGES TO THIS POLICY

We may change and update this policy. In that case, the ‘last updated’ date below will also change. Any changes to this policy will apply to you and your data immediately.

Last updated 30-05-19

LEGAL NOTICE

All rights reserved. Reproduction, adaptation, or translation without permission is prohibited except as allowed under the international copyright laws. All the text, graphics, design, content, and other works are the copyrighted works of Fuse Assurance Solutions Ltd