Privacy notice
Last updated 4 November 2026 · Liverpool pilot
Who we are
CornerMile is run-club software for hospitality venues, currently in a Liverpool pilot. For anything in this notice — questions, access requests, corrections or deletion — email security@cornermile.co.uk, the monitored contact address during the pilot.
What we collect, and why
Venue teams: your email, venue name and address, and team roles — to run your account. Runners: your email, optional display name, club memberships, RSVPs, verified check-ins and any rewards earned — to run the club you joined. You can also keep a runner profile: an optional phone number, an emergency contact, an age range (a band, never your date of birth), and an optional birthday (day and month only — the year is never stored). You enter these once and choose, per club, what that venue can see — a venue only ever sees the fields you share with it, and you can change your mind any time. Emergency contact details are controlled by you (a venue can ask for one), and only shown to the venue's run leaders for a run you're on, from 3 hours before to 6 hours after; they can download it for that run in case something happens, every download is logged, and they can't see it at any other time. A birthday you share with a venue is used only to time a birthday treat: the venue sees a “birthday this week” marker and a weekly count, nothing else about it. You can change or stop sharing it whenever you like. Consents: when you opt into run updates or venue news we store the exact wording you agreed to and when — and the same when you withdraw. Launch list: if you register interest from outside the pilot area we store your name, venue, contact details, location and role so we can email you launch and product updates you asked for, and to understand where demand is. Leader interest: if you register to lead a run club we store your name, contact details, location, social handle and the optional notes you give us about your audience and availability — so we can email you about venues looking for a run leader and match you with clubs, by hand, at pilot scale. Run leader qualifications: if you add a running qualification to your leader profile we store which one, the month your licence runs out and when you declared it. Only venues you apply to see it, labelled as self-declared; it never appears on public pages, and it's deleted with your profile. CornerMile doesn't check it. Runner interest: if you ask to hear when a club opens near you we store your email, the town or city you gave, an optional first name and postcode area, and the exact wording you agreed to — so we can email you when a club opens there and see where runners are waiting. Searching the club directory stores nothing; only that form does. The club widget: the embed a venue puts on its own website shows only the same public information as the club page and sets no cookies. Club WhatsApp: if your club shares a WhatsApp group, you accept a short notice before the invite link appears. We record which version of the link and notice you accepted, and when, so the venue can see how many members have the current link and we can show what you were told. The group itself is run by the venue on WhatsApp: CornerMile never joins it, reads it or receives anything from it. CornerMile staff may access a venue's data to give support, with the same limits as an owner. Changes they make are recorded internally; there is no per-visit notification.
What we don't do
No advertising, no selling or renting data, no tracking pixels in email (deliberately, we don't use open tracking), no advertising or cross-site tracking cookies anywhere, no profiles built about individual people, and no sending marketing without an explicit opt-in. Emails you receive because you RSVP'd to a run, such as cancellations and time changes, are service messages, not marketing. Nothing in the measurement described below is ever used to decide what to send you, and none of it is linked to your email address.
How we measure the pilot
We need to know where people get stuck signing a venue up, joining a club or checking in, so we can fix it. Two things do that, and neither builds a picture of you. A short-lived journey marker: when you start signing up, joining or checking in, we set a first-party cookie holding a random reference that means nothing anywhere else. It lasts 30 minutes, your browser cannot read it, and it lets us count steps like "asked for a code" and "came back with the code". What we store against it is a fixed list of step names plus whether you arrived from a search, a QR code, social or a link. We never store your name, email, postcode, IP address, browser, what you typed, or the address of the page you came from. Help given by hand: if we help someone through a step, we record what kind of help it was, at which step, and how it ended — with no notes, nothing about the person, and no record of which of us helped. What is deleted, and when: after 90 days the step records and the assistance records are deleted, and the random journey reference that links them goes with them. What survives is counts and timings that name nobody and cannot be traced back: how many journeys reached a step on a given day and how long that typically took, and how many times each kind of help was needed at each step. There is no way to get from those counts to a person, a session or a device. Page and speed statistics: the code for Cloudflare Web Analytics is built in but not switched on. It is privacy-first, sets no cookie, and reports page views and loading speed without identifying visitors — but it stays inactive until a Cloudflare site and token are set up, so nothing is being sent to it today, and when it is switched on it will run on the live site only. Technical error details: if the site stops working in your browser, a technical report is sent so we can fix it: the error, where in our code it happened, and your browser and operating system version. It is designed to exclude personal information: it never includes cookies, form entries or what you typed, email addresses, phone numbers and codes are removed from the error before it leaves your browser, and the page is recorded as a code pattern, never the link itself. Our lawful basis for both is legitimate interests: running and improving a service you are using. It is not marketing, it is kept separate from every consent you give us, and opting out of run updates or venue news has no effect on it either way.
Where your data lives
Data is stored with Supabase in London (UK/EU region) and served through Cloudflare. Emails are sent through two providers: Brevo, an EU-based email provider, and Amazon Simple Email Service (Amazon SES), run by Amazon Web Services in its London region. Sign-in codes go through Amazon SES; our other emails go through Brevo, with Amazon SES as a backup when Brevo can't send. Each provider receives only what it needs to deliver a message (the address and the email itself), and both keep a list of addresses that bounce or complain so that we stop sending to them. The technical error reports described above, and errors from our own servers, go to Sentry in its EU region; they are designed to exclude names and contact details. Ordinary email-queue rows store IDs, not email addresses; addresses resolve at send time. If you delete your account, one requested final confirmation uses a temporary, private recipient record that is removed after delivery or within 24 hours.
How long we keep things
Venue data: while the account is active; when a venue is deleted, a support-recoverable snapshot is kept for 30 days and then permanently purged. On a runner's request, account deletion is immediate and there is no recovery window. Personal profile, contact, sharing, consent and sign-in data are removed, and the person leaves every club. Venues retain attendance, accepted-terms, club WhatsApp notice and redemption records with the link to the person cleared and the name shown as Former member; anonymous consent counts remain. One final confirmation is sent, and no further email is sent to that address. The encrypted nightly backup may retain pre-deletion data for 31–44 days before its retention sweep; a separate hash-only deletion ledger ensures a restore applies the erasure before the service resumes. Launch-list, leader-interest and runner-interest entries: until you unsubscribe (one click in any email) or ask us to delete your entry. Concern reports and audit records are kept as long as safeguarding and accountability require. When a venue is deleted, concern reports about its clubs are moved to a safeguarding archive that only CornerMile's administrators can see, so repeated concerns about the same person at different venues can still be spotted; the archive keeps the report but not who sent it, and no screenshots. Screenshots attached to a concern are stripped of image metadata (including any location data) in the browser before upload and checked again on the server, stored in a private bucket that only the club's owners/managers and CornerMile can view, through short-lived signed links, and deleted 90 days after upload, unless an action about that report is still in progress, in which case they are deleted once it closes. To stop the form being misused, we count how many reports with screenshots each person sends in a day (screenshots can be added to three a day); the count is just a number and is deleted the next day. The onboarding step records and the assistance records described above are deleted 90 days after they are made — including the random journey reference — leaving only the counts and timings above, which identify nobody.
Your rights
Under UK GDPR you can ask for a copy of your data, correction, deletion, or restriction of processing. You can leave a club or delete your account from Your account; deleting your account requires a recent sign-in and typing delete. You can withdraw any consent at any time — consents have controls in the product, and every marketing email has a one-click unsubscribe. Email security@cornermile.co.uk to exercise any of these. If you're unhappy with how we handle your data you can complain to the ICO at ico.org.uk.
Changes to this notice
We'll update this page as the product grows — the date below always reflects the current version. Consent wording shown at the moment you opted in is stored verbatim with your record, so later copy changes never rewrite what you actually agreed to.
Looking for the launch list? It's here. Want to lead a club? Register as a run leader.