Legal
Cookie Policy
Rooetd: operated by Mauj Lo Roj Lo Ltd (trading as Rooetd). Last updated 17 August 2026 · Effective from 17 August 2026.
This page is about the small bits of data your browser (or, once it exists, our app) holds on to between visits: organised by category, so it’s easy to see what’s actually running.
A note on the app: when the Rooetd app launches, we’ll update this page (and any relevant privacy/permission information) to reflect the technologies actually used in the app; we won’t just assume they’re identical to the website’s.
The four categories, and where we stand on each
In short: functional cookies keep the site working and don’t need your consent; everything else only runs if you say yes (and right now that’s really just one marketing cookie and one first-party analytics cookie).
Cookies (and the local-storage equivalent) generally fall into four buckets. Here’s exactly where Rooetd sits today, honestly: not padded out with categories we don’t use yet.
Strictly necessary / functional
Cookies that make the site work as you’d expect. These don’t need your consent, because the site can’t function properly without them.
| Name | Purpose | Lifespan |
|---|---|---|
ro_consent | Remembers your cookie choice, so we don’t ask every visit. | 6 months |
ro_quiz_tripLocal storage | Saves your trip-quiz answers on your own device, so we can pre-fill your enquiry if you come back to finish it. Never leaves your device unless you submit the form. | Until you clear it, or finish/abandon the quiz |
Analytics
Cookies that help us understand how the site’s used. We do not currently use any third-party analytics tool, such as Google Analytics, or any equivalent. If we introduce one later, we’ll update this table and the consent mechanism before the technology goes live, not after.
We do run one first-party, non-essential session cookie of our own, used only for our own product insight; never shared with a third party:
| Name | Purpose | Lifespan |
|---|---|---|
ro_sid | Identifies your session so we can group your own on-site behavioural events together (for example, which map pins you view before saving one). Only set if you accept. | 1 day |
Marketing / attribution
Cookies that help us understand which channel brought you here.
| Name | Purpose | Lifespan |
|---|---|---|
ro_attr | Records which campaign, link, or search led you here, so we know which marketing is actually working. Goes only to us: never to an ad network, never sold, never shared for anyone else’s marketing, and never used to build an advertising profile of you. Only set once you’ve accepted. | 90 days |
Advertising
We do not currently use advertising pixels, retargeting, or ad-network tracking of any kind: nothing that follows you around the web after you leave. If that ever changes, we’ll update this table and the consent mechanism before anything goes live.
Third-party embedded content
In short: a technical audit of our codebase (17 August 2026) confirmed most of this was never actually a problem, and we’ve fixed the one thing that was.
Separately from cookies we set ourselves, some pages may embed content hosted by someone else; this is common, but it means that provider can receive technical data (like your IP address) or set its own cookie the moment the content loads, independently of anything above. This table is a record of what’s actually deployed today, checked directly against our codebase, not a list of things we might use someday.
| Technology | What loads, and when | Consent required? |
|---|---|---|
| Fonts (Cormorant Garamond, Inter) | Self-hosted from rooetd.com: no third-party contact at all. | No |
| Maps | No third-party mapping provider is used. Our interactive map is self-hosted, so nothing is contacted or set when it loads. | N/A |
| YouTube: video thumbnail | Self-hosted from rooetd.com: no request to Google, and no third-party contact at all, until you actively choose to play a video. | No: not a third-party contact |
| YouTube: video player | Only when you actively press play, an embedded player loads from youtube-nocookie.com. Once loaded, the player can set its own cookies and YouTube receives your IP address. | No consent gate needed to load the page; the player simply isn’t requested until you choose to play |
| Not currently embedded anywhere on our platforms. | N/A |
We also checked for the things people usually miss: Google Analytics, Google Tag Manager, Meta Pixel, Segment, Mixpanel, Hotjar, chat widgets (Intercom, Drift, Crisp, Zendesk), reCAPTCHA/hCaptcha, and error-tracking tools like Sentry. None of these are present anywhere on our platforms, confirmed by direct code review, not just by us saying so.
On Instagram: we don’t currently embed Instagram content anywhere on our platforms. If that changes, standard Instagram embeds can contact Meta’s servers and set cookies once they load; so we’ll run the same code-level check on them that we ran for everything else in this table, and update this row with confirmed, checked detail before any embed goes live, not after.
Opting out
In short: everything beyond strictly necessary is genuinely optional, and turning it off costs you little to nothing.
Anything outside "strictly necessary" is entirely optional, and we mean that. Be aware, though: rejecting cookies broadly could mean a feature like the quiz pre-fill doesn’t carry over between visits. Opting out of the marketing/attribution or analytics cookies costs you nothing functionally; it just means we can’t tell which channel sent you here, or group your on-site behaviour for our own product insight.
We’ll always be upfront, category by category, about which is which: never one vague "reject all" that quietly breaks something you didn’t expect.
How the consent banner works
In short: nothing non-essential loads until you choose, and rejecting is exactly as easy as accepting.
On your first visit, a banner offers two clear, equally-weighted choices: Accept and Reject. No dark patterns: rejecting is exactly as easy as accepting.
- We don’t set or allow any non-essential cookie before you’ve made that choice.
- Every cookie we do set exists to make your experience better or give you the full advantage of the site: not to build a profile of you for anyone else’s benefit.
- We remember your choice for 6 months, then ask again.
- You can change your mind at any time by clearing your browser’s cookies for this site, which will show the banner again. We don’t yet offer a standalone "cookie preferences" control separate from that; if that’s something you’d find useful, tell us at hello@rooetd.com.
Your browser controls too
In short: your browser can block cookies too, on top of anything you choose here.
Most browsers let you block or delete cookies directly: check the browser’s help menu. Blocking ro_consent itself just means we’ll ask again next visit.
Questions
hello@rooetd.com · datahandling@rooetd.com · +44 7447 793716
Drafted against PECR, as amended by the Data (Use and Access) Act 2025 (in force from 5 February 2026), and current ICO cookie guidance.
More on the site
See also our Privacy Policy, Terms & Conditions, Booking Protection, and our Travel Advice. Our Booking Conditions are the approved terms for a Rooetd package booking; Rooetd is currently operating on an enquiries-only basis, so see Booking Protection for what that means for your money today.