Privacy policy

Last updated November 10, 2026

This policy has not yet been reviewed by a lawyer.

Biiikes helps people discover group bike rides, connect with other riders, and find their community.

We believe you should know what information we collect, why we need it, who can see it, and what you can do with it. That's what this policy explains.

Biiikes is operated by Biiikes LLC, a Washington limited liability company.

Browsing without an account

You don't need an account to explore Biiikes. You can browse the calendar and read about rides without signing in.

We record which pages people visit on our website and when, so we can understand whether the calendar is useful and how people use it.

These visits are recorded using a random identifier stored in your browser, not your name or account. Our page-view records aren't connected to your identity, even if you sign in.

We keep these records for 13 months, then delete them. We may keep anonymous totals, like how many people viewed the calendar on a particular day, indefinitely.

Information you give us

When you create an account or use Biiikes, we collect information you choose to share and information needed to make the service work.

Your account

We collect:

• Phone number and email address: To sign you in, verify your phone number, and contact you.
• Name and username: So other riders can recognize you. Your account holds your first and last name, a ride name, and which of them you want to go by. Other riders see only the name you choose.
• Date of birth: To determine which features and privacy protections apply to you. Older accounts may instead have a record of whether the rider confirmed they were at least 18.
• Language: So we can send emails and text messages in the language of the version of our website you signed up on.
• Terms acceptance: Which version of our Terms of Use you accepted and when. Accounts created before we started tracking versions may not have this record.

We also keep the settings you choose, like notifications, appearance, and quiet hours, and the kinds of rides you've told us you like. For each device where you've turned on push notifications, we keep the code it gave us for sending them.

Your profile

You can choose to add a profile photo, cover photo, pronouns, a bio, and links to Instagram, Strava, or another website.

These are optional and remain blank unless you add them.

Your profile information is visible to signed-in riders, and to anyone if your profile is Public. If you're 18 or older and have given us your birthday, your profile is Public unless you choose Private. Your name and profile photo may also appear in ride attendee lists, depending on who you've allowed to see your attendance.

We store your bio as you write it.

Before a profile or cover photo becomes visible to anyone else, we check it automatically against our community rules, using OpenAI's moderation service. If it doesn't pass, we won't use it, and we'll let you know so you can choose another.

We also create a new copy of the photo without the information your camera saved in the file, such as where and when it was taken or what device you used. That's the copy other riders see.

If you're 18 or older, before we make that copy, we keep a private record of some of what the camera saved: when the photo was taken, the camera and its settings, and a rough area. It appears only in your own download of your information, and other riders never see it. For riders under 18, we keep none of it.

What you post to the Hub, where riders post photos and clips from rides: its words, photographs and clips, who you chose to see it, who can comment, who you tagged, and how you edited it (stickers, text, cut-outs), so we can show it. We keep each photo and clip's details privately, like when and where it was taken. The exact spot is kept only if you turn on "Use your photos' locations"; otherwise it's made approximate. None of it is shown to other riders, and from riders under 18 we keep only what the checks need.

If your profile is public and a ride is set to Everyone, anyone with its link can see it without an account: your name, the date, the route without its start and end or what's in your private zones, the distance, time and speed, the weather, the photos and clips, and the caption. They don't see heart rate or other health numbers, or counts of reactions or comments. A ride matched to a calendar ride you didn't lead stays closed to them.

A ride from your watch, or one that saved itself after 24 hours, goes to the Hub without you opening it, with whatever you'd already added. This is on unless you turn it off, under Posting in the app's Settings or on the Hub's settings page on the website. With it off, the ride stays out of the Hub until you tap Post it, but its page still shows to anyone its audience allows. Rides you import don't post themselves, and rides from Strava stay private to you.

Private notes on a ride are for you alone. They don't go on your card, in a share, to Strava, or on any public page, and we don't quote them in a report. They're in your data download and are deleted with the ride.

Comments. We keep your comment's words, up to 1,000 characters, which post it's on, when you wrote it, and hearts on it. Only the people who can see the post see your comment, and never anyone who isn't signed in. You or the poster can delete it, and then it's gone, unless someone reported it (see "How long we keep information"). If you block someone, their comments on your posts are hidden until you unblock them. Only you see who hearted your comment.

Reposts. We keep who reposted which post, and when. Your followers see your repost, and the poster sees that you reposted it. A repost is removed if the poster narrows who can see the post or deletes it, and hidden while the poster has you blocked.

Bookmarks. They show in a Bookmarks row on your own profile, and only you see them. Not even the poster knows.

Reactions. We keep who reacted to a post and with which of the five reactions. Anyone signed in who can see the post sees the counts and who reacted, leaving out anyone they can't see: a private profile or a rider under 18 they don't follow, and anyone they've blocked or who's blocked them. The poster sees everyone who reacted, except anyone they've blocked or who's blocked them. Someone who isn't signed in sees the counts but no names. Reactions, and comments from riders 18 and over, help decide which posts the Hub shows first. A reaction from a rider under 18 is counted but doesn't change that.

Cut-outs. When you lift a subject out of your photo, your phone finds it and sends us an outline of it with your edit. We cut it from the photo you uploaded. We don't use face recognition.

