Last updated 13 November 2026
RideWinds is a weather app for cyclists made by an individual developer in Canberra, Australia. It has no accounts, no analytics, no advertising and no tracking. This page says exactly what leaves your phone and why.
If you allow it, RideWinds uses your location on the phone to show where you are on the map, to set your weather place, and to let a ride start from where you are. Your live location stays on the phone and is not shared with anyone. If you set your weather place from where you are, that place's coordinates go with forecast requests, as described under Weather forecasts. You can decline location access and search for a town instead.
To fetch forecasts, the app sends the coordinates of your weather place and of points along your saved routes to RideWinds' own server (run on Cloudflare, with its records kept in Sydney), which passes them to Open-Meteo, the forecast provider, with RideWinds' key. With each request goes a random identifier made on your phone when the app first runs. It identifies the phone, not you: it is not linked to your name, Apple ID, email or location history, and it is used only to count each phone's forecast calls against a daily allowance and to hold a subscription's status. The server keeps the identifier and the count. It does not keep a record of where you asked about. For a short time (minutes for a forecast, up to a week for a place name) it may hold an answer together with the coordinates it was for, so that the same question is not sent to Open-Meteo twice; that copy is not linked to the identifier. Settings → About → "Forget this device" deletes the identifier and its record; a new one is made the next time a forecast is fetched. Open-Meteo sees the coordinates, not the identifier; its own privacy policy applies to that request.
Routes you import (GPX files, Strava routes, Quick out-and-back) are stored only on your phone and in your iCloud device backup. The routes themselves are never uploaded; only the sample points along them that a forecast needs are sent, as described above.
If you connect Strava, RideWinds asks for read-only access. The sign-in is handled by Strava; your Strava password is never seen by the app. Access tokens are stored in the iPhone Keychain. RideWinds never posts to Strava.
What it reads: the routes and rides you choose to import (GPS track, timestamps, name, distance); the segment efforts on those rides, your PR times, and each segment's details including its KOM/QOM time; your starred segments, only when you ask in Settings; your recent rides (the last week) to match them to your courses and compare them with the forecast, which you can turn off in Settings; how many riders Strava grouped on a ride; and heart rate and power on a ride, if you recorded them, used once while a debrief is worked out to tell effort from wind, and not kept.
How and where: through Strava's API when you import, when the Rides tab opens (at most hourly) and in a weekly refresh. Everything is kept only on your phone and in your iCloud device backup. Nothing that came from Strava is sent to RideWinds' server, apart from the sample points along a route that a forecast needs, and nothing is shared, sold or used for analytics. The details of a recent ride read for a debrief are deleted after seven days. Strava data that is kept longer (an imported route or ride you saved as a course) is refreshed from Strava weekly and anything that cannot be refreshed is removed; rides you delete on Strava are removed from the app within two days.
Withdrawing and deletion: Settings → Strava → Disconnect revokes RideWinds on Strava and deletes everything that came from Strava on your phone — imported rides, segment details and PRs, favourites imported from stars, and the ride history — and shows you a confirmation when it is done. You can also revoke RideWinds at strava.com/settings/apps, which has the same effect the next time the app runs, or email us to ask for deletion. Rides imported from GPX files are yours and stay.
Strava and usage data: Strava may collect data about RideWinds' use of its API (such as request volumes) under Strava's own privacy policy.
The Tour de Cure tab shows content (story, dedications, fundraising progress) fetched from this website. Donations happen on Tour de Cure's own site, under their privacy policy; the app does not see them.
Purchase of the app, TestFlight beta participation and crash reports (if you have opted in on your device) are handled by Apple under Apple's privacy policy. If you subscribe to RideWinds Plus, Apple handles the payment; RideWinds' server receives Apple's record of the subscription (its transaction identifiers, product, dates and status — never your name, email or payment details) and ties it to your phone's random identifier so the app can show what the subscription opens. That record is deleted with the identifier.
Questions: hello@ridewinds.app.