Privacy

The short version

• There is nothing to sign up for. The site sends no email, and it can’t receive any: cycleforchange.org has no mailbox. The one exception you choose yourself: tap “Keep me posted” on the Fruit Loop RSVP and Robert can reach you about rides.
• Google Analytics counts visits and pages. It never gets your name or anything you type. The few taps it counts are named below.
• Five forms exist. What you send goes to Netlify, which hosts the site. Some of it then goes into the review queue, which is a public list of issues in the site’s code repository on GitHub, and some of it, with your say-so, onto a page. Never your email, never a photo. Each form is spelled out below.
• “Near me” uses your location inside your browser and nowhere else.
• The ride briefing works on your ride file in your browser. It never uploads it.

Analytics

Google Analytics 4 is added by Netlify when it serves a page, not by this site’s own code. It counts which pages are read, roughly where visits come from and how long they last, and four taps we named so we can tell what’s useful: a tap out to a ride’s host, a tap to one of the orgs’ own ride registrations, a tap on a homepage finder tile (group rides or events), and a tap on the “Ride with me” bar. No name, no email and nothing you typed goes into any of them. What Google does with its own data is in Google’s privacy policy. If you block analytics with a browser setting or an extension, every part of the site still works.

The site’s own code sets no cookies. It uses your browser’s storage for small conveniences that stay on your device: whether you hid the “Ride with me” bar or paused the homepage film this session, your filters on the 2027 calendar, your week on Tonight, your details on the ride check-in, and your answer on the Fruit Loop RSVP with a random number that lets a second tap change it. The site never reads any of that back from anywhere else.

The five forms

Every form on the site is a Netlify form. What you send lands in Netlify, which stores it under Netlify’s privacy policy. From there, a script reads it once an hour (reports once a week) and opens a note in the review queue. The queue is public: it’s the issue list of the site’s code repository on GitHub, and only the fields named below go into it. Emails, files, photos and locations never leave Netlify.

Report a ride

On every ride page and on Add a ride. It asks what changed (new, changed, gone, still on), the ride, a new time or date, a link, who you are to the ride, and an email you can leave blank. Reports are read on Mondays and checked against the host’s own page before anything on a ride page changes. Your note (up to 300 characters) is kept with the ride’s record in the site’s public data; the change goes up; your email never does. If you tick “I run this ride” and leave an email, a person replies to that email to confirm before the listing changes. The email stays in Netlify.

Review a ride

On every ride page. It asks whether you’d ride it again, the pace, twenty to six hundred words, your first name, where you’re from, and an email you can leave blank. Each review becomes a note in the public review queue that carries the words, the first name, where you’re from and the date, never the email. Nothing shows until Robert has read it. If he posts it, the ride page shows the first name, where you’re from and the words. The email stays in Netlify and, when the email alert is set up, in Robert’s inbox.

Send us the route

On every ride page. It asks for the ride, the route file and a note. The file stays in Netlify; the note in the review queue says a route arrived for which ride, with your typed words minus any links, emails and phone numbers. A route goes onto a page only when it comes from the people who run the ride, and then the file itself is on the page for anyone to download.

What do you cycle for?

On the cycle-for page. It asks what you cycle for, your first name, your Instagram handle, the link to your post, a clip you can leave out (a big one is shrunk in your browser before it’s sent), an email you can leave blank, three boxes (you’re 18 or over, everyone in the clip said yes, and we can use it), and the version of the OK you agreed to. The public review queue gets the first name, the handle, the answer, the OK’s version and the time, never the email and never a link to the clip. The clip and the email stay in Netlify. With your OK cleared, the clip can appear in Robert’s reels, in boosted posts and on this site, with your first name and handle.

Ride check-in

A page we’re testing (the check-in, not linked from the site yet). It asks the ride, the time, how far from the start you are (rounded), what changed, a line, photos or a clip, your first name and an email you can leave blank. The public review queue gets the ride, the time, the rounded distance, the change and your line, with any links, emails and phone numbers stripped out; a plain “still rolling” opens nothing. Photos, clips and your location never leave Netlify.

Until Oct 9, 2026 the footer had an email signup for mile updates. It’s gone, and the addresses it collected have never been emailed. They sit in Netlify. If yours is one of them and you’d like it deleted, say so (below).

The Fruit Loop RSVP

On the RSVP page for the Fruit Loop (Robert’s Friday night ride). It isn’t a Netlify form: the answer goes to the site’s own small server and sits in Netlify’s storage for the site. Nothing goes into the public review queue.

• Yes or can’t make it: a count for that Friday and nothing about you. No name, no email, no address. Your browser keeps a random number so a second tap changes your answer instead of adding one.
• Maybe, keep me posted: your first name and the email or phone number you give. Only Robert sees them, on a private page. He uses them for one thing: letting you know when rides are coming up, by email or text, himself. Never shared, never sold, never added to anything else.

Location

“Near me” on the ride finder, the city pages and Tonight asks your browser for your position once, sorts the rides by distance on the page, and forgets it. Nothing is sent anywhere. Tonight asks for the weather at each ride’s start, not at yours.

The outside services a page talks to

• Open-Meteo (open-meteo.com): the forecast on the ride briefing, on Tonight and on event pages. Event pages and Tonight send the ride’s or the event’s coordinates. The briefing sends a few points along the route you dropped, rounded, and, when your file has no heights, the route’s points to get them.
• OpenStreetMap: the street maps on route pages are pictures made when the page is built. Your browser never calls OpenStreetMap. The drawn maps elsewhere are the site’s own files.
• Strava: the mile count on the homepage comes from Robert’s own Strava, through the site’s own server. Nothing about you goes to Strava. A Strava link on a ride page is a link and nothing more.
• Google Maps: “Directions to the start” opens Google Maps only when you tap it.
• Instagram: links only. Nothing from Instagram loads on a page.
• Fonts: served from this site. No font request goes to Google.

What this site never does

• No accounts, no logins, no paywall.
• No ad networks, no tracking pixels, no retargeting.
• Nothing typed into a form is sold, shared or used for anything but the ride, the review, the route or the clip it was sent for.
• No email to you from the site. Mile updates go up on Instagram. The only time anyone gets in touch is when you asked for it on the Fruit Loop RSVP.
• No face on the site or in a post without a cleared OK. Only Robert is recognisable in his own photos and video; riders are from behind or far off, and oncoming faces are cropped.
• Nobody’s Strava but Robert’s own is ever read.

Taking something back

Send a DM to @cycl_eforchange and say what it is.

• A review: it comes off the ride page at the next build, usually the same day.
• A “What do you cycle for?” clip: within 7 days our posts with it are deleted, it comes off the site, and any boost stops.
• A form entry, a photo, an old signup address: deleted from Netlify.
• Your name and number or email from the Fruit Loop RSVP: off the list the same day.

Who runs this

Cycle for Change LLC, Phoenix, Arizona. Robert Castan. The site’s code is public at github.com/castan1981-oss/cycle-for-change, including the scripts that move form entries into the review queue, so you can read exactly what moves where. How rides are checked covers the other half of trust: how every fact on the site gets its source and its date.