Cookie Policy

Effective Date: September 23, 2026

1. What a cookie policy usually lists

Most cookie policies sort cookies into four groups. Here is that list, honestly filled in for this site.

• Strictly necessary cookies: none for visitors. There is no login, no basket and no booking session to carry between pages. The only exception is the staff desk console, which sets a signed session cookie for signed-in staff and nobody else.
• Functional cookies: none. The preferences this site remembers are described in section 2, and they are not cookies.
• Analytics cookies: yes, from two services. Google Analytics sets _ga and _ga_* (up to two years) and Microsoft Clarity sets _clck (one year) and _clsk (one day). Clarity records session replays and builds heatmaps of how visitors move through the page, with strict masking on (all text and anything you type is replaced by placeholders before it leaves your browser). All three tags are loaded through one Google Tag Manager container (gtm.js from googletagmanager.com, which sets no cookies of its own); there is no Plausible and no Fathom. Clarity’s collection servers on clarity.ms and bing.com may also set Microsoft’s own third-party cookies (MUID, CLID, ANONCHK, MR, SM; MUID for up to a year), which most browsers now block by default.
• Advertising and marketing cookies: two, from one source. The Meta Pixel sets a first-party cookie called _fbp (and _fbc when you arrive through a link from Facebook or Instagram, an ad or otherwise) that lasts 90 days, so Meta can tell whether one of our ads led to this visit, and so we can show a reminder ad to people who have visited this site or one of our property sites. Section 3 says exactly what Meta receives and section 4 how to switch it off.

A cookie notice appears on your first visit. It records your choice in your browser (local storage, not a cookie) so it does not ask again. Choosing Reject All stops Google Analytics, Microsoft Clarity and the Meta Pixel from loading on every later page view; choosing Accept All lets them load. To change your mind, clear this site's data in your browser and the notice appears again.

2. What is stored on your device, and for how long

This site has an accessibility panel. If you change any of those settings, the choice is saved so the site does not reset itself on the next page. The eight tf- values below, and the site_cookie_consent value the notice writes, are held in your browser’s local storage, not in a cookie, and are never transmitted to us or to anyone else. The items after them are real cookies, set by Google Analytics, Microsoft Clarity and the Meta Pixel, and those services read them (section 3).

• tf-theme — light or dark appearance
• tf-font-size — your chosen text size
• tf-high-contrast — high contrast mode on or off
• tf-reduce-motion — reduced motion on or off
• tf-reading-guide — reading guide on or off
• tf-link-highlight — link highlighting on or off
• tf-pwa-dismissed-tfrooms — set only if you dismiss the “Install this site as an app” offer, so it is not shown again
• tf-office-v1: a copy of the office hours and holiday closures last read from tfrooms.com, so the office clock keeps working when that read fails; it holds nothing about you and is never sent anywhere
• _ga and _ga_* — set by Google Analytics: a random visitor identifier and the current visit, kept for up to two years
• _clck and _clsk — set by Microsoft Clarity: a visitor identifier (one year) and the current session (one day)
• _fbp — set by the Meta Pixel: a random browser identifier, kept for 90 days
• _fbc — set by the Meta Pixel only when you arrive through a Facebook or Instagram link that carries a click identifier (fbclid): that identifier, kept for 90 days

Duration: the local-storage values have no expiry date, because no server sets one; each stays until you change the setting back or clear your browser’s site data for this domain. The Google Analytics cookies expire two years after they were last refreshed, Clarity’s after one year and one day respectively, and the two Meta cookies after 90 days; none of them is set at all when your browser sends the signals described in section 4 or when you chose Reject All.

3. Third parties

Microsoft Clarity (session replay and heatmaps), Google Analytics and the Meta Pixel run on this site. See our privacy policy, section 3, for what each one collects. When the Meta Pixel loads, your browser tells Meta Platforms, Inc. which page you viewed and when, your IP address and browser details, whether you tapped a phone number on the site (a “Contact” event, no number and no name; Google Analytics also counts taps on phone numbers, map links and links to leave a review, noting which link and nothing else), and the _fbp value, and, whenever you send a form on this site (the contact chat, the Book Your Stay form and the Long-Stay Rental Application, or a career application), a hashed (SHA-256) copy of the name, email address and phone number fields it recognises and nothing else; the plain text never goes to Meta. Meta uses this under its privacy policy and, for residents of the US states whose privacy laws it supports, under its Limited Data Use terms, which we switch on. We get back only counts, never who you are. Apart from those three and the Google Tag Manager loader that fetches them (gtm.js from googletagmanager.com, which sets no cookies and is never requested when the signals in section 4 or Reject All apply), the only scripts the pages load are our own. The office clock on these pages reads the office hours and any holiday closures from our own server at tfrooms.com.

• Our web host. The site is hosted on Netlify, which keeps ordinary server logs in order to serve the pages and block abuse. Those are logs, not cookies. Our privacy policy covers them.
• Forms. Submitting a form sends what you typed to us through our host’s form service. It does not place a cookie on your browser.

If you follow a link from this site to one of our individual property websites, to a map or to a review page, that destination sets its own cookies under its own policy, which we do not control.

4. Do Not Track and Global Privacy Control

If your browser sends a Do Not Track header or a Global Privacy Control signal, we honour it, and so does the Reject All button on the first-visit notice: Google Analytics, Microsoft Clarity and the Meta Pixel are not loaded at all, none of the cookies in section 2 is set, and nothing about your visit reaches Google, Microsoft or Meta. That is the opt-out. On this site, loading the Meta Pixel is the only sense in which we share personal information for advertising; we never sell any. Clarity and Google Analytics are used to understand how the site is used, not to build advertising profiles. Most browsers offer both signals in their privacy settings, and any content blocker also stops the pixel.

5. Managing this yourself

Every browser can block or delete cookies and clear stored site data, usually under privacy or site settings. You can also simply switch any accessibility preference back to its default.

6. Changes and contact

If what this site stores or loads changes again, this page will be updated before that happens rather than afterwards, and the effective date above will change with it. The last change started counting taps on links to leave a review in Google Analytics (section 3); like everything else here, that is switched off by the same signals and by Reject All. It also made the office clock read the office hours from our own server at tfrooms.com, keeping a copy in your browser (sections 2 and 3).

Questions about this policy: newleafmotels@gmail.com, or use the details on our contact page. See also our privacy policy and terms of service.