Privacy

Beta and purpose

Good to Ride recommends gravel tires from structured experiences that riders contribute — ratings and setup details, not free-text reviews. The service is in beta and may change.

Who is responsible for your data

The data controller is the operator of Good to Ride; their name and email address are on the Contact page. Write to that address about anything to do with your data.

What is stored

When you save an experience we store the tire and size you chose and whether it is on the front or the rear; your weight and, if given, your bike's weight; tire pressure, mounting type and rim width if given; mileage and number of punctures; the mix of surfaces, ride types and conditions you ride in; your ratings; and, if you no longer ride the tire, why and what you want to improve. We also store a random contributor identifier and the time of the submission.

We do not ask for your name, email or an account, and nothing is published under your name. If you use "report a missing tire", the short text you type (up to 200 characters) is stored too, together with the interface language.

We also keep technical identifiers that let us recognise a repeated submission, so pressing Save twice, or retrying after a connection problem, does not record the same experience twice. These identifiers do not contain what you entered.

Your weight is body data: enter it only if you are comfortable with that.

The contributor cookie

After your first saved experience the app sets one cookie, gt_contributor_id. It holds your random contributor identifier plus a signature, so the app can recognise that later submissions come from the same browser. It is HttpOnly, is kept for up to two years and is refreshed when you save again. It is not used for advertising or tracking. Clearing it makes your next submission start a new identifier.

Visit statistics

We count visits with Plausible Analytics, to see how many people use the app and which pages they open. Plausible sets no cookies and builds no profile of you. It records the page address, the site you came from, your browser, operating system, device type and country. We also count when an experience is saved, what kind of result a search ends in (ranked, not enough data, no matching tire) and when results are shared — only that it happened, never what you enter. Results page addresses are sent without your answers. Your IP address is not stored: it is used only to tell the country and to count unique visitors per day in a way that cannot be traced back to you. The data is processed in the EU.

How experiences are used

Saved experiences are combined with other riders' into aggregated riding data. When someone describes what they are looking for, the app scores tires against that data and shows the result with a confidence level. Individual experiences are not shown to other riders.

Limits of the recommendations

Recommendations rest on a small, self-selected group of riders during the beta. Some tires have little or no riding data, and results can be wrong for your bike, weight or terrain. Treat them as a starting point, not as a guarantee or safety advice.

Server logs

If saving fails unexpectedly, the server logs the type of the error and a short reference number. Logs do not contain what you entered, cookies or secrets. The connection's IP address is used only to limit how often one source can submit or search and is not stored with your experience.

Legal bases

We process experiences and missing-tire reports on the basis of your consent (Art. 6(1)(a) GDPR), which you give by saving them. You can withdraw it at any time by asking for deletion; this does not affect the lawfulness of the processing before that. Providing the data is voluntary — without it you simply cannot save an experience.

Visit statistics, limiting how often one source can submit, and error logs rest on our legitimate interest (Art. 6(1)(f) GDPR): knowing how the app is used and protecting it from abuse. You can object by writing to the address on the Contact page.

The contributor cookie is necessary for the feature you are using: recognising that later experiences come from the same browser, and deleting them when you ask. That is why we do not ask for separate consent to it.

Service providers

We use three providers that process data only on our behalf: Vercel (app hosting), Supabase (database, on servers in Frankfurt, in the EU) and Plausible (visit statistics, EU). Requests to the app — including saving an experience — are processed on Vercel's servers in Frankfurt, in the EU; the connection, with its IP address, first reaches a nearby Vercel network node. Vercel Inc. is a US company, so data may also be transferred to the US. This transfer relies on standard contractual clauses approved by the European Commission. We do not sell data or pass it to anyone beyond these providers.

How long data is kept

Experiences and missing-tire reports are kept for as long as Good to Ride runs, or until you ask for them to be deleted. The contributor cookie expires two years after your last save. Server logs are kept briefly by the hosting provider, for no more than 30 days. Plausible keeps only aggregate statistics that cannot identify you.

Your rights

You have the right to access, correct, delete, restrict and port your data, and the right to object and to withdraw your consent. We do not know who you are, so we can only find your submissions through your deletion reference or your contributor cookie. Saved experiences are not edited: if something has changed, add a new experience or ask for your submissions to be deleted.

You can also lodge a complaint with a data protection authority — in Poland, the President of the Personal Data Protection Office (uodo.gov.pl). We make no decisions about you based solely on automated processing: a match scores tires, not you.

Deletion and contact

To ask for your submissions to be deleted, or with any privacy question, use the Contact page. Deletion is handled manually by the operator, who erases the data belonging to the deletion reference you send. You get that reference after saving an experience, and you can show it again below in the browser that holds your contributor cookie. If you lose both, we may not be able to identify your submissions.

Your deletion reference

If you want the operator to delete what you submitted, they need this reference. It is generated from the contributor cookie in this browser and is not stored or shown anywhere else.

Keep it somewhere safe. If you lose it and the cookie is gone too, your submissions may not be identifiable and deletion may not be possible. If the service's signing secret is ever changed, references and cookies issued before that stop working. Recovery is not guaranteed in either case.