Privacy Policy

Who we are. Ridgework is the controller of the personal data described here. Our identity, address and host are published in full on the Legal notice page. Questions, or any request below, go to support@ridgework.org and are answered by a person.

No advertising pixel, no fingerprinting and no cross-site tracking. The signed-in cookie keeps you signed in and disappears when you sign out. A separate first-party cookie stores the first utm_source, via, and which plan was opened, for 30 days, so a signup on a later page still carries them. It is not shared and it is not an advertising cookie. If you sign up through an operator's link, a first-party cookie holds that link's code for one day, and our records link your account to that operator's pack. The operator is told only counts, never your name or your plan.

How many times a page is opened. We count, per day, how many times each page was opened. A record is three things: a date, the address of the page, and a number. No IP address, no browser identifier, no session, nothing that could connect two opens to the same person — and nothing that leaves our own server. Before anything is counted the address has its query string removed entirely and any token in it replaced (the calendar feed, the passport, a password reset), so a link that works as a key is never written down. We count two more things the same way, a date, a label and a number: where a visit came from (the utm_source on the link if it has one, otherwise the name of the site that linked here — a search engine or a few social sites by name, anything else as “other site” — or “direct”), and how many times the create-account form was opened. The referring address itself is never sent. Lawful basis: legitimate interest in knowing whether the service is used at all. Still no cookie banner, because there is still nothing to consent to.

Six further counts, still a date, a step and a short source label, and nothing else. The source is the same label as above: utm_source when the link has one, otherwise the referring site’s name, or direct. We count how often the worked-example page is opened, and how often the “Why this changed” box is shown with at least one session that changed. On an account we also count, once each: the address confirmed, the day's page opened on a later day, a second session logged, and a second time a session is rewritten. To group those four by where the account came from, that short label is kept on the account and deleted with it, and the same label is kept in the first-party cookie described above for 30 days. Nothing else is stored in the browser for these counts, and none of it leaves our server.

Visit statistics from our host. Our host, Vercel, also counts page views for us (Vercel Web Analytics): which page was opened, the site a visit came from, and the country (from the connection), browser and type of device. Before anything is sent, the address has its query string removed and any token replaced, exactly as above, and an address that is not a page of this site is counted only as “other”. Links inside this site pass on only our domain, never the page you came from. Vercel states that Web Analytics works without cookies. Lawful basis: legitimate interest in knowing whether the service is used. Vercel acts as our processor, as it does for hosting.

When the example rewrites a week. On the example page, when “Slept badly” or “Missed” rewrites a session, we count it the same way: a date, which plan, which of the two taps, and a number — nothing that identifies you. If you then create an account from that page’s trial button, the button’s link says a rewrite was showing, and we note that against your new account, with the plan. Nothing is stored in your browser to do this. Lawful basis: legitimate interest in knowing whether the example is what brings people in. The note is deleted with your account.

Your account. Your name, email address and a hash of your password. We never store the password itself. Legal basis: performance of the contract — without an account there is no plan to show you.

How you train. What you told us during setup: sport, objective, peak date, how many hours you can train in a week, the longest outing you have already done, how often you can train, which days and for how long each time, experience, terrain, and any constraints such as shift work or short sleep. Legal basis: performance of the contract. This is the input the plan is written from; without it there is no product.

How you feel. One tap on the morning: as written, slept badly, or missed. Legal basis: performance of the contract. These are subjective training inputs, not clinical measurements, and we do not ask for and do not want diagnoses, medication, test results or any other medical record. Ridgework is not a medical service and makes no diagnosis.

What you did. Which session was planned, whether you marked it done, missed or moved, and the minutes you entered. Legal basis: performance of the contract — it is what lets the plan respond to the week you actually had rather than the one that was written.

Integrations, only if you ask. A calendar feed creates a secret address for your sessions. Connecting intervals.icu stores the API key you paste, so we can push sessions to it. Both are off until you turn them on, both can be disconnected, and disconnecting deletes what was stored. Legal basis: consent.

Payments. Card payments are handled by Polar as merchant of record. We hold your subscription status and never your card number.

Who else sees it. Only the providers that run the service, listed with their addresses and regions on the Legal notice page: Vercel (hosting in the Paris region, and the visit statistics above), Neon (database, Frankfurt), Resend (confirmation and password emails, Ireland) and Cloudflare (DNS and mail routing). Each acts on our instructions under a data processing agreement. We do not sell personal data, and we do not share it for advertising.

Data outside the EU. Those providers are US companies. Your data is stored in the EU where the provider offers it — the database is in Frankfurt and email in Ireland — but support access from the United States is possible. Transfers rely on the European Commission's standard contractual clauses and, where the provider is certified, the EU–US Data Privacy Framework.

How long we keep it. Your account and training history stay while the account exists. Delete the account and we delete them, except anything we must keep for accounting or legal reasons, which we keep for the period the law requires and for nothing else.

Your rights. You may ask for a copy of your data, correct it, delete it, restrict or object to how we use it, take it elsewhere in a portable form, and withdraw consent for the integrations at any time. Write to support@ridgework.org. We answer within a month, usually far sooner.

Complaints. If our answer does not satisfy you, you can complain to the French supervisory authority: CNIL, 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, or cnil.fr. You may also complain to the authority where you live.

Changes. If this notice changes materially we will say so on this page and, where the change affects how we use data you have already given us, by email.