What we store, and what we don’t

No Google Analytics. No Facebook Pixel. No advertising or attribution tags. No session replay or heatmaps. No profiling, and nothing sold or shared with data brokers. No third party is given anything about you.

This site used to show a cookie banner asking permission for Google Analytics and the Facebook Pixel. Neither was ever actually installed — the banner was gating tracking that did not exist. We removed it rather than leaving you a decision to make about nothing.

This app runs on Base44, and its platform records a first-party page view each time you open a page here. It is theirs and ours, not an advertising network’s, and it does not follow you off this site.

• What it records — the path you opened (for example /privacy), the time, the page you arrived from, and your account id if you are signed in — null if you are not.
• Session id — a random string kept in your browser's local storage, so several page views in one visit can be counted as one visit rather than several. It is not tied to you, and clearing your browser storage ends it.
• What it's for — knowing which pages get used, so we build the ones that do. Nobody is targeted, scored or advertised to on the back of it.

It is part of the hosting platform rather than something we added, and it cannot be switched off from our side. If that matters to you, a tracker blocker will stop it without breaking anything on this site.

All of it is in your browser’s own storage, and all but the last line is there to make something you asked for work.

• Sign-in session — keeps you logged in. Set by Base44, which hosts this app.
• Onboarding flag — remembers you finished the intro so it doesn't ambush you again.
• Checklist progress — your own ticks on the remote work checklist, saved in your browser so you keep them without an account.
• Check-in draft — a report you started writing but haven't filed, so a refresh doesn't lose it.
• Platform keys — a handful of Base44 values: the app id, a stored answer to the old cookie prompt, and the page-view session id described above.

Clearing your browser storage clears all of it. The checklist ticks are the only thing you would actually miss.

Some features work by asking someone else. Your browser connects to these directly, so they see your IP address, as any site you visit does. We don’t send them anything about you.

• OpenStreetMap (Nominatim) — turns a place name into map coordinates when you search.
• postcodes.io — looks up UK postcodes.
• Cloudflare — runs the connection speed test, and only when you start one.
• Google Fonts — serves the two typefaces the site is set in.

We store your email address, the first name you gave us, the date and time you opted in, and the exact wording of the opt-in you ticked. That last one matters: it means we can show precisely what you agreed to, rather than just claiming you agreed.

We only add you if you tick the box. If you don’t tick it, nothing is saved at all — we don’t keep the address for later. The list is used for the weekly guide and nothing else, and every email will carry an unsubscribe link.

Spots, reports, check-ins and reviews you file are shown publicly on the site under your profile name, because the whole registry is built from them. Your email address is not shown.

There are none today. If we ever add them, tracking a click for commission is not something we can do quietly under “strictly necessary” — we will ask first, in a prompt about exactly that and nothing else, and any link will still work perfectly well if you say no.