RollOut

Privacy Policy

This Privacy Policy is effective as of September 25, 2026.

This Privacy Policy describes how RollOut Cycling, LLC (“RollOut,” “we,” “our,” or “us”) collects, uses, discloses, and protects information about you when you use our mobile application and website that provide a scheduling and coordination platform for group bike rides (the “Services”).

By using the Services, you agree to this Privacy Policy.

Direct any questions about this policy or requests about your information to help@joinrollout.com.

1. What You Give Us

To create an account we require your email address, your first and last name, your gender, and your confirmation that you are at least the age of majority in your applicable jurisdiction of residence and accept our Terms of Service and Liability Waiver. We do not ask for your date of birth.

Your last name is never shown to other riders as text. It is used to build your initials and, where a rider has no nickname, a single last initial (for example, "Dave M.") to distinguish multiple riders sharing a first name.

Gender is required, and unlike everything else on your profile, you cannot change it yourself. RollOut supports women-only rides, and that setting is enforced against the gender on your account rather than trusted from the browser. If your gender is recorded incorrectly, email help@joinrollout.com and we will correct it.

Everything else is optional and can be added, changed or removed at any time from your profile: a nickname, a profile photo, the ZIP code we use to centre your ride search, the bikes you own (type, brand and colours), and whether you want email notifications. App notifications are turned on or off in your device’s settings.

2. What You Create By Using RollOut

When you create a ride, we store its date and start time, the meetup place — including its name, full street address and precise coordinates — the distance, pace and ride type, the rider limit, and any notes you write in The Plan. Coordinates are used to place the map, to work out which rides are near a rider, and to determine the ride's own local time zone.

If you attach a route file (GPX) to a ride, or save one to your route library, we store that file as you uploaded it. A route file is a detailed record of a path, and it often begins and ends where the ride begins and ends — frequently at a rider's own home. Treat it as you would any map of where you ride.

Many route files are exports of rides that were actually ridden, rather than routes drawn in advance, and a recorded ride carries more than a shape: the file usually records the date and the time of day at each point along it, which together describe when you were where. We keep the file you gave us, including anything of that kind inside it. What other riders can find is built separately and does not include it — see “What Other Riders Can See” below.

We also store the rides you join, the rides you leave and when, the riders you invite or Rally and their reply, the riders you block, your connections and connection requests, photos you upload to a past ride, up to three saved start locations, and any ride alerts you save — including the ZIP code you chose, the search radius, and the pace, distance, and start-time window that alert covers.

If you arrive through a referral link or a printed card's QR code, we record which link or card it was, so we can tell where sign-ups come from.

In order to run the app, we also store an Apple push token, the APNs environment, and a last-seen timestamp.

3. What We Do Not Collect

RollOut does not track you, and we do not keep a record of where you have been. The app can use your device's location in two places, and only if you allow it: to show where you are on a ride's route and to centre a search on where you are now. In both cases, your location is used on your device and is never sent to us. We do not receive it, we do not store it, and it is never attached to your account.

You are asked for permission the first time it is actually needed — never when the app opens — and only for while you are using the app, never in the background. You can say no, and everything keeps working: you can search by typing a ZIP code instead, and a route still draws without showing where you are. You can change your mind at any time in your device's settings.

Every location we do store is one a rider typed in: the meetup place for a ride or a ZIP code for searching. We never turn your position into a saved trail, a heat map, or a history of your rides. This is a real difference from ride-tracking apps, and it is deliberate.

We do not collect payment information, health or fitness measurements, your contacts, your browsing history on other sites, or your date of birth. We do not sell your information, we do not share it with advertisers, and we do not use it for advertising.

4. What Other Riders Can See

Other riders can see your display name — your nickname if you have set one, otherwise your first name and last initial — along with your profile photo, the bikes you own, and a shop or club badge if your account is set up as one. They can also see the rides you lead and the rides you have joined, and riders you have ridden with may be suggested to you as connections.

Your email address, ZIP code, and full last name are never shown to other riders. Your gender is never shown to other riders, and is never sent to the browser — women-only rides are filtered on our servers, so what reaches your device is a shorter list rather than a list plus everyone's gender.

Photos and profile pictures are stored in a way that makes them readable by anyone who has the file's web address. Those addresses are not listed anywhere and are not guessable in practice, but they are not protected by a password. Do not upload a photo you would not be willing to hand to someone outside the ride.

Route files are handled more strictly than photos, because a route file is a detailed record of where you rode. They are not readable by web address at all. Each time a map is drawn, we issue a temporary link that expires within minutes, and only to someone already entitled to see that ride or that shared route.

A ride marked private is hidden from search and from riders who were not invited to it. That protection covers the ride's details, including its address, and it covers the ride's route file too.

Routes you save to your route library are shared with other riders by default. You can turn off sharing for any route, at any time, from the sharing panel on your Routes page. What other riders can find is the route's name, its length, its ride type, the ZIP codes the shortened copy passes through, and that shortened copy of its shape. They do not receive the file you uploaded, anything recorded inside it about when you rode, or the point where the route actually starts and finishes.