Suggestions. On phones that can, your phone writes a caption or description suggestion itself, only when you tap Suggest. Nothing about the photo or ride is sent to us or anyone else to make one (on Android, see Google's ML Kit under "Companies that help us run Biiikes"). The website doesn't offer them, and they're off for riders under 18.

Your rides

We keep track of:

• Rides you say you're going to.
• Rides you've attended.
• Rides you've saved because you might go.
• Who you've ridden with, which helps provide trust signals between riders.

Rides you've saved show under Saved rides on your profile, for anyone who can see it. An app or assistant you've connected to your account may also access them if you've given it permission.

You control who can see that you're going to a ride. Your choices are:

• Only you
• Close friends
• Riders you've ridden with
• Followers
• Everyone

Who can see you're going starts at Everyone.

Other riders aren't told which audience groups you've placed them in.

If a ride happens regularly, we'll remember your last visibility choice for that ride and use it for the next date.

Rides you record

In the Biiikes iPhone and Android apps, you can record a bike ride. The website doesn't record rides, but you can see your recorded rides there and download them.

When you record a ride, we keep it: the line you rode on the map, when you rode it, and its numbers, like time, distance, speed and climb. If you have no signal, your phone keeps the recording and sends it to us once it can. You can edit or delete any ride you've saved. If you choose Stop without saving, the ride is discarded.

When you crop a ride, we keep the parts you cropped off, stored with the ride, so you can put them back. Nobody else sees them, and they're deleted when you delete the ride. If you already sent the ride to Strava, Apple Health or Health Connect, their copy doesn't change.

If you set goals, we keep them with your account: the kind of goal, whether it's for a week or a year, and the number. Only you see them. They're deleted when you delete your account.

If the ride you recorded is one on the calendar, we can mark that you went. A ride you start from its page is matched already. Otherwise, the summary after your ride asks whether it was that ride.

You can tag a friend on a ride you recorded. We keep who tagged whom, on which ride.

You choose who can see each ride you record. If you've told us a birthday that makes you 18 or older, it starts at Everyone. If you're under 18 or haven't told us your birthday, it starts at Only me. After your first saved ride, we ask what your usual choice should be, and you can change it on any ride. A ride's distance, time, speed and climb are seen by the same people who can see the ride. Your heart rate, calories, power and cadence are seen only by you unless you choose to show them. Rides you bring in from other apps and services start at Only me. Your private zones always apply to your recorded rides on Biiikes.

We work out personal bests, like your longest ride or most climbing, from your own rides only. "Show my personal bests" is a privacy setting and it's on unless you turn it off. Someone looking at your profile sees bests only from rides they're allowed to see.

Wind shows whether you're riding into a headwind or with a tailwind. While you record a ride with Wind among the numbers on your recording screen, your phone sends Biiikes a rough area, a square about a mile and a half across, not your exact location. We use it to look up the wind forecast from the National Weather Service. Your phone sends it only while you're recording, including rides you don't share live, and never while you're inside one of your private zones. We don't keep the area with your account or write it in our logs, and your phone never contacts a weather company itself. To stop it, remove Wind from your ride screens. If you're under 18, you get Wind only when recording is open to you.

You can also upload a GPX or FIT file of a ride from the website. We keep an uploaded ride the same way as one you recorded.

Health numbers

A recorded ride can include health numbers: heart rate, calories, power and cadence. They're seen only by you, unless you choose to show them on a ride or turn them on for every ride. Deleting a ride deletes its health numbers too.

When you pair a sensor, we add one to a daily count, so we know which sensors riders use with Biiikes. The count records the kind of sensor (heart rate, power, speed, cadence, or speed and cadence), its brand and model as the sensor reports them, its firmware version if it reports one, whether you paired it to your phone or your watch, whether your phone is an iPhone or Android, and whether it connected or failed. That’s all. It never includes a serial number, a Bluetooth identifier, your account, your device, a location or a health number, so a count can’t be tied back to you. We keep these counts indefinitely. We don’t count sensors paired by riders under 18, or by riders in the EU, the European Economic Area or the UK. The sensor itself is remembered only on your phone.

Your connections

We keep track of the riders you follow, the people following you, and the riders you've marked as Close friends.

Your Close friends list is private. Nobody is told you've added or removed them, and adding someone doesn't give you access to anything they haven't chosen to share with you. Nobody else can see how many Close friends you have.

If someone asks to follow your private profile, we keep the request until you respond.

If you accept, we'll tell them. If you decline, they won't be notified.

If you've confirmed an email address, emails about follow requests start on. Every email has a link to turn that kind off, and you can also turn them off under Settings › Notifications and sound.

What you chose the Hub, your column of posts and updates, to show: which kinds of update and in what order. We also keep how far you have read, as one date and time that is overwritten whenever you read further, so that we can tell you what is new on any device. It is not a list of what you read, and we do not record which items on the Hub you were shown or which you opened.

Invitations

When you share a Biiikes link, it may contain a code that identifies you to Biiikes without revealing your name or username.

If someone opens your link, their browser remembers that code for 30 days. If they create an account during that time, we can record that you invited them and which ride's link they followed.

We don't record invitation relationships when either person is under 18 or hasn't told us their age.

Your location

Biiikes can use a location you choose to help you find rides nearby, estimate distances, and find nearby Biketown bikes, and, while you record a ride, to record it and share it as you choose.

You don't have to provide one.

Where you ride from

You can choose a neighborhood, park, street corner, or other place as your starting point. You can also provide a street address or choose an exact point on a map.

As you type, we suggest neighborhoods, parks, and other places from information we keep ourselves. Your search for those suggestions isn't sent to another company.

If you enter a street address, our server sends it once to the US Census Bureau's geocoding service to find its position on a map. We don't send your name or account information, and we don't keep the request.

For a street corner, our server finds its location in a table of corners we build each month from OpenStreetMap's data and keep on our own server, so looking it up sends nothing to OpenStreetMap or any other company. If your city's table isn't loaded yet, our server asks OpenStreetMap for the corner and saves the result by street names, so we don't need to look up the same corner again.

The map images you see are delivered through Cloudflare, which also helps deliver the Biiikes website.

We store:

• A point on the map for a street address, rather than the address itself.
• The name of a selected park, corner, place, or neighborhood.
• The neighborhood containing your location.
• Whether you typed the location, chose a suggestion, or used your device's location.

The point on the map and the name of the place are encrypted. The neighborhood, and whether it's a park, corner, or other kind of place, aren't. What you type isn't written to our logs.

Using your device's location

Your phone or browser asks before we can use your location, and we ask only when you choose something that needs it, like Near me, From here or Use my location. Once you've allowed it, the phone apps also use it without asking again, to put nearer places first when you search and to start ways from where you are. They also find where you are as soon as you open a ride's page, so the ways to it are ready. Your location stays on your phone until the Getting there card is on screen or you open the ways sheet. If you haven't allowed location, the app doesn't ask and doesn't check where you are. On Android, the app also reads it when you open search, without asking.

For adults with precise location enabled, we can save the exact location returned by the device as the place they ride from.

When precise location is turned off, we save only the neighborhood.

When you use Near me in search, your location is rounded to about 100 meters, the same as for Biketown bikes. We use it to find rides near you and, in the phone apps, to put nearer places first when you search for a place. We don't save or log it on our server.

Your starting location is never shown to other riders.

If you've told us a birthday that makes you 18 or older, your neighborhood shows on your profile once you've given one as where you ride from. Only the neighborhood shows, never a street address or corner. If you're under 18 or haven't told us your birthday, it starts off. You can change this in Settings, beside where you ride from.

You can change or delete your starting location at any time from your account page or Settings.

Searching for a place

When you search for a place, what you type goes to our own server, which looks it up in open map data from OpenStreetMap and Overture. It isn't sent to another company, except for a complete street address and Search in Maps, described below. Rides that match show first, and places show under them. In the phone apps, if you've allowed location, your phone rounds it to approximately 100 meters and sends it with the search, so we can put what's near you first and show how far each place is in a straight line. We never use your home for this. Opening search doesn't ask for your location. On Android, if you've already allowed location, the app reads your phone's location when you open search, to put nearer places first; it doesn't ask you anything. On the website, place search never uses your location, even after you click Use my location. With location off, and on the website, places are listed by how well their name matches what you typed, then by how near they are to the middle of the city. For place search, we don't keep or log what you type, your location, or the results. The same words also search rides, and when a word matches no ride we may keep that word, with no account or device attached. On the website, what you type also shows in the page's address. What we keep about place searches is a daily count of finished searches, split by whether they found a place, found none or couldn't reach the map data, and by the kind of the first place, with no account or device attached and never the words. The phone apps also count which result you open, by its rough position in the list and its kind, never the words or the place.

Addresses and street corners are looked up by our own server as you type. Our address list comes from Overture. Our street corners come from a table we build each month from OpenStreetMap's data and keep on our own server, so looking up a corner sends nothing to OpenStreetMap or any other company. If a city's table isn't loaded yet, our server asks OpenStreetMap for the corner and saves the result by street names. If what you type is a complete street address that our own list doesn't have, our server sends it once, after you stop typing, to the US Census Bureau's geocoding service to find where it is on the map. We don't send your name or account information, and we don't keep the request.

When nothing matches, Search in Maps sends the words you typed to Apple Maps on iPhone, to your phone's maps app or Google Maps on Android, or on the website to Google Maps in a new tab. Nothing is sent until you tap it. Open in Maps hands your maps app the place's point on the map and the place's name as it shows on our map, never the name you gave a saved place. For a saved place with no name on our map, like a pin you dropped, it sends only the point.

If you save a place, we keep it on your account on our server, encrypted, with the name you give it. Only you see your saved places. They're in your data download and are deleted with your account, and Remove deletes your name and pin for a place for good; the place itself stays on the map. Your saved places aren't stored on your phone, so without a connection Your places shows only Home. Saving a place doesn't hide anything. Only a private zone hides where a recorded ride starts or ends, and a ride to a saved place records and can be shared like any other ride. A saved place has no Share, and the name you give it never leaves your account. Home in Your places is the home you marked as a private zone, and you change it in Settings under Private zones.

We limit how many searches and ways can be asked for in a short time. We count them per connection, per account and per internet address. We hold your internet address only as a scrambled code, in memory, and never write it down. The code changes each time our server restarts. If you reach the limit, try again shortly; rides still show.

Finding nearby Biketown bikes

When you tap Use my location on a ride page to find nearby Biketown bikes, your browser rounds your location to approximately 100 meters.

We use that location while the page is open to find nearby bikes. We don't save or log it, and we don't send it to Biketown or another company.

If you've saved a starting location, our server can also use it to find nearby Biketown bikes without sharing that location with Biketown.

Ways to a ride

To show you ways to a ride or a place from where you are, we need your location. Your phone or browser rounds it to approximately 100 meters and sends it in one request to our own server, which runs our own routers. When ways start from where you are, the phone apps keep looking for a more exact location for a few seconds after the ways show. If that moves your start by more than about 150 meters, your phone rounds it the same way and sends it in one more request, to get the ways again and the drive time if one is showing. We use each one only for that request, and we don't write it to a log, the database, a cache or a measurement. We don't send your location to any other company to plan a way. On the website, we don't ask for your location until you tap Use my location. For ways, your phone asks for permission to use your location only when you tap From here or Use my location. If you've allowed location and we can find you, ways start from where you are. If not, we don't plan any until you pick where you're starting from. A way starts from your home only when you tap From home. A way can also start from one of your saved places, or from a place, address or corner you search for. A start you pick is used for that one request and kept nowhere, and a saved place's name on the start chip is seen only by you. Ways to a place have no drive time: we don't ask Mapbox or any other company about a place, and the Drive row offers only Open in Maps. The drive time paragraph below applies to rides only. A ride's drive time is asked for only from where you are or your home.

When you tap From home, the way starts at the home you marked as a private zone in Settings. We read your home for that one request and don't keep a copy from it. The way is drawn for you alone, and nobody else sees a way. The drive time is separate: whenever you're signed in and a ride's Getting there card comes into view, or the ways sheet opens, our server sends another company, Mapbox, your starting point, rounded to approximately 100 meters, with no account or ID. That starting point is your home, and we don't ask before sending it to Mapbox.

Whenever you're signed in and a ride's Getting there card comes into view, or the ways sheet opens, and there's a starting point to use, our server asks another company, Mapbox, how long the drive is. This happens on every phone and on the website. We don't ask first, and there's no setting to turn it off. Our server sends Mapbox your starting point, rounded to approximately 100 meters, the meeting spot and, when it's still ahead, the ride's meet time. If your phone sends a corrected start, our server sends it to Mapbox once more, rounded the same way, with no account or ID. We only do this when you start from where you are, or from your home after you tap From home. From a saved place or a place you search for, the Drive row shows Open in Maps with no drive time. We don't send your account or an ID, and the request comes from our server, so Mapbox doesn't get your own internet address. Our server doesn't log your starting point or keep it, and it doesn't keep the answer. If you're signed out, this doesn't happen. If Mapbox has no answer, the row says only Drive with Open in Maps.

Send to phone shows only when you're signed in to the Biiikes app on a phone. Tapping it sends one notification to the phones where you're signed in, not to this browser. For a ride, it names the ride. For a place or a point on the map, it names that place, like NE 15th at Broadway. Either way, it names the kind of way, like Calmest or bike and bus. It never includes where you're starting from. It has no route line, no minutes and no leave-by time, and it doesn't say whether you planned from home. For a place with its own page on Biiikes, the notification's link names that place by its ID on Biiikes. For any other place or point, the link holds where it is, rounded to about 10 meters (33 feet). When you open the notification, the way gets planned again from where your phone is, so its numbers can differ from what you saw on the website. If location's off on your phone, nothing is planned until you tap Use my location. Your browser's location is never sent to your phone. We store nothing about a sent way except the notification itself, which you see in your notifications. For a place or a point, we remove its ID or where it is from the notification after 24 hours, and the notification opens the map instead. Its name stays. There's no setting to turn it off: it sends only when you tap Send to phone, and it reaches your phone even during the quiet hours you set in Biiikes, because you just asked for it.

While turn-by-turn directions run and nothing is recording, the app uses your location with the screen off and on the lock screen. It does this only while that route runs. All the way there, the screen says it isn't recording, and nothing from the route is saved. On Android, a notification also stays up saying it isn't recording.

Record your ride there is a switch above Start route. On bike ways it's on the first time, then stays as you left it. On bus and train ways it starts off, which doesn't change what's remembered for bike ways. With it on, your ride there records like any other ride. Arriving doesn't end the recording, and if you never tap anything, it's one long ride. When you finish, the usual posting screen opens. If your ride there ends at the meeting spot, its audience starts at whichever reaches fewer people: your usual audience or who can see that you're going. You can change that right there. So your ride there can reach the Hub before the group ride has happened. If you start recording the group ride while your ride there is still recording, your ride there ends, the group ride records from zero, and the two stay separate. Your ride there then doesn't post, whatever Post rides I don't finish on my phone says. It waits on its own page with Post it and stays out of the Hub until you post it. After you post the group ride, you'll see one reminder that your ride there is waiting.

When you get within 300 feet of the meeting spot, the app shows a small line saying you're here. On a locked phone, you get one notification per ride saying the same thing. This happens only if you started with Start route, or you're going to a ride that starts within an hour and you're recording. Your phone works it out, and no location leaves your phone for the line or the notification.

Recording a ride

When you record a ride in our iPhone or Android app, the app uses your phone's location from the moment you start until you finish. The first time, the app explains this, then your phone asks to share your location while you're using the app. Biiikes asks for your location all the time, or for Android's background location, only if you turn on Location when a ride rolls in Settings, and you don't have to. Apart from that one check, described under Notifications, the app uses your location with the screen off only while you're recording or a route you started is running.

Private zones

A private zone is a circle you set around a place like home or work. It reaches an eighth of a mile, a quarter, a half or a whole mile from its center. On Biiikes, other people never see your line inside it. We move the circle's edge by a fixed random amount, so it doesn't point at your door. Each zone is named by its neighborhood.

On Biiikes, the start and end of every ride you share are always hidden. If you haven't set a zone, we trim them for you. "Hide the line inside zones, mid-ride too" is on unless you turn it off, and it also hides any stretch of a ride that passes through one of your zones.

If you start or end rides at the same place five times in 30 days, we may suggest a zone there. You can accept or say no. For each place you say no to, we keep a scrambled code, not the place itself, so we don't suggest it again.

Sharing where you are while you ride

While you're recording, you can share where you are, live. You can send a private link to people you pick. It opens in any browser and doesn't need an account. You can also share with your Close friends or your followers. You choose who you usually share with once, and you can change it on each ride. Until you choose, it's only the people you send a link to.

We keep a list of the people you send links to: the label you gave each one, and their username if they're on Biiikes.

Everyone you share with sees where you are now and when that last updated, your trail so far, your name and profile photo, your speed, how far you've ridden, your phone's battery level, and the route if you're following one. If you lose signal for 2 minutes, they see where you lost signal and how long ago.

Your location updates about every 5 seconds while you're moving, every minute while you're stopped, and every 2 minutes when your battery is low.

Every link stops working when your ride ends, including any copy someone forwarded. Until then, anyone who has the link can see where you are, and we can't tell who that is. Share it only with people you trust. You can end one link, or stop sharing, at any time.

While you share, the recording screen shows who's looked, like "Viewed by Alex, Sam and 1 link". Close friends and followers who look are named. Someone who opens a link isn't named; we count that link as opened. So if you look at someone's live location on Biiikes, they see your name. We keep the list of who looked until sharing ends, and one day more.

If you've set private zones, people you share with still see you inside them, because you picked them.

Your live location is held only in the memory of a server that never writes it to disk. Each position expires on its own within hours, it isn't kept after you stop sharing, and it's never written to our logs. The ride you record is kept as described in "Rides you record".

Where a ride is while it's rolling

When a group ride is rolling, its page and the calendar's map can show one moving dot for where the group is. The dot is made by combining the riders sharing with that ride, and it doesn't show anyone by name. It's exact: if only one rider is sharing, the dot is exactly where that rider is. The ride page also says in words where the group is, like "near SE Ankeny & 12th".

You help make the dot only if you said you're going, you're 18 or older, and you turn on "Help show where the ride is" for that ride. It's off unless you turn it on, and it ends with the ride. You stop helping make it if you're about half a mile from the group for 3 minutes. If you've set private zones, you also stop while you're inside one.

Only signed-in riders see the dot. Someone you've blocked sees it without you, and sees no dot if you're the only one sharing. The dot starts at the meet time, or at the roll time if the meeting spot is secret. The ride leader, or someone on the Biiikes team, can turn it off for a ride.

After the ride, the path the dot took shows on the ride's page as "The route they rode", to signed-in riders, and it's kept with the ride. With it, we keep an encrypted list of which riders made each part of it, so blocking and deleting an account can reach it. A part that only you made is hidden from people you've blocked, and deleted if you delete your account.

If you're running late, Catch up in our apps starts recording your ride and shows a route to the group and how many minutes it'll take you. To work out the route, your location is sent to our own server, which runs our own router. It's used for that one route and isn't stored or logged, and it isn't sent to any other company. If the route can't be worked out, the app shows how far away the group is and in which direction, and your phone works that out. The ride you record is kept like any other. If you open Apple Maps or Google Maps to catch up, the group's spot is handed to that app as where you're going. On the website, Show where I am asks your browser for your location once and works out the direction in the page. Your location isn't sent to us or stored. After you catch up, the app asks once whether you'd like to help show where the ride is. It never turns on by itself.

When you tap Back to the route, Take me home or Back to the start while you're recording a ride in our apps, your location is sent to our own server, which runs our own router, to work out a way by the streets. Back to the route also sends which of your saved routes you're following and how far along it you left it. Back to the start also sends where your ride started. Take me home goes to the private zone you've marked as home in Settings › Private zones. Our server already keeps that zone, and it reads the zone's center for that one request. What's sent is used for that one way and isn't stored or logged, and it isn't sent to any other company. If the way can't be worked out, because there's no signal or our router doesn't answer, the app draws a straight line, and your phone works that out. If you open Apple Maps or Google Maps from there, it gets where you're going. None of this changes what anyone else sees of your ride or your private zones. If you're under 18, these three buttons aren't available yet.

Turn-by-turn gives you directions while you follow one of your saved routes in our apps. If you've been well off the route for about 15 seconds while you're recording, the app finds you a new way that rejoins the route further ahead. That timing can change. To find it, the app sends four things to our own server, which runs our own router: your location, which saved route you're following, how far along it you left it, and which of your bikes you're riding. It also sends a fifth thing, the direction you're moving, so the new way starts in the direction you're already riding. If you're stopped or barely moving, it doesn't send a direction. Your location and the direction you're moving are used for that one new way. They aren't stored or logged, they aren't attached to your ride, and they aren't sent to any other company. The app sends all of this again only if you leave the new way, or if it couldn't find you one and tries again a minute later. Tapping × on the directions banner stops this until you're back on the route. With no signal, nothing is sent, and the app keeps telling you you're off the route. Getting a route's list of turns sends only which route and which bike, not your location. While Turn-by-turn is on, Back to the route, Take me home and Back to the start give you directions turn by turn too, from the same router. They send what the paragraph above says, and which of your bikes you're riding. They don't send the direction you're moving. None of this changes what anyone else sees of your ride. If you're under 18, Turn-by-turn isn't available yet.

How we understand and improve Biiikes

We collect a limited amount of information about how people use Biiikes so we can find problems, improve features, and understand what's useful.

We don't sell this information or use it for advertising.

Different measurements have different privacy protections.

Website visits

We record which pages people visit on the website using a random browser identifier that isn't connected to their account.

We record the page address without anything after the question mark, so information in a page's query parameters isn't included.

These page-view records are deleted after 13 months. Because they aren't connected to your account, deleting your account doesn't delete them.

Notifications

If you're 18 or older, we record which notifications you open from your notifications list in Biiikes, so we can understand how notifications are used. We don't record this for riders under 18 or riders who haven't told us their age.

Unlike anonymous website visits, notification opens are associated with your account.

Records of turning notifications on and off, if your account is 18 or over. We keep these so we can see which kinds riders turn off, so we send fewer of the ones they don't want. Each time you turn a kind of notification on or off in Settings, like ride changes, reminders, weather or new rides, we keep a record of which kind it was, whether you turned it on or off, whether it was the phone or the email switch, when you did it, and whether it was on the website, the iPhone app or the Android app. We don't keep them from an assistant or another app you've connected to your account. We don't keep them for an account under 18 or one that hasn't told us its age, and we don't keep them from the EU, the EEA or the UK.

General account activity

For riders aged 18 or older, we keep a daily record of whether they used the website, iPhone app, or Android app.

We record only the date and platform, not every action taken that day.

We also keep the last date you used Biiikes and count how many eligible riders used the service each day.

We don't collect these account-level usage records for riders under 18 or riders who haven't told us their age. Those accounts aren't included in the daily activity totals.

Ride and social activity

For riders aged 18 or older, we also record certain actions to understand how the calendar and social features are used.

These include:

• Saying you're going to a ride, changing your mind, or marking a ride as attended.
• Saving or unsaving a ride.
• Following or unfollowing someone.
• Requesting to follow a private profile.
• Accepting a follow request.
• Using the website to share a ride you're going to.
• Posting, commenting, reacting, reposting, bookmarking, tapping Not interested, or muting someone on the Hub. For a post, we record its kind (a ride recap, photos or words) and who it's shown to. For a reaction, we record which one.
• Reaching Finish on a ride you're recording, with its length and moving time in rough ranges, or discarding it instead of saving it. Posting a recorded ride to the Hub, with who it's shown to, whether it had photos and roughly how many, and whether it had a caption. Deleting a recorded ride, cropping its ends, splitting off a copy or joining one back, or taking yourself or a photo out of a group recap.
• Adding a route from a file, saving a copy of someone's shared route, making a link to a route, or putting routes in a collection.
• Asking for directions to a ride or a place, a reroute while you follow a route, or directions back, and whether we found any.
• Tapping Send to phone, with whether it went to a ride, a place or a point on the map, the kind of way (like Calmest), and whether it was sent, found no phone you're signed in on, or was refused, but never which ride, which place, or where it is.
• Saving a place to Your places or removing one, and whether you did it after tapping the place in search or on the map, or from Your places.
• Setting a ride goal, with its kind and whether it's weekly or yearly. Adding a bike to your bike shed, or making a passkey.
• Disconnecting a ride app like Strava, or sending or resending a ride to Strava.
• Opening a notification from your notifications list, and what kind it was, like a ride change or a new follower.

Depending on the action, we record when it happened, whether it came from the website or an app, the relevant ride date, and the country the request came from.

For follow activity, we don't record who the other person was in these analytics records.

These records never include what you wrote, your photos or who you tagged. They don't say whose post it was or who you muted. They don't include the path a route takes or the places on it, where you were when you asked for directions or where you were going, a health number like heart rate, or a goal's target. They don't say which place you saved or removed, its name, the name you gave it, its pin or where it is, or what you searched for. Renaming a saved place or moving its pin isn't recorded.

These measurements are separate from the information needed to make your ride history, attendance, and social connections work.

We don't collect this additional activity information for riders under 18, riders who haven't told us their age, or riders in the EU, EEA, or UK. We also don't collect it from third-party apps or assistants connected to Biiikes.

Records of which parts of your profile you save, if your account is 18 or over. We keep these so we can see which parts of a profile riders fill in after joining. Each time you save a part of your profile (your name, pronouns, bio, Instagram, Strava, another link, your profile color or what you bring), we keep a record of which part it was, when you saved it, and whether it was on the website, the iPhone app or the Android app. We don't keep what you wrote or chose. These records don't show on your profile. We don't keep a record when you change who can see your profile or your rides, or when you change your photo, cover or username. We don't keep them from an assistant or another app you've connected to your account. We don't keep them for an account under 18 or one that hasn't told us its age, and we don't keep them from the EU, the EEA or the UK.

For riders aged 18 or older, we count how many recordings are started and finished, with each ride's length and duration sorted into broad ranges. These counts never include a location or a health number. We don't keep them for riders under 18 or riders who haven't told us their age, or from the EU, the EEA or the UK. We keep them like the other activity measurements described here.

We also count how often riders turn on live sharing, on the same terms. Separately, we keep a plain total of how often live links are opened, with no account attached. None of these counts include a location.

We also count how many connections riders make to other ride apps, on the same terms.

Sometimes we try two or three versions of one part of the app with different riders, to learn which works better, then keep that one or the original. Right now that's the picture you share of a recorded ride and the summary after a ride: for example, whether the picture shows biiikes.com, or whether a ride where you set a personal best shows that best as the big number on its summary. We never test a ride's time, place or whether it's cancelled, who can see you're going, your privacy settings, safety, reporting or blocking, accessibility, or anything for riders under 18. If your account is 18 or over, you may be put in one version, and you'll see the same one on every phone and visit while the test runs. We don't tell you which one you're in, and nobody is charged or shown ads for it. When you share a picture of a ride, or open a ride's summary within an hour of finishing a ride where you set a personal best, we keep which test it was, which version you saw, when, and whether it was on the website, the iPhone app or the Android app. Each picture you share also notes which version it was shared with. To compare versions, we count how many new riders joined through a link someone shared and said they're going. We don't keep who you shared with. Only Biiikes' admins see the results, as totals for each version, with no names and never for a group under 20 people. We don't put riders under 18, riders who haven't told us their age, or anyone from the EU, the EEA or the UK in a test, and we record nothing about them for tests. Which version you're put in is deleted when the test ends, and the record of each time you were shown it is kept like the other activity measurements described here.

Joining Biiikes

We want signing up to be simple, so we measure where people finish, skip, or leave the process.

We count how often each joining screen is shown, completed, or skipped, grouped by day and screen version. A screen shown to the same person twice in one day counts once.

These totals contain no names, accounts, or identifiers that connect them to an individual.

For riders aged 18 or older, we may also record which joining screens they finished, when they finished joining, and which version of the screens they saw.

We never keep what someone typed or selected on a joining screen as part of these measurements.

We don't collect these individual joining records from riders under 18, people whose age isn't known, or people in the EU, EEA, or UK.

Separately, we record how far each visit gets through joining and signing in, under a random identifier for that visit or one your browser keeps for 30 days. These records include people of any age. They aren't connected to an account, except that an adult's sign-in steps are kept with their account.

For now, we collect these measurements on the website only.

iPhone and Android app activity

For signed-in riders aged 18 or older, we record which general parts of our mobile apps request information from Biiikes each day.

The parts include the calendar, rides, search, place search, the map, profiles, notifications, settings, sign-in and joining Biiikes. They also include going and following, the Hub, where riders post and comment, stickers, ride recording and ride data, live location, getting to a ride, turn-by-turn directions, routes, bike sensors, and connected apps like Strava.

We keep one record per app area per day. We don't record exactly what you viewed, searched for, or typed.

We don't collect these measurements for riders under 18, accounts whose age isn't known, the website, or third-party apps and assistants.

While app measurement is on, our iPhone and Android apps also record some things about how you use them, whether or not you're signed in. Each time you open the app, we record when the visit started, how it started (for example from a notification, a widget or a link), whether the app was starting fresh or already running, and whether notifications are allowed. When the visit ends, we record how long the app was open, in rough ranges, and how many screens you saw. We also record which screen you opened and where you opened it from. If it's a ride's page, we record which ride and which date it is, by the ride's public web address, never a number from our database. If you tap a widget, we record which widget and its size. If you run a shortcut, like opening a ride or telling Siri you're going to a ride, we record which shortcut. We record whether you allowed notifications when the app asked. To find what makes the apps slow or go wrong, we record how long the app took to start, and which screen it was and how long it took to first show its content after you opened it, both in rough ranges. For now, the screens we time are the calendar and a ride's page. When a screen shows you an error, we record which screen it was and what kind of error, from a fixed list like no connection or a problem on our side, but never the error's wording or what you were doing or asking for.

To learn how the apps are used, we also record some taps, from a fixed list, whether or not you're signed in: opening Getting there (directions to a ride's start); the kind of directions you picked, and whether you opened them full screen; live bus and train arrivals being shown; the place search result you opened (its position in the list, in rough ranges, and the kind of place); where you opened a post from; and opening the share menu, or closing it without sharing. When you open a part of a ride's page, we record which part, from a fixed list like the route, Getting there, the weather, who's going, the schedule or the photos, and which ride and date it was. Each time you use Near me (showing rides near you), we record that you used it, and nothing else: never where you are or what it found. Each time you start sharing a ride, we record how you started: copying the link, opening the share menu, sending a message, posting an Instagram story or saving the ride's share picture. We record this when you start, whether or not you finish, and we never record who you shared with or which ride it was.

