Cookie Policy
Last updated: 17 August 2026
This policy explains what cookies are, which ones this site uses, and how to control them. Read it alongside our Privacy Policy.
What a cookie is
A cookie is a small text file a website stores on your device. Some remember things between visits, like a login. Some just make a specific feature work, like a booking widget. Some track behaviour across sites for advertising.
The short version
We set no cookies of our own unless you accept them. We run two analytics tools. One is our own, it uses no cookies, and it runs for everybody. The other is Google Analytics, it does use cookies, and it loads nothing at all until you press Accept on the banner.
The one exception is not ours: if you use the Calendly booking widget on /schedule/, Calendly sets its own cookies to make the booking work, under its own notice inside the widget. That is described further down.
Analytics that runs without cookies
Rialto. This is our own analytics tool, built and hosted by us. It records page views and on-page interactions such as clicks, so we can see which pages get used. It sets no cookies, uses no cross-site tracking identifier, and does not identify who you are. Visitors are counted using a value that is rebuilt from scratch every day and cannot be traced back to a person or linked across days.
Because it stores nothing on your device and holds nothing that identifies you, it needs no consent and it is not affected by your answer to the banner.
Analytics that only runs if you accept
Google Analytics 4. If you press Accept, we load Google Analytics, which sets its own cookies on your device and sends details of your visit to Google. The cookies it sets are:
- _ga, which lasts up to 2 years and tells Google Analytics apart one browser from another.
- _ga_DZ2LML1S9W, which lasts up to 2 years and holds the state of your current visit.
We use it to count visits and see which pages and sources bring people here. We do not run Google Ads or any other advertising product on this site, and we never grant Google permission to use this data for advertising or personalisation.
If you press Reject, nothing is requested from Google at all. No script is loaded, no cookie is set, and no data about your visit leaves this site for Google. This is stricter than the common approach, which loads Google's tag straight away and asks it to hold back the cookies.
How we remember your answer
Your answer is stored in your browser's local storage under the name lm-consent, not in a cookie. It records only your answer and the date you gave it. Clearing your browsing data removes it, and the banner asks again.
Changing your mind
You can change your answer at any time, and withdrawing is exactly as easy as accepting. Use the button below, or the "Cookie choices" link in the footer of every page.
If you switch from Accept to Reject, the Google Analytics cookies described above are deleted from your browser at the same time.
Cookies set by third parties we embed
Calendly. The booking widget on our /schedule/ page is provided by Calendly. It sets its own cookies to run the scheduling flow, for example to remember the time zone and steps you've completed while booking. These are set by Calendly, and governed by Calendly's own cookie and privacy policies, not by us. Calendly shows its own consent notice inside the booking widget, which is why that page can show two.
Managing cookies in your browser
You can block or delete cookies through your browser settings at any time. Blocking Calendly's cookies may stop the booking widget from working correctly, in which case you can still book a call by emailing [email protected] or reaching out through our contact page.
Most browsers let you see and clear cookies under Settings, then Privacy. Check your browser's help pages for exact steps, they differ between Chrome, Safari, Firefox and Edge.
Changes to this policy
We'll update this page if the cookies this site uses change, and update the date at the top when we do.
Questions
Email [email protected] or use our contact page.