Cookie Policy

This page describes the cookies and similar technologies used across moorerunway.com and app.moorerunway.com, and what they keep in your browser. One policy covers both because one cookie does: it is set for the shared parent domain, so the same visit is recognised on either host. Some of what is kept is necessary to make the audit work at all; the rest is analytics, which tells us where people stop.

What is kept on your device

The audit at app.moorerunway.com keeps things in two places in your browser, and the marketing site keeps neither. Neither is a cookie: neither is ever attached to a network request, so nothing here is sent to us or to anyone else.

Two things are held in local storage, which stays on your device until you clear it.

• Your audit progress. The answers you have given and the score derived from them, so a reload or a back button does not lose your place.
• Your colour scheme. Whether you asked for the light or dark theme, so the page does not flash the wrong one on the next visit.

Two more are held in session storage, which is emptied when you close the tab.

• Your website scan result. What the check found, and the address you gave it, so the report survives a reload and the back button. It is never stored on our side — closing the tab is what removes it.
• Which analytics events have already been sent. A marker per event, so one thing you did is not counted twice.

Cookies

We use analytics cookies, set by Google Analytics, to understand which pages and screens people reach and where they leave. They record behaviour — a page was seen, a button was clicked, a question was answered — and never the text you type into the audit. Because the cookie belongs to the parent domain, it is the same cookie on moorerunway.com and app.moorerunway.com, which is what lets us see that a visit which began on one continued on the other.

We do not use advertising cookies, we do not run session recording, and we do not sell what analytics collects.

There is no consent banner. On moorerunway.com, analytics storage starts denied in the European Economic Area, the United Kingdom and Switzerland: no analytics cookie is set there, and you are not asked, because we do not rely on your agreement to set one. Everywhere else it starts granted, and you can refuse it in your browser settings at any time — see below.

On app.moorerunway.com analytics is not running at all, so no analytics cookie is set anywhere. It carries the same regional default as the marketing site, so if it is switched on it starts denied in the same places. If that changes, this page changes first, and the effective date at the top is how you can tell.

Being honest about what “denied” means, where it applies: no cookie is written and you are not identified, but a request is still made to Google carrying the page you are on, where you came from, and an approximate location derived from your network address. If you would rather make no such request at all, blocking googletagmanager.com in your browser or an extension prevents it.

How to clear it

Clearing site data for moorerunway.com removes the analytics cookie for both hosts, because it belongs to the parent domain — clearing only app.moorerunway.com will not remove it. The audit’s local storage is cleared with app.moorerunway.com. In most browsers this is under Privacy, as “Cookies and site data”, then “See all site data”. Using a private window means nothing is kept after you close it.

Blocking cookies for either host breaks neither the marketing site nor the audit. Your audit progress lives in local storage, which is separate — though clearing that will lose your place.

Related

The Privacy Policy covers what happens to your answers more generally, including the website address you enter on the first screen.