eola - Cookie Policy

Overview - the key information you should be aware of

  1. Who we are: We are eola Ltd, a booking and management platform for experience providers, and the operator of the eola marketplace, through which customers can find and book outdoor experiences. If you need it, our company number is 10810774 and our registered office is Sas House Friarswood, Chipperfield Road, Kings Langley, Hertfordshire, United Kingdom, WD4 9JB. All references in this policy to "eola", "our", "us" or "we" refer to eola Ltd. All references in this policy to "our website" refer to the website owned by eola at eola.co and all of its subdomains.

  2. What this policy is for: This cookie policy explains what cookies and similar technologies we place on your device when you use our website, what each of them does, how long they last, and how you can control them. It sits alongside our privacy policy, which explains more broadly how we collect and use your personal information and what rights you have in relation to it.

  3. Who this policy applies to: This policy applies to visitors to our website, enthusiasts (people who book activities through our website), and instructors and other contacts at activity centres that partner with us.

    Please note that some of the cookies described in section 6 are chosen and configured by the activity provider whose booking pages you are using, not by us. Where that is the case, the activity provider determines why those cookies are used, and their own cookie and privacy policies apply to them.

  4. What this policy contains: You can click on the links below to find out more:

  1. What cookies and similar technologies are

    1. A cookie is a small text file that a website asks your browser to store on your device. When you return to that website, your browser sends the cookie back, which allows the website to recognise your device and remember things about your previous visit.

    2. Cookies set by the website you are visiting are called first-party cookies. Cookies set by another organisation whose content or services are embedded in that website - for example an analytics provider or a payment provider - are called third-party cookies.

    3. Session cookies are deleted when you close your browser. Persistent cookies stay on your device until they expire or you delete them. Where a cookie is persistent, we have set out below how long it lasts.

    4. Some of the technologies described in this policy are not strictly cookies but work in a comparable way, including tracking pixels, web beacons and browser storage. We refer to all of them as "cookies" in this policy for simplicity.

  2. Strictly necessary cookies

    These cookies are required for our website to work. They enable core functions such as keeping you signed in, keeping your basket intact while you book, and protecting your account and forms from misuse. Without them, services you have asked for cannot be provided, so they cannot be switched off through our website. You can still block them in your browser, but parts of our website will not work if you do.

    1. Session cookie (name beginning "_eola_session") - identifies your browsing session so that we can keep you signed in and protect forms against cross-site request forgery. This cookie is shared across eola.co and its subdomains so that your session continues to work as you move between our marketplace, booking widget and business dashboard. It is a session cookie and is deleted when you close your browser.

    2. Sign-in cookies (names beginning "remember_") - set only if you choose the "remember me" option when signing in, so that you do not have to sign in again on your next visit. There is a separate cookie for each type of account, for example enthusiast, instructor and point-of-sale device. These cookies last for as long as the remember period on your account, and are removed when you sign out.

    3. Basket storage (a key ending "-basket") - holds the reference number of your basket, so that the items you have chosen are still there if you leave our booking pages and come back. This is what actually keeps your basket intact, and without it you would lose your selections. There is a separate entry for each activity provider whose booking pages you use, and each one is held in your browser's storage for 72 hours before it expires.

  3. Functional and preference cookies

    These cookies remember choices you have made and small details about how you use our website, so that we can give you a more consistent experience. They are not required for our website to work, but blocking them means you may have to repeat certain choices.

    1. last_outlet_visited - remembers which activity centre you were last working in, so that we can take you back to the right dashboard when you next sign in. This cookie is only set for instructors and other business users, and its contents are encrypted.

    2. collapsed_sidebar - remembers whether you have collapsed the navigation sidebar in the business dashboard.

    3. fontsLoaded - records that our fonts have already been downloaded by your browser, so that pages render without text flickering on later visits.

    4. referral_code - records a referral code where you have arrived at our website through a referral link, so that the referral can be credited to the right partner if you go on to make a booking. This cookie lasts for 12 hours.

  4. Analytics, testing and advertising cookies

    1. We use analytics to understand how our website is used - for example which pages are visited, how people move through the booking process, and where errors occur - so that we can fix problems and improve the service. We use testing technologies to compare different versions of our pages so that we can see which works better. We use advertising technologies to measure whether our own marketing is working.

    2. Google Analytics and Google Tag Manager. We use Google Tag Manager to load Google Analytics, which sets cookies (with names beginning "_ga") to distinguish visitors and sessions and to measure how our website is used. These cookies last up to two years. Google Tag Manager itself does not set analytics cookies, but it is the mechanism through which the tags described in this section are loaded.

    3. Google Ads. Where we are running paid marketing campaigns, Google sets cookies that allow us to see whether a visit that began with one of our adverts resulted in a booking, and allow Google to build advertising audiences. These cookies last up to two years.

    4. You can find out more about how Google uses information from sites that use its services at policies.google.com/technologies/partner-sites and you can opt out of Google Analytics across all websites using the browser add-on at tools.google.com/dlpage/gaoptout .

    5. Statsig. We use Statsig to run A/B tests on our marketplace and booking pages. An A/B test means showing different versions of a page or booking step to different visitors, so that we can measure which version works better and then improve the one everybody sees. To do this, Statsig stores a randomly generated identifier and the test variations you have been assigned using your browser's storage, so that you keep seeing the same version on later visits and are not counted twice. We do not send your name, email address or account details to Statsig, and we do not use it to build advertising audiences or to track you across other websites.

    6. Statsig explains how it handles information in its own policies at statsig.com/privacy .

    7. Cloudflare Web Analytics. We also use Cloudflare Web Analytics to measure page performance and traffic levels. Cloudflare has designed this product not to use cookies and not to track visitors across websites or over time, so it does not store anything on your device.

  5. Marketing attribution storage

    1. When you arrive at our marketplace or booking pages, we record where you came from, so that we can understand which of our own marketing brings people to us and so that a partner or campaign can be credited for a booking it introduced. Unlike the items in section 4 , this uses our own first-party browser storage rather than cookies, and the information stays with us - it is not shared with advertising networks.

    2. We store the following on your device:

      • basket-source-first-visit - the first visit that brought you to us, recording the website that referred you, any campaign tags in the link you followed (for example utm_source, utm_medium and utm_campaign), the page you landed on, and the date and time of the visit.

      • basket-source-latest-visit - the most recent such visit, recording the same details. This lets us tell the difference between how you first found us and what brought you back.

      • basket-source-session-visit-captured - a marker recording that we have already captured a visit during your current browsing session, so that moving between pages does not overwrite it. This is deleted when you close your browser.

      • A marketplace referral key (ending "-marketplace-referal") - where you reached an activity provider's booking pages through the eola marketplace or one of our partner marketplaces, this records which marketplace sent you, so that any resulting booking is recorded as coming through that marketplace rather than as a direct booking. There is a separate entry for each provider, and each one expires after 3 hours.

    3. The two visit records expire three months after the most recent visit we recorded, and are deleted automatically the next time we look for them after that. Moving between pages on our own website does not replace them, unless you have arrived through a link carrying campaign tags.

    4. If you add something to your basket, these details are attached to that basket so that the resulting booking can be attributed to the right source. They are not used to build advertising audiences or to track you across other websites.

  6. Cookies set by activity providers

    1. Many of the booking pages on our website are operated by us on behalf of an activity centre or instructor. Those activity providers can choose to add their own tracking to their booking pages so that they can measure their own marketing. Where they have done so, the following cookies may be set in addition to ours:

      • Meta (Facebook) Pixel - where the activity provider has supplied a Meta Pixel ID. Meta sets cookies that allow the provider to measure the performance of their advertising on Facebook and Instagram and to build advertising audiences.

      • The activity provider's own Google Analytics property - where the activity provider has supplied a Google Analytics measurement ID. This sets the Google Analytics cookies described in section 4 , but reports to the activity provider's own account rather than ours.

    2. For these cookies, the activity provider decides why the information is collected and how it is used, and is responsible for telling you about them. We enable the facility at their request. If you want to know how a particular activity provider uses this information, or you want to exercise your rights in relation to it, please contact that provider directly, or contact us using the details in section 10 and we will help put you in touch.

  7. Payment and fraud prevention cookies

    1. We use Stripe to process card payments. When you reach a payment page, Stripe loads its own payment components and sets cookies that are necessary to process your payment securely and to detect and prevent fraudulent transactions. These cookies are set by Stripe, and Stripe uses the information for its own fraud prevention purposes as well as on our behalf.

    2. Stripe explains its use of cookies in its own policies at stripe.com/cookies-policy/legal . Because these cookies are needed to take payment, you will not be able to complete a booking that requires payment if you block them.

  8. How to control and delete cookies

    1. All modern browsers let you see which cookies are stored on your device, delete them individually or all at once, and block cookies from being set in future - either for all websites or for particular websites. These controls are usually found in your browser's settings under a heading such as "Privacy", "Cookies" or "Site data". Your browser's help pages will explain how to do this on your device.

    2. The same controls also cover the browser storage described in section 4 and section 5 , although your browser may list it separately from cookies under a heading such as "Site data" or "Local storage". Clearing site data for our website will remove it.

    3. Please remember that the cookies in section 2 are needed for our website to function and the cookies in section 7 are needed to take payment. If you block or delete them, you may not be able to sign in, keep a basket, or complete a booking.

    4. Most browsers also offer a "Do Not Track" setting. There is currently no agreed industry standard for how websites should respond to it, so we do not act on it. If you want to limit analytics and advertising cookies, please use the browser controls and opt-out tools described above instead.

    5. To opt out of interest-based advertising from participating companies more generally, you can use the tools at youronlinechoices.com .

  9. Changes to this cookie policy

    We may update this cookie policy from time to time, for example if we start using a new provider or stop using an existing one. Any changes we make will be posted on this page. Please check back frequently to see any updates or changes.

  10. Further questions and how to make a complaint

    1. If you have any queries or complaints about our use of cookies, or if you wish to exercise any of your rights in relation to your personal information, please contact our Data Protection Officer on help@eola.co. We will investigate and attempt to resolve any such complaint or dispute.

    2. You may also make a complaint to the Information Commissioner's Office, or the data protection regulator in the country where you usually live or work, or where an alleged infringement of applicable data protection laws has taken place. Alternatively, you may seek a remedy through the courts if you believe your rights have been breached.

The practices described in this cookie policy are current as of August 2026.