What we collect

Nobody, unless you decide otherwise. When you first do something worth remembering we set one cookie, sid, holding a random number and a signature. It is not derived from anything about you, it expires after thirty days, and its only job is so that the frame you measured is still there when you come back. No account is required for any part of the product, and none is ever asked for before you have made something worth keeping.

If you do create one, that changes and this page says so rather than pretending otherwise. An account is handled by Clerk, who hold your email address and your password so that we do not; we receive an account identifier from them and store that against your frames, trips and gear in place of the random session number. From that point we can identify your data from your email address, where before we could not. Signing in on a new device brings across whatever the browser you signed in from was already holding.

It is the measurement, so it is the one genuinely sensitive thing here. When you upload it we strip the EXIF metadata — which is where the GPS coordinates of your house usually live — and re-encode the image before storing it. The original, with its metadata, is never written down.

A copy also stays in your own browser so a saved frame can show its photograph without fetching it again. That copy is yours and clearing your browser storage removes it.

Your answers, the kit list they produced, what you own, and the frames you measured. Trips and gear carry the names you gave them. All of it is attached to that random session number and nothing else.

A ride in progress is held in your browser rather than on our servers until you save it, which is why closing the tab does not lose it and why we cannot see it before you do.

If you accepted the banner, we record which parts of the product get used — that a plan was started, that a question was answered, that a link was followed. We use PostHog for this, and it sets its own cookie.

What it never receives: your photograph, the names you typed, or the free text you wrote. Automatic click-capture and session recording are both switched off, specifically because the first records the text of what you click and the second would record the photograph. If you declined, none of it loads at all — no script, no cookie, no request.

Four companies, and each one only what it needs to do its job:

Vercel hosts the site, so every request passes through them. MongoDB Atlas is the database where a saved trip, frame or item of gear actually sits. Clerk handles accounts, and holds your email address and password so that we do not — we receive an account identifier from them and nothing else. PostHog receives the measurement events described above, and only if you agreed to them.

When you follow a link to a bag maker you are on their site under their terms, and some of those links pay us a commission — which is shown to you on the link itself, before you click it, including when the answer is that it pays us nothing.

Nobody buys this data. There is no advertising network here and no data broker, and we do not sell or share it for advertising in the sense any privacy law means by those words.

Deleting a trip, a frame or an item of gear removes it from your account view. Clearing your browser storage removes the local copies and the session cookie, after which nothing remaining can be connected to you.

If you want everything associated with you erased outright, ask and we will do it. With an account, your email address is the handle and that is enough for us to find it. Without one we hold no email address at all, so the session cookie is the only handle that exists and you have to still be able to supply it.

The controller — the party that decides why and how your data is used — is [controller — not yet supplied], at [address — not yet supplied]. Questions, requests and complaints go to [contactEmail — not yet supplied].

Your frames, trips and gear are held to perform the service you asked for — you pressed save, and this is what saving means. The session cookie that connects them to you is strictly necessary for the same reason: without it your own things are unreachable, so it is not a cookie you can be asked to consent to.

Measurement is held on consent, and only consent. If you declined the banner, no analytics script loads at all — not a request, not a cookie. You can change your mind in either direction and the product works identically either way.

An account, if you make one, is held to perform a contract: you asked us to keep your things across devices, and that cannot be done without something stable to attach them to.

Keeping the service standing up — refusing repeated wrong admin passwords, refusing malformed requests — rests on our legitimate interest in not being trivially broken into or knocked over. The data involved is an IP address and a counter.

The session cookie: thirty days from your last use, then it expires and whatever it pointed at becomes unreachable.

Trips, frames and gear: until you delete them, or until you ask us to erase everything. There is no automatic sweep, because a rider who comes back after two winters should still find their bike.

Rate-limiting records: an hour at most, and they are swept automatically.

Measurement events: retained by PostHog under their retention policy. They contain no photograph, no free text and no name.

The processors are named above: hosting, the database, the account provider and — with your agreement — the analytics service. They act on our instructions and for nobody else.

Data is processed in the European Union and the United States depending on the provider. Where it leaves the UK or EEA it does so under the transfer mechanisms those providers publish, which for all four is the standard contractual clauses or an adequacy decision. We do not move it anywhere else.

You can ask for a copy of what we hold, ask us to correct it, ask us to delete it, ask us to stop using it, object to a particular use, or ask for it in a portable form. Send any of those to [contactEmail — not yet supplied] and you will get an answer within one month.

Two honest limitations. Without an account, the session cookie in your browser is the only handle that exists — so a request has to come from that browser, or carry that session, or there is genuinely nothing we can match you to. With an account, your email address is the handle and that is enough.

If you think we have handled your data badly you can complain to a supervisory authority — for us, [supervisoryAuthority — not yet supplied] — and you do not have to raise it with us first, though we would rather you did.

This is not built for children and is not offered to them. We do not knowingly collect anything from a child under 16. If you believe a child has used it and left something behind, tell us and it will be removed.

The fit verdicts and the kit list are produced by rules, which is a kind of automated decision — but not the kind the law is worried about. Nothing here decides anything about you: no profiling, no scoring, no legal or similarly significant effect. Every line tells you which of your own answers produced it, and you can disagree with all of them.

It describes what the code does today and is updated when the code changes. If something here turns out not to match the behaviour, the behaviour is the bug.

It has not been written or reviewed by a lawyer. The facts in it are accurate and checkable; whether stating them this way satisfies a particular obligation in a particular country is a question for somebody qualified, and one worth asking before this takes real traffic.

In effect since 2 August 2026. Also worth reading: the terms of use.