If you're signed in and 18 or older, we also record these things. With turn-by-turn directions: starting them; being rerouted (whether you left the route or asked for a new one, and which reroute it was, in rough ranges); getting back on the route; giving up or arriving; and turning spoken directions on or off. With stickers: opening a sticker pack, and placing or removing a sticker (which sticker and its style). With cut-outs: lifting a cut-out (whether you tapped one thing or used Lift all), and removing one. With suggestions: tapping Suggest or Try again (and whether it was for a caption, or for a photo's description for people who use a screen reader), and whether you posted the suggestion as it was, changed it first, or threw it away. When no suggestion was shown, we record why: your phone can't write them, it declined to write one, or it couldn't this time. With cut-outs and suggestions, we never record the words (the suggestion's or yours), the photo, a cut-out's outline, or what you lifted. With recording: pausing a recording, or the recording pausing itself, and showing the ride on your watch, or the watch losing it. We also record when you look at your own ride's summary or a group recap, and which part.

We keep all these records under a random identifier for your app installation. If you're signed in and 18 or older, we also keep them with your account. These records never include what you type, which place it was, a route, where you are, the time you rode, or a health number like heart rate. The apps send nothing for an account under 18, or for one that hasn't told us its age. We don't keep any of these records from the EU, the EEA or the UK.

How the iPhone app is used

Each time you open the iPhone app, it records the visit and the name of each screen you see, like the calendar, a ride's page, Find, a profile, Settings or the bell (your notifications). For a ride's page, it also records where you opened it from, like the map, a notification or Siri, and which ride and date it was, by the ride's public web address. For a profile, it records where you opened it from, but never whose profile it was. It also records which parts of a ride's page you open, that you used Near me, and how you start sharing a ride, as described above. It records how the visit began, like from the Home Screen, a link or a widget. It also records whether the app was already running and whether you allow notifications. It records roughly how long the app was open, like 30 seconds to 2 minutes, and how many screens you saw. A visit ends after you've been away from the app for 5 minutes. It also records the app's version, which iOS you have, like iOS 26, and your screen size, like small phone, large phone or tablet, but never your phone's model.

It never records what you typed or searched for, the wording of an error, where you are, a route, what time of day you rode, or any health or fitness number.

If you're signed out, what it records goes with the app's random identifier only, explained below. If you're signed in and 18 or older, our server connects it to your account. If you're signed in and under 18, or your account hasn't told us your age, the app records nothing and sends nothing. Nothing is recorded from the EU, the EEA or the UK.

The app keeps what it records on your phone for a short time, then sends it in batches to our own servers and nowhere else. No other company gets it, including any analytics or advertising company. It never sends anything older than 7 days, and it holds no more than 1,000 records. If we turn this off on our side, the app stops right away and deletes what it was holding.

When you tap a Biiikes widget, the app records which kind it was: your next ride, or tonight's rides. When one of our Siri or Shortcuts actions runs, like “I'm going” or “Tonight's rides”, it records which action it was. It doesn't record which ride.

The app also records how long it took to open, as a rough range like under a quarter of a second or 1 to 2 seconds, and whether it was already running. It records which screen it was and how long it took to first show its content after you opened it, in rough ranges from under a quarter of a second to more than 4 seconds. For now, the screens it times are the calendar and a ride's page. When a screen shows you an error, it records which screen and what kind of error it was, like no connection, a problem on our side or the map didn't load, but never the error's wording or what you were doing or asking for.

If you're signed in and 18 or older and you tap a Biiikes notification, the app records that you opened one and what kind it was, like a ride change, a reminder, the weather or a new follower. It doesn't record the words or which ride.

When your iPhone asks whether to allow notifications from Biiikes, the app records your answer: allowed, not allowed, allowed quietly (delivered without a sound or banner), or closed without answering. That's recorded when you're signed out too, but never for an account that's under 18 or hasn't told us its age.

We keep all of this until you delete your account, and no longer than 25 months. From a signed-out app, we keep it 13 months, or up to 25 months once it's connected to an adult's account.

Browser and app identifiers

Each browser and app installation has a random identifier.

We use it to measure which days Biiikes is used, including when nobody is signed in.

For adults, we can associate these identifiers with their accounts. This helps us delete related activity records when an account is erased, including records created before signing in.

If two adults use the same browser, deleting either account also deletes the activity records associated with that browser.

We don't associate these identifiers with accounts under 18 or accounts whose age is unknown, and we don't record activity days for those identifiers while such accounts are signed in.

Because we don't know the age of someone who isn't signed in, anonymous browser and app activity may still be recorded before they sign in.

iPhone and Android crash reports

If the Biiikes Android app crashes, freezes or is closed by the phone to free up memory, it may send us a report the next time you open it.

On an iPhone, Apple's own system hands our app a report about an earlier crash, or a freeze (when the app stopped responding). That usually happens the next day or the next time you open it, and the app then sends us the details listed below.

Reports are sent only if you're signed in and have confirmed you're at least 18.

We don't collect crash reports from younger riders, people whose age is unknown, or people who aren't signed in.

The report contains:

• What kind of problem it was, like a crash or a freeze.
• A scrambled fingerprint of where in our code it happened.
• Which Biiikes app sent it.
• The app version.

We don't keep an account or device identifier with a report, so we can't connect it to you.

We use these reports only to fix problems. We don't share them or use them for advertising.

Calendar subscriptions

If you subscribe to your rides through a calendar app, we count how many calendar subscriptions are in use.

Each calendar link counts once per week, no matter how frequently an app fetches it.

The link is processed in memory without being written to our records. We keep only the total number of subscriptions.

This count includes subscriptions from riders of any age.

Search

We don't keep a personal search history.

We count how many searches are made and how many return no results, without attaching those counts to an individual.

When you finish typing a place search on the map, we also count whether it found a place, found none or couldn't reach the map data, and what kind of place came up first in the results, like a bike shop, a cafe or a street. In the phone apps, we also count which result you open, by its rough position in the list and its kind. These counts never include the words you typed, where you were, or which place it was, even when a search finds nothing. These place search counts have no account or device attached, and include riders of any age.

When a search returns no results at all, we may keep the search words to understand what's missing from Biiikes. We don't attach an account or device to them.

Your searches aren't used to influence suggestions shown to other people.

Stickers

When you add stickers to a photo, our server draws each sticker the photo editor shows you. Each day we count how many of each sticker were drawn, like a ticket sticker for the ride, the weather or the distance, and in which color. For a sticker from a pack, we count only which pack it came from. We also note whether the sticker was drawn on the website, in the iPhone app or in the Android app. The count has no account, device or ride attached, and it never includes your photo. This count includes riders of any age.

Counts without an account

We also count how often shared route links are opened, how often a passkey sign-in works or doesn't, and how often signing up stops because the birthday entered is under 18. These counts have no account attached, and we don't keep anything about the person or the birthday. They include people of any age.

Notifications and reminders

Biiikes can notify you about rides, people you follow, weather, and account activity.

You can manage most notifications and how you receive them in Settings.

A comment on your post, a reply to your comment and a repost of your post each send you a notification in Biiikes, and can reach your phone and your email. Each has its own setting, and they're on unless you turn them off. A mention in a comment uses your Tags setting.

Ride and weather notifications

You can choose weather conditions that matter to you, such as how much rain or cold is too much.

We use those preferences to notify you about weather affecting rides you're attending or have saved.

Your preferences don't affect what anyone else sees.

If you choose Use the defaults, we delete your custom weather preferences.

We also remember which weather notifications we've sent for each ride date so you receive no more than two: one when the weather turns bad and another when it clears.

If you're going to a ride and aren't recording it, we send you a notification about 10 minutes before it meets, and another when the ride has rolled and someone's sharing where it is. These are Ride starting notifications. They're on unless you turn them off in Settings. Nothing checks your location to send them unless you turn on Location when a ride rolls, described below.

If you'd like, the notification when a ride rolls can say how many minutes away by bike the group is. To do that, the app checks where you are once, when the ride rolls, even if the app isn't open. It only happens for a ride you said you're going to, between when it meets and when it's listed to end, and only once per ride. Your location is sent once to our own server to work out the route. We don't store it or write it to our logs. It needs your phone's Always location permission on iPhone, or Allow all the time on Android. Everything else works without it. Riders under 18 are never asked and never get it. Settings shows whether it's on, and you can change it in your phone's settings.

Sign-in alerts

When a new device signs in to your account, we notify your other signed-in devices through Biiikes.

We also send a push notification if push notifications are enabled, and an email if you've confirmed an email address.

These alerts don't identify the person, device, network address, or location involved.

Sign-in alerts are always enabled and can't be turned off. We keep a record of the alert and when it was sent.

Notifications for younger riders

We don't send riders under 18 messages intended simply to bring them back to Biiikes.

Notifications that someone new has followed them start off.

Younger riders can choose to enable those notifications in Settings.

Ride reminders, changes, cancellations, and weather notifications remain available to everyone.

Text messages

We send one kind of text message: a six-digit code when you ask to sign in using your phone number.

Message and data rates may apply.

You can reply:

• STOP to stop receiving text messages.
• START to resume them.
• HELP for assistance.

Stopping text messages doesn't close your account. You can still sign in with your email address.

We keep a record of what you agreed we could text you, when you agreed, and the wording shown at the time. We also record STOP and START requests so we can honor your choices.

We don't share your phone number or your consent to receive texts with anyone for their marketing.

Our messaging provider sends texts on our behalf and isn't permitted to use your number for other purposes.

What we don't collect

There are some things we've deliberately chosen not to collect.

Your phone contacts. Our iPhone and Android apps don't request access to your contacts.

A personal search history. We don't keep a record of searches associated with your identity.

Age verification documents. We ask for your date of birth. We don't ask for ID or other documents.

Unnecessary behavioral records about younger riders. We don't collect the additional account activity, engagement, invitation, crash-report, or ride-recording measurements described above for riders under 18 or accounts whose age hasn't been provided.

We still keep the information needed to make their accounts work, including their rides, attendance, and social connections. Anonymous totals, page views, and the joining and sign-in records described above may also include younger people, signed in or not.

Accounts for riders under 18. You must be 18 or older to have a Biiikes account. If you give a birthday that makes you under 18, we delete the account right away.

Who can see your information

Other riders see only the information Biiikes makes available through your profile and the visibility settings you've chosen.

The name you choose to go by, your username, and your optional profile information are visible to signed-in riders, and to anyone if your profile is Public.

Other riders see what the service displays: your name and username, rides you lead, and content you post. They see a ride you are attending only if you chose to show it to them, and the ride leader always sees that you are attending.

A post you share with Everyone can be seen by anyone, signed in or not, and its page names you. Someone who isn't signed in never sees comments or who wrote them. When you share a post, a share picture or a ride replay to another app, that app gets it with biiikes.com on it, and its own privacy policy applies.

Who can see your ride attendance depends on your choices for that ride.

Rides you've saved show on your profile to anyone who can see it. Your Close friends list is private, subject to any access you've granted to connected apps or assistants.

Where you ride from is private. Only your neighborhood can show on your profile, never a street address or corner. If you've told us a birthday that makes you 18 or older, it shows once you've given one, and you can turn it off in Settings, beside where you ride from.

Who can see a ride you record on Biiikes is up to you, ride by ride. If you've told us a birthday that makes you 18 or older, it starts at Everyone; otherwise it starts at Only me.

If you've told us a birthday that makes you 18 or older, these settings start at their most open choice:

• Your profile is Public, and search engines can show it. "Let search engines show my profile" only matters while your profile is Public.
• Who can see which rides you're going to starts at Everyone.
• Rides you record start at Everyone.
• When someone tags you on a ride, the tag shows right away. You can remove it.
• Your bike shed can be seen by Everyone. On a Private profile, Everyone means only the followers you've approved.
• "Other people's AI assistants", which decides whose assistants can see you through apps they've connected, starts at Everyone.
• Your neighborhood shows on your profile once you've given one as where you ride from. We never show a street address or corner.
• Notifications on your locked phone show names, such as who followed you or which ride changed.

If you're under 18, or you haven't told us your birthday, these settings start at the more private choice: your profile is Private, where you're going starts at Followers, search engines can't show your profile, "Suggest me to other riders" is off, tags ask you first, your bike shed starts at Close friends, other people's AI assistants start no wider than Followers, your neighborhood isn't shown, notifications on a locked phone don't show names, and rides you record start at Only me. If you're under 18, some of these can't be changed until you turn 18 (see "Privacy for riders under 18"). If you haven't told us your birthday, you can change any of them.

Whatever your age, these stay off until you turn them on: showing your heart rate, calories, power and cadence to anyone else; sharing your live location, which only people you send a link to can see; and a photo's exact location.

If you've already changed a setting, we keep your choice. You can change these under Settings › Who can see what, your neighborhood beside where you ride from, and notification previews under Settings › Notifications and sound.

Your health numbers are seen only by you, unless you choose to show them.

While you share where you are, the people you share with see it, and so does anyone a link was forwarded to, until the ride ends.

If you help show where a ride is, signed-in riders see the dot, and if you're the only one sharing, it's exactly where you are.

Reports, blocking, and safety tools

You can report a rider, block them, or turn on Warn me to get a private heads-up about them. Here's what each one keeps, who can see it, and who's told.

If you report someone

You can report a rider from their profile. We keep who made the report, who it's about, the reason you picked, and anything you wrote, up to 1,000 characters.

You can also report a post or a comment from the post, and another rider's collection from the collection. We keep the same things, and which one you reported.

If you report someone for harassment or bullying, violence or threats, sexual content, or child safety, we block them and turn on Warn me for you as soon as you send it.

A person on the Biiikes team reads every report and decides what happens. We keep the outcome, the rule it fell under, and who on the team decided. We also keep a record of each step the team takes.

Apart from you, only the people on our team who decide reports can see your report and what you wrote.

The rider you reported is never told that you reported them, or that anyone did, although the circumstances may sometimes make it possible for someone to guess.

We'll tell you when we receive your report and when it's settled, but nothing about the other person. In Settings → Your reports, you can choose Ask for another look once per report, within 30 days after it's settled. We keep your request and anything you write with it.

If you report a ride, we keep who reported it, the ride and the date, the reason you picked, the outcome, and any request for another look with what you wrote.

You can report a live link page, or someone's live location, with Report this live share. You need to be signed in to report one. If you opened a link without an account, we ask you to sign in first. We keep the same things as for a report about a rider: the reason you picked and anything you wrote, but no one's location.

If someone reports you

You never see a report about you. We never tell you that anyone reported you, or who.

You may hear about an outcome. A caution comes by email and in your notifications. If your account is locked, you'll see that when you open Biiikes, along with the rule and what's restricted.

You can ask once for another look at that decision. We keep your request, and anything you write with it, with the decision.

Blocking and Warn me

When you block someone or turn on Warn me, we keep who you are, who the other rider is, and when. Only you know about it. The other rider is never told.

Blocking ends any follows between you, in both directions.

Blocking someone also ends any live link you sent them and stops them seeing where you are while you ride. Warn me doesn't change live sharing. To stop a follower seeing where you are, block them, or leave followers out when you share.

Someone you've blocked sees a rolling ride's dot without you, and no dot if you're the only one sharing. A part of "The route they rode" that only you made is hidden from them.

We never count how many riders have turned on Warn me for someone, and we never treat it as a report.

Unblocking someone or turning off Warn me in Settings → People deletes it.

Photo checks

Before anyone else sees a profile or cover photo, a photo or clip in a post, or the words of a post or comment, OpenAI's moderation service checks it automatically. For a clip, it checks the cover and frames. We keep the scores and the result of that check.

If a photo doesn't pass, we don't use it. We keep a private copy so a person on our team can look at it. Only our team can see it.

When you upload a photo, we keep the network address (IP address) it came from, encrypted so no screen shows it, until the photo’s automatic checks finish. Then it’s deleted. We keep it longer only inside a report the law requires us to make about the photo. An address doesn’t prove who uploaded a photo: many people can share one.

Cloudflare's CSAM Scanning Tool checks images as Cloudflare serves them against known child sexual abuse material. It blocks a match and tells us. It doesn't check clips, and it checks an image when it's served, not before a post shows. When we learn of apparent child sexual abuse material, however we learn of it, we report it to the National Center for Missing & Exploited Children's CyberTipline, as the law requires. We take it down, lock the account, and keep the material and the report's details securely for one year, or longer only if NCMEC or law enforcement asks. The report includes account details and, where we still have it, the IP address it was uploaded from.

When an account is deleted

A report about a rider stays when either rider's account is deleted, but it no longer names the deleted account. What was written in it stays too.

The list in "How long we keep information" covers reports, blocks, and photos that didn't pass.

Apps and assistants you connect

You can connect other apps and assistants to your Biiikes account.

We keep track of each connection, including its name, what you've allowed it to access, when you connected it, and when it last used your account.

You can disconnect an app or assistant from your account page.

Using Sign out everywhere disconnects them all.

Third-party apps and assistants that go unused for 30 days stop working and are deleted. Ride apps you connect, described below, don't expire.

Our own iPhone and Android apps can remain signed in for up to one year without use.

You can make a personal key that lets your own apps or scripts use your account. We keep its name, a scrambled version of it, and when it was last used. It doesn't expire. It lasts until you delete it.

Your calendar link

If you create a calendar subscription link, we keep a scrambled version of it rather than the link itself.

Anyone who has your actual link can use it to see the rides in your calendar feed.

You can create a new link whenever you want. Doing so immediately invalidates the old one.

Treat your calendar link as private, and share it only with people or apps you trust.

Ride apps you connect

You can connect Biiikes to other apps that record rides. Each one is its own connection, and you turn it on yourself. We keep your sign-in for each one encrypted. It's never shown, and never sent anywhere else. When you disconnect, we delete it and tell that service you've disconnected. Sign out everywhere doesn't disconnect ride apps; disconnect each one on its own.

Strava. Once you connect Strava, every ride you record in Biiikes is uploaded to your Strava account automatically, unless you skip it on that ride. If Strava needs you to reconnect, rides you record in the meantime are sent once you do. Strava receives each ride's route with its times and moving time. While "Hide my private zones in rides sent to other apps" is on, which it is unless you turn it off, that route leaves out the stretches inside your private zones and the start and end that Biiikes hides from other people, just as others see it on Biiikes. If you turn it off, Strava gets the whole route. Your other Biiikes privacy choices don't apply on Strava. Each upload also carries the ride's heights, the forecast temperature for that hour, and the ride's name and caption, once each has passed our check, as the activity's name and description. If you're 18 or older and have health numbers turned on, it also carries heart rate, power, cadence, speed from a speed sensor, and calories (your device's if it measured them, otherwise our estimate). Your weight, age and sex never go.

Your Strava rides also come into your Biiikes log, seen only by you, with View on Strava instead of a download. If you disconnect Strava, or remove Biiikes in your Strava settings, we delete the rides that came from Strava. If you delete a ride on Strava, we delete it here too. Rides you recorded in Biiikes stay, and copies already uploaded to Strava stay on Strava. Riders under 18 can't connect Strava.

Apple Health and Health Connect. On iPhone you can connect Apple Health, and on Android, Health Connect. Biiikes writes the rides you record to it, and reads rides other apps recorded there. For each ride, it receives the workout: its start and end, its distance and its route. While "Hide my private zones in rides sent to other apps" is on, the route leaves out the stretches inside your private zones and the hidden start and end; if you turn it off, the whole route goes. We don't write your health numbers to it. Your phone asks before Biiikes uses Apple Health or Health Connect, the first time it's needed. A ride written there is yours in that app, and deleting it in Biiikes doesn't delete it there. If the same ride comes from another connected service and from Apple Health or Health Connect, we keep the other service's copy. If you disconnect, rides already brought in stay until you delete them. Riders under 18 can't connect Apple Health or Health Connect.

Wahoo. Your Wahoo rides come into your Biiikes log as Only me. Before anyone else can see them, you say yes once for Wahoo. Then you can share them like any ride. Turning that yes off returns them to Only me. We don't send Wahoo any of your rides. Disconnecting Wahoo deletes the rides that came from Wahoo.

Ride with GPS. Your rides from Ride with GPS come into your Biiikes log as Only me, and you can share them like any ride. We don't send Ride with GPS any of your rides. If you disconnect, rides already brought in stay until you delete them.

Your routes from Ride with GPS. Once you connect, every route on your Ride with GPS account, ridden or not, comes into your Biiikes route library, and we store it encrypted. An edit on Ride with GPS updates our copy at the next sync, and a route you delete there leaves your library. A group ride already listed with that route keeps its own copy until the ride changes route, and other riders' saved copies stay. If you disconnect, your routes and collections stay but stop updating. We don't send anything back to Ride with GPS.

A route that's public on Ride with GPS starts at your "Who sees rides I record" choice, and any other starts at Only me. After that you choose in Biiikes, and changes on Ride with GPS don't move it. If you're under 18, your routes never start at Everyone. Others see a route trimmed at your private zones.

Your Ride with GPS collections show up on their own and change only on Ride with GPS, and you can make your own from any of your routes. Each collection has its own "Who sees this collection?" choice, and it never shows anyone a route they aren't allowed to see. You can share a collection by a link nobody could guess. An Everyone collection on a Public adult's profile opens for people who aren't signed in, showing only its Everyone routes; otherwise they're asked to sign in. Other riders can report a collection. When your first sync finishes, we send you one notification, which has its own setting.

Companies that help us run Biiikes

We use outside service providers for things like hosting, website delivery, email, text messages, and images.

These companies process information on our behalf to provide their services. They're not permitted to use it for unrelated purposes.

Email

Resend delivers our emails.

It keeps your email address and your email preferences so unsubscribe links can work without requiring you to sign in.

Apart from the emails themselves, we don't send Resend additional account information.

When you change your email address, Resend's copy of the old address is removed. When you delete your account, its copy of your email address is removed.

Hosting and website delivery

Railway hosts Biiikes, and Cloudflare helps deliver the website and protect it.

While you share your live location, it's held in memory on a Railway server, alongside the rest of Biiikes.

Both companies may keep records of requests made to Biiikes, including IP addresses, requested pages, and browser information.

Railway keeps its request records for 30 days.

Cloudflare keeps records of requests acted on by its security checks for 31 days.

Our own rate-limiting system uses a scrambled version of an IP address, held in server memory for one hour, to stop too many requests, like asking for sign-in codes or sending page-view reports.

When our iPhone or Android app asks for a sign-in code, we also save that scrambled address in our database for about a day, to slow down repeated tries.

We don't store the original IP address in either place.

Location services

As described earlier, we use the US Census Bureau's geocoder for complete street addresses, and a table of street corners we build from OpenStreetMap's data and keep on our own server.

We don't send those services your identity or account information with those requests.

Mapbox gives us the drive time on a ride's Getting there card. When you're signed in, that card or the ways sheet is showing, and you're starting from where you are or from your home, our server sends it your starting point, rounded to approximately 100 meters, along with the meeting spot and, when it's still ahead, the ride's meet time. We don't send your account or an ID, and because the request comes from our server, Mapbox doesn't get your own internet address.

Other services

Twilio sends our sign-in codes. It receives your phone number, the code, and which language to send it in.

OpenAI's moderation service checks photos, clips and words automatically. It receives each profile and cover photo you add, each photo in a post, the cover and frames of each clip in a post, and the words of each post and comment.

Google's ML Kit, in our Android app only, finds the subject for a cut-out and writes suggestions on your phone. It sends Google metrics about how those features performed and how often the app used them. ML Kit doesn't send Google your photos or the words it's working from. There's no setting to turn the metrics off.

Cloudflare stores the photos you add.

Apple and Google deliver push notifications to your phone, and your browser's maker delivers them to your browser. They receive the notification's text and a code that identifies your device.

Advertising and selling data

We don't sell your personal information.

We don't share it for advertising that tracks you across different companies' websites or apps.

We may disclose information when required by law or when necessary to protect someone's safety.

How long we keep information

We don't keep every kind of information for the same length of time.

Here's how long different records stay with us.

• Website page views: 13 months
• iPhone and Android crash reports: 13 months
• Account activity and engagement measurements: Until account deletion, up to 25 months
• Individual joining and sign-in records: Until account deletion, up to 25 months
• Incomplete joining and sign-in records: 13 months
• Anonymous browser or app activity: 13 months, or up to 25 months when associated with an adult
• Browser and app associations with accounts: Until account deletion
• iPhone and Android app activity: Until account deletion, up to 25 months
• Connected apps and assistants, and sessions: 30 days after last use, or one year for our own mobile apps
• Invitations: Until either person's account is deleted
• Personal keys: Until you delete them
• Rides you record or upload, and tags on them: Until you delete the ride or your account
• Health numbers: With their ride, until you delete the ride or your account
• Private zones: Until you delete them or your account
• A scrambled code for each place you said no to as a private zone: Until you delete your account
• Your live location: Held in memory only, never written to disk, gone within hours and not kept after you stop sharing
• Who looked at your live location: Until sharing ends, and one day more
• Your list of people you send live links to: Until you remove them or delete your account
• The route a ride took, and the encrypted list of who made each part: Kept with the ride. A part only you made is deleted when you delete your account
• Your sign-in for a connected ride app: Until you disconnect it
• Rides from Strava: Until you delete them, disconnect Strava, remove Biiikes on Strava, delete them on Strava, or delete your account
• Rides from Wahoo: Until you delete them, disconnect Wahoo, or delete your account
• Rides from Garmin Connect, Hammerhead, Ride with GPS, Komoot, Apple Health or Health Connect: Until you delete them or your account, even if you disconnect
• Duplicate-action protection records from mobile apps: Up to 24 hours
• Rate-limiting records for app sign-in codes: About a day
• Safety reports: until 12 months after the case closes, then they’re deleted. A case closes once it’s decided and the 30 days to ask for another look have passed, or the other look is decided. A report that’s still open stays until it closes, and every 90 days it goes back to a person at Biiikes. When an account is deleted, the report stops naming it
• Cautions and locks on an account, and the rider's request for another look: Until that account is deleted
• Blocks and Warn me: Until you undo them, or either account is deleted
• A photo that fails the automatic check, when nobody reported it: 30 days, then it’s deleted.
• The original files you sent for your profile photo and cover photo: for as long as each one is your photo. Nobody else can open them. They’re deleted when you replace or remove the photo, or erase your account.
• A photo in a post that someone reported, while the report is open or after a person at Biiikes took the post down: until 12 months after the case closes, then it’s deleted. We keep it even if the person who posted it deletes the post or erases their account. Once the post is gone, only the people at Biiikes who decide reports can see it.
• Comments: Until you or the poster delete one, the post is deleted, or your account is deleted. If we take a comment down after a report, it's deleted 30 days later unless you ask us once to look at it again before then
• The words of a comment someone reported: until 12 months after the case closes, then they're deleted. We keep them even if the comment is deleted or the person who wrote it erases their account. Once the comment is gone, only the people at Biiikes who decide reports can see them.
• Reposts: Until you undo one, the poster narrows the post below Everyone or deletes it, or either account is deleted
• Bookmarks: Until you remove one, the post is deleted, or your account is deleted
• Routes and collections from Ride with GPS: Until they're deleted on Ride with GPS or you delete your account, even if you disconnect. A group ride already listed with a route keeps its copy until the ride changes route
• Record of what our team does when deciding a report: No set deletion time today
• Anonymous aggregate counts: Indefinitely
• Words from searches that found nothing: Indefinitely
• Other account information: As long as the account exists, unless otherwise described

Anything under a legal hold, a court or police order to keep it, stays until the hold is released, even past these periods. Once the hold is released, safety reports and the photos kept for them are deleted on the schedule above.

Incomplete sign-ups

If you verify a phone number but don't finish creating an account, we keep the number temporarily.

If you don't continue, the incomplete account and its sessions are removed 7 days after your last activity.

Text message consent records

We keep text message consent records for as long as your account exists.

After you delete your account, we remove the phone number itself but keep a scrambled identifier, together with the consent record, for four years after the last text we sent. This lets us demonstrate that a message was authorized if a carrier asks.

If you've replied STOP, we keep the scrambled identifier on a do-not-text list for as long as Biiikes sends texts. That prevents another sign-in text from being sent to that number until it replies START.

If someone gives a birthday that makes them under 18, we delete their phone number right away and keep only a scrambled identifier for two years, for opt-out and carrier compliance. It isn't used for anything else.

Backups

We keep encrypted database backups in case something goes wrong and Biiikes needs to be restored.

Backups are kept for no longer than approximately 30 days and aren't used during normal operation.

If we restore a backup, we reapply completed account deletions before using the restored data.

A ride you delete can stay in our backups for about 30 days, then it's gone.

Your rights and choices

Your information belongs to you, and you have ways to view, change, and remove it.

You can manage these choices from your account.

Access your information. Download the information we hold about you.

Download everything, in Settings › Your data, includes every ride on the Rides tab of your profile, your private zones and your ride recording settings. You can also download any single ride as a GPX or FIT file, for free. Rides that came from Strava show View on Strava instead.

Correct your information. Update your account details and what appears on your profile.

Delete a ride. Deleting a ride you recorded deletes it for good everywhere in Biiikes: its line, its numbers and any health numbers, and any part of a ride's route that only it made. If it marked that you went to a ride, that stays. A copy already uploaded to Strava or written to Apple Health or Health Connect is yours there, and isn't deleted there.

Take a break. Choose to leave Biiikes without deleting your account. You won't be findable or receive messages, but your information is kept so you can return.

Delete your account. Start the process of permanently removing your account and its information.

Manage notifications. Choose which optional notifications you receive and how they're delivered.

Deleting your account

When you request account deletion, you're immediately removed from the service.

You have seven days to change your mind and cancel the deletion.

After those seven days, your account information is deleted from the active service, except for limited records we must retain as described in this policy.

Any remaining encrypted backup copies expire within approximately 30 days.

Deleting your account deletes every ride you recorded, the tags you made, and the tags of you on other riders' rides.

It also deletes your private zones.

It also deletes your list of people you send live links to.

It also deletes your part of "The route they rode" on every ride.

If your account is under a legal hold (see How long we keep information) when it’s erased, the safety reports made by you or about you, and the photos kept for those reports, stay until the hold is released, then they’re deleted on their usual schedule. You’re still removed immediately, and everything else is deleted after the 7 days.

For step-by-step instructions, see How to delete your account.

Depending on where you live, you may have additional privacy rights, including the right to appeal certain decisions about privacy requests. Email us if you'd like to exercise those rights.

Privacy for riders under 18

You must be 18 or older to have a Biiikes account, but anyone of any age can see every ride on the calendar without one. If the birthday you give us when you join makes you under 18, we delete the account right away, along with what it held, and keep only the scrambled identifier described under "Text message consent records". Rides may be public, and other people can see you at a ride.

Where your information is stored

Your information is stored in the United States. Some of the companies that help us run Biiikes may process it outside the United States.

How we protect your information

We encrypt information stored by Biiikes.

Sensitive information, including the phone number on your account, is encrypted using keys kept outside the database.

We also use controls such as sign-in alerts, account session management, and limits on repeated requests to help protect accounts and the service.

No online service can promise perfect security, but we work to protect the information people share with us.

Changes to this policy

We may update this policy as Biiikes changes.

When we do, we'll update the date at the top. If a change is significant, we'll notify you.

Change history

November 10, 2026: Said that street corners are found in a table we build each month from OpenStreetMap's data and keep on our own server, so looking one up sends nothing to OpenStreetMap.

November 9, 2026: The lines in this policy about searching for any place and Your places began to show.

November 7, 2026: The lines in this policy about ways to a ride began to show.

November 4, 2026: Turn-by-turn now finds you a new way after you've been well off the route for about 15 seconds, not about 30. Added the direction you're moving to what it can send. The lines in this policy about routes and collections from Ride with GPS began to show.

November 3, 2026: Biiikes is now for riders 18 and over. Took out what this policy said about accounts for riders aged 13 to 17, and said what happens when someone gives a birthday that makes them under 18. The lines in this policy about posting and the Hub, your column of posts and updates began to show. The lines in this policy about comments on posts began to show. The lines in this policy about reposts began to show. The lines in this policy about bookmarks began to show. The lines in this policy about caption suggestions written on your phone began to show. The lines in this policy about cut-out stickers began to show.

November 2, 2026: Added how we handle posts, comments, reposts, bookmarks and reactions, and the automatic checks on posts and comments; how Cloudflare checks images and how we report child sexual abuse material; editing tools that run on your phone, and Google's ML Kit on Android; routes and collections from Ride with GPS; and what Strava receives with each ride.

November 1, 2026: The lines in this policy about connecting Wahoo began to show.

October 31, 2026: The lines in this policy about connecting Strava began to show. The lines in this policy about trying different versions of parts of the app began to show.

October 30, 2026: Changed where settings start. If you've told us a birthday that makes you 18 or older, most privacy settings start at their most open choice and most notifications and emails start on. Riders under 18 and riders who haven't told us a birthday start with the more private settings, a few things stay off for everyone until you turn them on, and any setting you've already changed keeps your choice.

October 26, 2026: The lines in this policy about recording rides, private zones and downloading your rides began to show. The lines in this policy about sharing your live location and helping show where a ride is began to show. The lines in this policy about health and sensor numbers began to show. The lines in this policy about Apple Health and Health Connect began to show. The lines in this policy about uploading ride files began to show. The lines in this policy about connecting Ride with GPS began to show.

October 24, 2026: Reorganized and clarified the policy, including how Biiikes handles account information, location, analytics, younger riders' data, service providers, and account deletion.

October 23, 2026: Added a dated change history and clarified retention periods for page views and crash reports, database backups, and how account deletion applies to restored backups.

Questions?

If you have questions about this policy, your information, or your privacy choices, email [email protected].

Biiikes LLC

We're happy to help.