Cookie Policy

What is a cookie?

Our website uses cookies.  A cookie is a file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.

Cookies may be either "persistent" cookies or "session" cookies: a persistent cookie will be stored by a web browser and will remain valid until its set expiry date, unless deleted by the user before the expiry date; a session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.

Cookies do not typically contain any information that personally identifies a user, but personal information that we store about you may be linked to the information stored in and obtained from cookies.

We use both session and persistent cookies on our website.

Cookies we use

The names of the cookies that we use on our website, and the purposes for which they are used, are set out below:

  1. We use __unam to track the click stream activity of users e.g. amount of time a user spends on our website. This cookie only identifies a user if they have separately signed up with ShareThis for a ShareThis account and given them consent. This data is stored for 14 months.
  2. We use cc_cookie_accept to recognise whether a user has accepted the cookie message or not. This data is stored for 365 days.
  3. We use ASP.NET_SessionId to validate authenticated users sessions. This data is held only until the end of your session.
  4. We use ARRAffinityto administer the website in so far as it tells which server to handle website requests. This data is held until the end of your session.
  5. We use MemberLoggedIn to recognise whether a user is logged in or not. This data is stored until the end of your session.
  6. We use ai_session and ai_user to track users as they navigate the website predominately for infrastructure performance insights. This data is held for 1 day.
  7. We use DisplayName to personalise the website for each user and show their preferred name for Direct Debits. This data is held until the end of the user session.
  8. We use IDE, DSID,_ct_rmm to recognise when a user has of the website has seen or clicked on an advert displayed via DoubleClick. This data is held for 2 years from set/update.
  9. We use __cfduid to recognise individual clients behind a shared IP address and apply security settings on a per-client basis. This data is stored for 365 days.
  10. We use Facebook Pixels to track whether users of the website have come through Facebook or Instagram adverts. These Pixels may also record return visits, how you navigate the website and if you make a purchase or donation. We also may use this data and the personal data you have given us to target or re-target Facebook and Instagram adverts to you.
  11. We use Google Tag Manager to track whether users of the website have come through AdWord campaigns or social media campaigns using a google trackable link. All of our link data is anonymised. However, we may use data collected through Google Tag Manager to re-target ads to you or to target new ads to you in combination with personal data you have already provided to us.

Google Analytics

We use Google Analytics to analyse the use of our website. Our analytics service provider generates statistical and other information about website use by means of cookies.

The analytics cookies used by our website have the following names: [_ga, _gid, _gat, __utma, __utmt, __utmb, __utmc, __utmz and __utmv].

The information generated relating to our website is used to create reports about the use of our website.

Our analytics service provider's privacy policy is available at: http://www.google.com/policies/privacy/

Controlling cookies

Most browsers allow you to refuse to accept cookies, for example:

  1. In Internet Explorer (version 11) you can block cookies using the cookie handling override settings available by clicking "Tools", "Internet Options", "Privacy" and then "Advanced"
  2. In Firefox (version 47) you can block all cookies by clicking "Tools", "Options", "Privacy", selecting "Use custom settings for history" from the drop-down menu, and unticking "Accept cookies from sites"
  3. In Chrome (version 52), you can block all cookies by accessing the "Customise and control" menu, and clicking "Settings", "Show advanced settings" and "Content settings", and then selecting "Block sites from setting any data" under the "Cookies" heading

Blocking all cookies will have a negative impact upon the usability of many websites. If you block cookies, you will not be able to use all the features on our website.

You can delete cookies already stored on your computer, for example:

  1. In Internet Explorer (version 11), you must manually delete cookie files (you can find instructions for doing so at: http://windows.microsoft.com/en-gb/internet-explorer/delete-manage-cookies#ie=ie-11)
  2. In Firefox (version 47), you can delete cookies by clicking "Tools", "Options" and "Privacy", then selecting "Use custom settings for history" from the drop-down menu, clicking "Show Cookies", and then clicking "Remove All Cookies"
  3. In Chrome (version 52), you can delete all cookies by accessing the "Customise and control" menu, and clicking "Settings", "Show advanced settings" and "Clear browsing data", and then selecting "Cookies and other site and plug-in data" before clicking "Clear browsing data"

Deleting cookies will have a negative impact on the usability of many websites.


Your support changes lives - please donate today

Donate