Our cookie policy
Why do we use cookies?
Our website uses cookies, as almost all websites do, to help provide you with the best experience we can.
What are cookies?
Cookies are small text files that are placed on your computer or mobile phone when you browse websites.
We use cookies, which are issued by third party service providers that we continuously assess to make sure the data is secure. We collect these cookies in order to ensure that anything we do in our online advertising and campaigns are cost effective and relevant. We track how well our adverts perform and then analyse this data to make sure we can continue to make improvements.
What do cookies help us to do?
- Make our website work as you'd expect
- Remember your settings during and between visits
- Improve the speed/security of the site
- Allow you to share pages with social networks like Facebook
- Continuously improve our website for you
We do NOT use cookies to:
- Collect any personally identifiable information (without your express permission)
- Collect any sensitive information (without your express permission)
- Pass personally identifiable data to third parties
- Pay sales commissions
You can learn more about all the cookies we use below.
First party cookies
This site uses cookies in several places – we’ve listed each of them below with more details about why we use them and how long they will last.
Third party cookies
We use a number of suppliers who may also set cookies on their websites’ on its behalf. This site does not control the dissemination of these cookies. You should check the third party websites for more information about these.
Cookie provider: The Wildlife Trusts
Purpose: Used by the website to remember cookie preferences.
Cookies: cookie-agreed expires in 100 days. MCPopupClosed expires on site entry.
Cookie provider:SESSxxxID
Purpose: Authentication session to prevent having to login multiple times in one browser session. This is only set if you authenticate via the site. This may happen if you purchase items from the shop or make use of our commenting.
Cookies: A unique id that ties the current session to a database settings table. Expires in one week.
Cookie provider: has_js
Purpose: This helps the website understand browser Javascript functionality.
Cookies: An on/off flag that denotes whether or not the browser supports Javascript. Expires on site exit.
Cookie provider: Online forms
Purpose: This cookie is essential for our webforms to operate. It is set only for those people using the form, and prevents the browser from storing the information you enter. This cookie is deleted when you close your browser.
Cookies: NO_CACHE
Cookie provider: Facebook
Purpose: Used by Facebook for sharing content, conversion tracking, optimisation, creating audiences for Facebook Ads and marketing.
Cookies: _fbp, _fbc, fr, lu, xs, c_user, m_user, pl, dbln, aks, aksb, sfau, ick, csm, s, datr, sb, fr, oo, ddid, locale, js_ver, rc, campaign_click_url, wd, usida, presence
Provider policy: Facebook
Cookie provider: Paypal
Purpose: Used to support payment services.
Cookies: AKDC, LANG, X-PP-SILOVER, X-PP-L7, akavpau_ppsd, enforce_policy, nsid, ts, ts_c, tsrce, x-csrf-jwt, x-pp-s, 7_az
Provider policy: Paypal
Cookie provider: Vimeo
Purpose: Used to embed videos from Vimeo using cookies that we consider essential to the video player experience. Does not use third-party analytics or advertising cookies.
Cookies: player, vuid, continuous_play_v3
Provider policy: Vimeo
Cookie provider: Eventbrite
Purpose: Used to deliver event booking services and content tailored to the user’s interests.
Cookies: csrftoken, AS, eblang, G, guest, session, SP, SS, tcm, ebGAClientId, stableld, lux_uid, SERVERID
Provider policy: Eventbrite
Cookie provider: New Relic
Purpose: Anonymously maintains a user’s browsing session on the website to allow us to monitor and troubleshoot website performance.
Cookies: JSESSIONID
Provider policy: New Relic
Cookie provider: Engaging Networks
Purpose: Maintains a user’s browsing session on the website when participating with our online campaigning activities.
Cookies: en_sessionId
Provider policy: Engaging Networks
Cookie provider: Google
Purpose: Used to understand website usage including how users found and explored our site and how their experience can be enhanced. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.
Google also provides campaign tracking, advertising and website functionality services.
We may remarket to you via the collection, sharing, and use of online user data for Google Ad personalization. This allows us to advertise to you according to your interests, providing an improved experience for you. Google considers ads to be personalized when they are based on previously collected or historical data to determine or influence ad selection, including your previous search queries, activity, visits to sites or apps, demographic information, or location. Specifically, this would include, for example: demographic targeting, interest category targeting, remarketing,
You can update your Google Ad settings at My Ad centre.
Google signals: These are session data from sites and apps that Google associates with users who have signed in to their Google accounts, and who have turned on Ads Personalization. This association of data with these signed-in users is used to enable cross-device reporting, cross-device remarketing, and cross-device conversion export to Google Ads. It is used to provide aggregated and anonymised insights into our users’ cross device behaviours. Such data may be accessed and/or deleted by you via My Activity
Cookies: IDE, _ga, _ga_*, _gat, _gat_*, _gac_, _gat_UA-xxxxxxx-xx, _gid, __utma, __utmt, __utmb, __utmc, __utmz, __utmv, __utmx, __utmxx, _dc_gtm_, AMP_TOKEN, FPAU, FPID, FPLC, __gsas, __gpi, __gpi_optout, GED_PLAYLIST_ACTIVITY, ACLK_DATA, _gcl_au, _gcl_dc
Provider policy: Google
Cookie provider: Stripe
Purpose: Used for making card transactions on the website. Provided by Stripe.com which allows online transactions without storing any credit card information.
Cookies: __stripe_mid, __stripe_sid, m
Provider policy: Stripe
Cookie provider: Hotjar
Purpose: Anonymously analyses how the website is being used to improve the user experience.
Cookies: _hjSessionUser_xxxxxx, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjIncludedInSessionSample, _hjSession_xxxxxxx, _hjIncludedInPageviewSample
Cookie provider: Disqus
Purpose: We embed commenting from Disqus.
Cookies: __jid, disqus_unique
Provider policy: Disqus
Cookie provider: Ecwid (Lightspeed)
Purpose: We embed our online shop from Ecwid.
Cookies: PSecwid__*', ec-*, PSdispatcher__*, PSec__*, PSreloadTriggerPSreloadTrigger, PSreloadTriggerPSreloadTrigger_expire, PSlast__*, ec_storefront_ab_test, PSorder__result__{store_id}PSorderResult, __eca_s_id_, __eca_v_id_, PSdispatcher__,
Provider policy: Lightspeed
Cookie provider: MailChimp
Purpose: MailChimp automatically places single pixel gifs, also known as web beacons, in bulk email sent by Cumbria Wildlife Trust. These are tiny graphic files that contain unique identifiers that enable Cumbria Wildlife Trust to recognize when their subscribers have opened an email or clicked certain links. These technologies record each subscribers email address, IP address, date, and time associated with each open and click for a campaign. MailChimp uses this data to create reports for Cumbria Wildlife Trust about how an email campaign performed and what actions subscribers took.
Provider policy: Mailchimp
Cookie provider: X
Purpose: We may implement an X website tag to collect conversion tracking data.
Provider policy: X privacy policy
Cookie provider: Wufoo (by Survey Monkey)
Purpose: This is a session ID cookie used to identify unique visitors completing forms on our site. If you have your browser set to reject cookies the forms may not work correctly.
Cookies: wildlifetrusts40, ep201, ep202
Provider policy: Survey Monkey
Cookie provider: YouTube
Purpose: We embed videos from YouTube. This may set cookies on your computer, particularly if you are logged into a Google or YouTube account.
Cookies: GPS, VISITOR_INFO1_LIVE, PREF, YSC, DEVICE_INFO, LOGIN_INFO, VISITOR_PRIVACY_METADATA
Provider policy: YouTube
Cookie provider: ASP.net
Purpose: To identify the user's session on the server. The session being an area on the server which can be used to store session state in between http requests.
Cookies: ASP.NET_SessionId
Provider policy: Microsoft
Cookie provider: Akamai Botmanager
Purpose: This cookie is used to analyse traffic to determine if it is automated traffic generated by IT systems or a human user.
Cookies: _abck
Provider policy: Akamai Botmanager
Cookie provider: Amazon web services
Purpose: These cookies enable us to allocate server traffic to make the user experience
as smooth as possible. A so-called load balancer is used to determine which server currently has the best availability. The information generated cannot identify you as an individual.
Used to collect anonymised information about how which web pages are visited, how long users spend on pages and what users search for.
Anonymous metrics validation token. Anonymous cookie for privacy regulations
Cookies: AWSALB, AWSALBCORS, AWSELBCORS, AWSELB, AWSALBTGCORS, AWSALBTG, aws-csds-token, aws_lang, aws-target-visitor-id, aws-priv
Provider policy: Amazon web services
How do I manage my cookie preferences?
Most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.allaboutcookies.org.
How do I opt out of being tracked by Google Analytics?
To opt out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout
What other data do we use?
Email data
We also use email data for tracking purposes.
Hashed data
What is Hashed data?
Hashed data is used to create targeted advertising for our fundraising and campaigning activities on social media and web platforms.
What does Hashing mean?
Hashing means that data such as email addresses are turned into unreadable codes for security and privacy during data transfer.
How long do we keep Hashed data?
We delete the hashed data after a short period of time and it's not used for any other purpose.
Why do we use Hashed data?
It helps us reach and inspire new people to take meaningful action for nature and to create an inclusive society where nature matters. It's both cost-effective and helps us grow support for Cumbria's wildlife.