Before a route is shared, we remove the places that would identify where you set out from. Short detours off the road — the kind a driveway leaves behind — are taken out. On a route that returns to where it began, the copy other riders see is turned so that it starts at an arbitrary point along the way rather than at your own. On a route that ends somewhere else, both ends are cut back by an amount that varies from route to route. The length we publish is the length of that shortened copy, not of your ride, so the two cannot be compared to work out how much was removed.

5. Email and Push Notifications

We send email and push notifications for things that happen on your rides: someone joining a ride you lead, a ride you joined being cancelled, a reminder the day before, an invitation to a ride, and a digest of rides matching any alerts you saved. You can turn the emails off from your profile, and app notifications off in your device’s settings.

Two notifications are not covered by that switch, because they are not alerts: a welcome email message when you confirm your account, and a single email note from the founder after your first ride. Both come from a real email address you can reply to.

We use Resend to deliver email; push notifications are delivered through Apple. RollOut does not send text messages.

6. Who Else Handles Your Information

We use a small number of service providers, each of which only handles information to run RollOut, and none of which is permitted to use it for their own purposes: Supabase, which hosts our database, accounts and uploaded files; Vercel, which hosts the site; Resend, which delivers email; Apple, which handles the push notifications; and Google, whose mapping services power address lookup when you create a ride, the ride's time zone, and the small map image in ride invitation emails.

We may disclose information if we are legally required to, or where we believe in good faith that disclosure is necessary to protect someone's safety.

7. Analytics

We measure how the website is used through Vercel Analytics. It records page views along with coarse information such as browser, operating system, and country, and does not use cookies or build a profile of you. These measurements are aggregate and are not tied to your account. The iPhone app contains no analytics at all — it is not built into the app, so nothing about your use of the app is measured or sent anywhere.

We set cookies for limited purposes only: keeping you signed in and remembering that you arrived through a referral link or printed card long enough to attribute your sign-up. We do not use advertising or tracking cookies.

8. Deleting Your Account — And What Survives

You can delete your account from your profile. Deletion is permanent and cannot be undone: your sign-in is destroyed, you can never sign in again, and your email address, nickname, photo, ZIP code, and bikes are removed.

Your name is deliberately kept. RollOut is a record of rides that actually happened, and every past ride shows who led it. Removing a departed rider's name would erase the ride leader from every ride they ever led, for everyone who rode it. Your name therefore remains attached to those past rides. Nothing else identifying you remains, you receive no further email or push notifications, and you are removed from rider search, connections, and the riders-you-have-ridden-with list.

If you lead rides that have not happened yet, we will ask you to cancel them before deleting, so the riders who joined are told rather than left waiting.

If you would prefer your name removed from past rides as well, email help@joinrollout.com and we will discuss what is possible.

9. Your Choices

You can view and change most of your information from your profile at any time, turn email notifications off (and app notifications off in your device’s settings), delete saved ride alerts, and delete your account.

For anything you cannot do yourself — correcting your gender, asking what we hold about you, or asking us to remove something — email help@joinrollout.com. Depending on where you live, you may have additional rights over your information, and we will honour them; tell us what you are asking for and we will respond.

10. Security and Where Your Information Lives

We implement administrative, technical, and physical safeguards designed to protect personal information. Information is stored in the United States. Access is restricted at the database level so that riders can read only what they are entitled to, and we keep backups so the service can be recovered.

No method of transmission or storage is completely secure. You are responsible for maintaining the confidentiality of your account credentials. If a breach affects your information, we will tell you.

11. Minors

RollOut’s Services are not intended for, and we do not knowingly permit use by, minors. You must be at least the age of majority in your applicable jurisdiction of residence to create an account, and you confirm that when you sign up. We do not knowingly collect information from anyone under the age of majority, and we do not ask for anyone's date of birth. If we learn that an account belongs to someone under the age of majority in their applicable jurisdiction of residence, we will close it. If you believe a minor has created an account, email help@joinrollout.com.

12. Legal Bases for Processing - GDPR/UK GDPR

If you are in the EEA, UK, or Switzerland, we process personal data on the following legal bases: (1) performance of a contract (to provide the Services); (2) legitimate interests (e.g., to secure and improve the Services, prevent fraud, and communicate administrative updates); (3) consent (e.g., for certain marketing, cookies, or precise location); and (4) compliance with legal obligations.

13. Changes

We may update this Privacy Policy from time to time. If we make material changes, we will post the updated policy and update the Effective Date, and we may provide additional notice as required by law or at our discretion. Your continued use of the Services after changes become effective constitutes acceptance of the revisions.

14. Contact Us

If you have questions or requests regarding this Privacy Policy or our data practices, contact us at help@joinrollout.com.

See also our Terms of Service & Liability Waiver.