Cookies

What are cookies?

Every time you visit our website, it sends us a cookie. Warm, crumbly and delicious? Sadly not. This is a text file that tells us about your visit. The information is all anonymous, so we’re told about your computer, not you. And when the data comes to us it’s bulked together with information from all the other visitors to our site. Cookies tell us, for example, about traffic data, location data, device information, the date and time people visit and the pages they visit.

Most major websites use cookies. You can find out more at http://www.allaboutcookies.org/ or https://www.aboutcookies.org/.

How we use cookies on our website

To make the most of our website you should leave cookies turned on, otherwise you might not be able to see all of our lovely site.

Cookies help us:

customise what you see when you visit our site, and help us understand what would interest you
process any requests, applications or transactions
do our internal administration and analysis

Managing cookies

You can turn off cookies on most browsers. To find out how, use the help function.

Third party cookies

There are a few external companies that Tearfund works with who set cookies on our website. These cookies are mainly used for reporting and advertising so we can improve the way we communicate.

We use websites like Youtube and Vimeo to embed videos, and they may send you cookies too. We don’t control the setting of these cookies, so check those websites for more information.

Tearfund also uses companies like Facebook, HotJar and Google Analytics, which may use cookies. They may also use tracking pixels, which tell us how effective our adverts are.

You can opt out of Google's tracking cookies any time you want. Google uses cookies to match adverts with your preferences so they’re more relevant to you. If you don’t want to see adverts from us based on that information, you can use Google's Ad Personalisation Tool.

All information we get through Google's cookies is anonymous, it just helps us understand how people use our website and which pages are more popular. If you don’t want Google to include you in this information, you can install the Google Analytics Opt Out Tool.

You can also visit the Digital Advertising Alliance website to personalise your advertising preferences.

As some of these services may be based outside of the UK and the European Union, they might not fall under the jurisdiction of UK courts. If you’re worried about that, you can change your cookie settings (see above). Or for more information, visit https://ico.org.uk/

List of the main cookies used on our website

This is a list of the main cookies set by the Tearfund website, and what each is used for.

Name of cookie owner/service	Associated cookies	Description
Asp.net	aso.net_sessionId	This cookie enables essential functioning of our site and your secure use of it during your current visit only. This cookie is deleted when you close your browser.
Sitecore	SC_ANALYTICS_GLOBAL_COOKIE_, SC_ANALYTICS_GLOBAL_COOKIE_Main Site, SC_ANALYTICS_SESSION_COOKIE, SC_ANALYTICS_SESSION_COOKIE_Main Site	These cookies help us deliver personalised content to you and provide anonymous reports to us on how visitors use our site.
Cloudflare	_cfduid	Set by the CloudFlare service to identify trusted web traffic. It does not correspond to any user id in the web application, nor does the cookie store any personally identifiable information.
Tearfund	mainsite#lang	Set users preferred language version of the website.

Third Party Cookies set by Tearfund

We work with a number of third party suppliers who set cookies on our website to enable them to provide us with services. These cookies are mainly used for reporting and advertising purposes so that we can improve the way we communicate with our supporters and ensure the money we invest in online advertising is well spent.

More information about the main suppliers we use are listed below.

Name of cookie owner/service	Associated cookies	Description
Google Analytics	_utma, _utmb, _utmc, _utmt, _utmz, _dc_gtm_UA, _ga, _gat, _gid, collect, _utmli	_utma - Tracking Code that logs details about the visitor’s browser and computer. _utmb - Collects data on the number of times a user has visited the website as well as dates for the first and most recent visit. _utmc - Registers a timestamp with the exact time of when the user leaves the website. _utmt - Used to throttle the speed of requests to the server. _utmz - Collects data on where the user came from, what search engine was used, what link was clicked and what search time was used. dc_gtm_UA - Used by Google Tag Manager to control the loading of a Google Analytics script tag. _ga - Registers a unique ID that is used to generate statistical data on how the visitor uses the website. _gat - Used by Google Analytics to throttle request rate. _gid - Registers a unique ID that is used to generate statistical ata on how the visitor uses the website. Collect - Used to send data to Google Analytics about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels.
Google Adwords	ads/ga-audiences, ads/user-lists/	Used by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor’s online behaviour across websites.
Vimeo	Vuid	Collects data on the user’s visits to the website, such as which pages have been read.
Facebook	Fr	Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.
Youtube	GPS, PREF, VISITOR_INFO1_LIVE, YSC	GPS - Registers a unique ID on mobile devices to enable tracking based on geographical GPS location. PREF - Registers a unique ID that is used by Google to keep statistics of how the visitor uses Youtube videos across different websites. VISITOR_INFO1_LIVE - Tries to estimate the user’s bandwidth on pages with integrated YouTube videos. YSC - Registers a unique ID to keep statistics of what videos from YouTube the user has seen.
Google DoubleClick	IDE	Used by Google DoubleClick to register and report the website user’s actions after viewing or clicking one of the advertiser's ads with the purpose of measuring efficacy of an ad and to present targeted ads to the user.
Zopim	_zlcmid, zte	Saves a Zopim Live Chat ID that recognises a device between visits during a chat session.
Amazon Web Services	AWSALB	Manages web traffic and balances traffic load.
Adalyser	__adal_ca, __adal_cw, __adal_id	__adal_ca - Data stored: Traffic source / campaign data; Purpose: Store which advertising campaign drove a user to visit. __adal_cw - Data stored: Visit timestamp; Purpose: Tie back conversion events to earlier visits. __adal_id - Data stored: Device ID (generated); Purpose: Uniquely identify a device.