Peak Cluster Watch
Privacy notice
Effective: May 2026
Short version: your postcode is checked locally in your browser, never stored on a server we run, never visible in the address bar, and never put into a share link. It lives in the form field on your device — nowhere else.
What happens when you enter a postcode
The postcode lookup sends the postcode you type to postcodes.io to fetch an approximate coordinate for that postcode area. That request goes directly from your browser to postcodes.io — this site never sees, logs, or stores it. postcodes.io is run by Ideal Postcodes (a third-party service); see their privacy notice for what they do with requests.
The distance calculation then runs locally in your browser using the coordinate returned. There is no campaign-controlled postcode database or server-side log.
Sharing your result
When you press Share this with friends, the share link is just peakclusterwatch.org — your postcode is stripped out, so a forwarded link never reveals where you live. The accompanying share message names your distance (e.g. "I'm 1,200 m from the proposed Peak Cluster CO₂ pipeline") but never your postcode.
Map tiles
The map is rendered using OpenFreeMap. As you pan and zoom, your browser requests map tile images from OpenFreeMap's servers. Those requests include the tile coordinates your browser is loading — a standard feature of all web maps. We do not control or log those requests.
Fonts and scripts
Page fonts are loaded from Google Fonts. Page scripts and the map library are loaded from jsDelivr (a public CDN). These are standard third-party services; your browser connects to their servers as part of loading the page.
Cookies and local browser state
This site sets no cookies. It does store two small flags in your browser — both kept on your device, never sent to any server:
pcw-intro-seen(local storage) — remembers that you've already watched the cinematic intro animation, so it doesn't replay on every visit. Cleared when you press Watch the intro on the main page (the intro then plays from the start).pcw-legend-pulsed(session storage) — remembers that the map legend has pulsed once during this browser tab, so it doesn't pulse again on repeated postcode searches. Cleared automatically when you close the tab.
Neither flag contains a postcode, an identifier, or any information about you. They control animation timing only.
Analytics
This site uses Vercel Web Analytics to count page views and visitor geography (country / device). Vercel Web Analytics is privacy-respecting: it sets no cookies, does not track individual users across sites, and does not collect personal information. Your postcode is never sent to Vercel because it never appears in the page URL — the form holds it on your device and the page address bar shows only peakclusterwatch.org. The analytics script is served from the same server as this page (/_vercel/insights/script.js). For details see Vercel's analytics privacy policy.
Geographic data
The boundary and infrastructure data files (GeoJSON) are served from the same server as this page. No information about you is embedded in or returned from those files.
Applicant-published section polygons (Wirral, Cheshire West, Coastal AGI, eastern sections) are from Peak_Cluster_AGOL Individual Sections and Coastal AGI feature services, copyright Arup/AECOM. Overlay layers (transport, paths and cycleways, waterways, water bodies, habitats, farmland, receptors) are derived from OpenStreetMap contributors under the Open Database Licence (ODbL) 1.0. Full per-layer attribution is on the main page under Sources & method.
Questions or a problem? Email us.