1. Who we are
BikeLife is provided by BikeLife Network LLC, a New York limited liability company whose mailing address is 228 Park Ave S, PMB 362349, New York, NY 10003-1502, United States ("we", "us", "our"). We are the controller of the personal information described in this policy, which means we decide how and why it is used.
Privacy contact: [email protected], or by post to the address above, marked "Privacy".
Our representative in the United Kingdom (Article 27 UK GDPR): MadeYouViral Ltd, 66 Paul Street, London EC2A 4NA, United Kingdom. Please address post to MadeYouViral Ltd and mark it "BikeLife".
2. What this policy covers
This policy covers the BikeLife app for iPhone and Android, our website at joinbikelife.com, the emails and notifications we send, and any other place that links to it (together, "BikeLife"). It explains what we collect, why, who we share it with, how long we keep it and your rights. It does not cover other companies' apps, sites or services, even if BikeLife links to them. Words such as "rideout", "host" and "content" have the meanings in our Terms of Service.
3. What we collect
3.1 What you give us
| Information | What it includes |
|---|---|
| Account | Your email address and password (your password is stored by our sign-in provider only as a secure scrambled "hash", and we never see it). If you sign in with Apple or Google: the account identifier they give us, your email address (which may be an Apple private relay address), and your name if you choose to share it. If you use Sign in with Apple, we also keep a token Apple gives us so that we can revoke your Apple sign-in when you delete your account. |
| Date of birth | Asked on the sign-up screen before your account is created (or during setup if you sign in with Apple or Google), to confirm you meet the minimum age and to apply teen account protections if you are under 18. Until setup finishes it is kept only on your phone. It is stored separately from your profile and is never shown to anyone. |
| Profile | Display name, username, profile photo, banner image, bio, and the YouTube, TikTok and Instagram handles you type in. Your passport style choices (cover, finish, crest, paper and the country shown on it), and the profile frame and passport tape you wear. |
| Clips and photos | Videos you post, the poster image made from them, captions, length, size and dimensions, the riders you tag, and the rideout a clip belongs to. Photos you upload as profile pictures, banners and crew badges. Photos are re-encoded on your phone before upload, which removes hidden details such as where they were taken. Some video files can carry details such as where they were recorded; we do not read or use them, but you can turn off location tagging in your camera settings if you do not want them in your files. |
| Comments and reactions | Comments and replies, likes, saves, and likes on comments. |
| Rideouts you host | Title, description, banner, meet time, ride time and end time, the meetup place's name, coordinates and country, the stops, bends and line of the route and whether each part follows roads or paths, rules, how many riders can go, who can see it, the stamp you design, and when you confirmed that motorbikes are allowed on any paths in the route. |
| Rideouts you go on | That you are going, when you agreed to the host's rules, when you checked in and out, how far you were from the meetup point when you did (a distance in meters, not your coordinates), and the stamps you collect. |
| Crews | Crews you create (name, bio, badge), your membership and role, invites, requests to join, crew notices and crew chat. |
| Messages | The text of messages you send, clips you share in them, replies, reactions, whether messages have been read, which conversations you mute, message requests, group chat names, and a short preview of the latest message used for your inbox. |
| Follows and blocks | Who you follow, who follows you, and who you block. |
| Reports and appeals | Reports you make (the reason and any details you add), and appeals and complaints you send us. |
| Settings | Your notification choices, whether you accept message requests, and whether you share usage data. |
| Support | Anything you send when you email us or use a form on our website. |
3.2 What is created when you use BikeLife
| Information | What it includes |
|---|---|
| Clip viewing | Which clips you have watched, for how long, how many times and whether to the end. Used to rank your feed, count views and give creators totals. Creators see totals only, never who watched. |
| Activity and progress | XP and the reasons for it, your rank and rank history, your daily streak and the last day you opened the app, notifications we send you and whether you have read them, and referral codes and who joined with them. |
| Purchases | From Apple, Google and RevenueCat: which membership or item you bought, transaction identifiers, dates, renewal and expiry, trial status, billing problems, and whether it was a test purchase. What you own and use: extra rideouts to host, boosts, featured rideouts and cosmetics. We never receive your card or bank details. |
| Device and connection | A push notification token for your phone, your platform (iOS or Android), app version and time zone (the time zone is used to keep notifications quiet at night for riders under 18). Our providers' servers record your IP address, the time and technical details of requests (such as the type of device and software) in short-term security logs. |
| Usage analytics | If you share usage data (see section 7): the actions listed there, the screens you open (named by type of screen, not whose profile or which clip), when the app is installed, updated, opened or closed, your device model and maker, operating system and version, app version, language, time zone and screen size, and your approximate location (city and country) worked out from your IP address. |
| Error reports | When something breaks: the error message and code, the part of the app, technical details of the failure (a "stack trace"), and the device details above. |
| Route planning | How many route requests you make each minute and day, so that one account cannot overload the routing server. |
| Safety and moderation | Reports about you or your content, decisions we make, and whether your account is suspended. |
3.3 What we get from others
- Other riders: when they tag you in a clip, invite you to a crew, message you, add you to a group chat, report you, or join with your referral code.
- Apple and Google: when you sign in with them, and when you buy through their stores.
- RevenueCat: the state of your memberships and purchases.
3.4 What we do not collect
We do not access your camera, microphone, contacts, calendar, health or fitness data, motion sensors, Bluetooth devices or advertising identifier. We do not use facial recognition or any biometric data. We do not ask for sensitive information such as your health, ethnicity, religion, politics or sexuality. If you choose to put something like that in a public clip, bio or comment, it becomes public because you chose to share it.
4. Your location, in detail
BikeLife only uses your phone's location after you allow it in your phone's permission prompt, and only for these features:
| Feature | What happens to your location |
|---|---|
| Rideouts near you | Your phone sends your current coordinates to our server to find rideouts near you. They are used for that search and not stored. |
| Hosting and place search | The meetup place and stops you choose are saved with your rideout and shown to riders who can see it. When you type a place, the text you type and your approximate position (so that nearby places come first) are sent to Google Places, or to your phone's own place search, to suggest places. |
| Checking in and out | Your phone sends your coordinates at that moment. Our server checks you are at the meetup point and stores only the distance in meters and the time. Your coordinates are not stored. |
| Route planning | The coordinates of the meetup point, stops and bends are sent to our own routing server (in Finland) to plan the roads. The routing server does not receive your name or account. |
| Navigation | Your position is used on your phone to give turn-by-turn directions. It is not sent to us for this. |
| Live ride | While a rideout is live and you have the ride screen open, including when your phone is locked, your position, direction and speed are sent about every three seconds to the other riders on that rideout, through our real-time service, so the group can see each other on the map. It is not stored in our database. It stops when you close the ride screen or the rideout ends. On iPhone a blue location indicator shows while this is on; on Android a "BikeLife ride" notification does. |
| Maps | Maps are shown by Apple Maps on iPhone and Google Maps on Android, which load map images for the area on screen under their own privacy policies. |
We also estimate your approximate location (country or city) from your IP address for security and, if you share usage data, analytics. We do not keep a history of your movements, and we do not track your location in the background at any other time. You can turn location off in your phone's settings at any time; the features above will stop working.
5. Phone permissions
- Location ("while using the app"): for the features in section 4. On iPhone, a ride can continue in the background while the ride screen is open, which is shown by the blue indicator.
- Photos: to choose the photos and videos you post. We only receive the ones you pick. Separately, "add photos" permission lets BikeLife save images you choose to keep, such as your passport, to your photo library.
- Notifications: to tell you about messages, follows, rideouts and other activity. You choose which kinds in Settings.
You can change any permission in your phone's settings at any time.
6. How we use your information, and our legal reasons
Data protection law in the UK, the EU and some other places requires us to have a legal reason (a "lawful basis") for each use. Ours are:
| Why we use it | Lawful basis |
|---|---|
| To create and run your account, show your profile, host and deliver your content, run rideouts, check-ins, stamps, passports, crews, messages, notifications, navigation and the live ride, and provide what you buy | Performing our contract with you (the Terms of Service) |
| To confirm your age and apply age rules | Legal obligation, and our legitimate interests in keeping under-age users off BikeLife |
| To use your phone's location, photos and notifications | Your consent, given in your phone's permission prompt, and performing our contract |
| To keep BikeLife safe: reviewing reports, moderating content, preventing abuse, fraud, spam and ban evasion, enforcing our terms, and securing our systems | Our legitimate interests, and yours and other riders', in a safe and secure service, and legal obligations |
| To rank your feed and recommend clips and rideouts | Our legitimate interests in showing you what you are most likely to want, and performing our contract |
| To understand how BikeLife is used and fix errors (section 7) | Your consent where the law requires it; otherwise our legitimate interests in improving BikeLife |
| To handle purchases, memberships, refunds and billing problems | Performing our contract, and legal obligations (such as tax and consumer law) |
| To show public clips to promote BikeLife | Our legitimate interests in promoting BikeLife, and the license in our Terms |
| To respond to legal requests, report illegal content where required, and establish, exercise or defend legal claims | Legal obligation and our legitimate interests |
| To protect someone's life in an emergency | Vital interests |
Where we rely on legitimate interests, we have balanced them against your rights and you can object (section 17). Where we rely on consent, you can withdraw it at any time, which does not affect what we did before.
We do not use your information for third-party advertising, we do not sell it, and we do not use your content or messages to train artificial intelligence models, and we do not allow our providers to.
7. Usage analytics and error reports
We use PostHog to understand which features are used and to find and fix errors. When you share usage data, the app sends: the screens you open (by type, never whose profile or which clip); app opens, installs and updates; and these actions, with the kind of thing involved but never its content: signing up, logging in, finishing onboarding, resetting a password, posting, liking, saving or sharing a clip, commenting, following, hosting, joining or checking in to a rideout, creating, joining or asking to join a crew, sending a message (never what it says), opening the membership screen, buying, cancelling or restoring a purchase, and deleting an account. Error reports are described in section 3.2. We never send your messages, what you write, your email, your name, your date of birth or your precise location to PostHog. Before you sign in you are anonymous; after you sign in you are known only by a random BikeLife account number.
Your choice. Where the law requires your consent for this (including in the UK, the European Economic Area and Switzerland), we ask for it before collecting anything. Elsewhere, usage data is on unless you turn it off. You can turn it off, or back on, at any time in Settings, Privacy, Share usage data. If you are under 18, usage data is off until you choose to share it: we ask you once, after you join, and you can change your answer in Settings. We do not use session recording.
8. How your feed works
The Home feed shows clips you have not watched yet first, and gives every new clip an audience, then ranks clips by how riders have reacted to them, including views, watch time, how many watched to the end, likes, comments and saves. Your own viewing history decides which clips count as new to you. The Rides tab shows rideouts by date, distance and whether they are promoted. Promoted clips and rideouts are marked where they appear. You can refresh the feed, follow different riders, and block riders to change what you see. We do not use information about you from outside BikeLife to rank anything. If you are under 18, your feed is not personalized: it is not based on what you have watched or who you follow, and shows clips ranked by how all riders reacted to them.
9. Automated decisions
Two things are decided automatically, without a person, based on information you give us: whether you meet the minimum age (from your date of birth), and limits on what an account can do (such as how many rideouts it can host each month, how often it can post, and whether a check-in counts). If you think an automated decision about you is wrong, email [email protected] and a person will review it. We do not make any other decision that has legal or similarly significant effects on you solely by automated means.
10. Who can see what
| What | Who can see it |
|---|---|
| Your profile | Anyone using BikeLife: display name, username, photo, banner, bio, social handles, rank, badges, frame, tick, follower and following counts, your public clips, and your passport with the stamps you have collected (which show the rideouts you attended and when). |
| Clips and comments | Anyone using BikeLife, and anyone you or others share a link with. Tagged riders are shown on the clip. |
| Rideouts | Public rideouts: anyone using BikeLife. Followers-only rideouts: the host's followers. Riders who can see a rideout can see its details, its route, who is hosting and who is going. |
| Crews | Crew names, badges, members and standings are public. Crew chat is visible to crew members. |
| Messages | Only the people in the conversation. We may see a message when it is reported or as section 11.4 explains. |
| Live location | Only the riders on the same live rideout, while you have the ride screen open. |
| Never shown to other riders | Your email, date of birth, purchases, clip viewing history, usage data, device details and IP address. |
If you block someone, they can no longer see your profile and content in BikeLife or message you. Anything you make public can be seen, screenshotted, recorded or shared by others, and we cannot control copies made outside BikeLife.
11. Who we share it with
11.1 Our service providers
We use these companies to run BikeLife. They act on our instructions, under contracts that require them to protect your information and use it only to provide their service to us.
| Provider | What they do for us | Where |
|---|---|---|
| Supabase, Inc. | Our database, sign-in, server functions, real-time messaging and live ride sharing | United States (Amazon Web Services, Virginia) |
| Cloudflare, Inc. | Storing and delivering photos and videos, protecting our servers, and the secure connection to our routing server | Global network |
| Hetzner Online GmbH | Hosts our own routing server, which plans routes from coordinates only | Finland |
| RevenueCat, Inc. | Manages memberships and purchases made through the app stores | United States |
| PostHog, Inc. | Usage analytics and error reports (section 7) | United States |
| 650 Industries, Inc. (Expo) | Delivers push notifications to Apple and Google, and delivers app updates | United States |
| Resend | Sends our emails, such as password reset codes | United States |
| Google LLC | Place suggestions when you type a place (Google Places) | United States and global |
| Cloudflare, Inc. and Google LLC | Receive and store the emails you send us (Cloudflare Email Routing and Gmail) | United States |
11.2 Apple and Google as independent companies
When you sign in with Apple or Google, buy through the App Store or Google Play, receive push notifications, or view maps, Apple and Google process your information under their own privacy policies, as independent controllers.
11.3 Other riders
We share what you make visible with other riders, as section 10 explains.
11.4 Safety, the law and legal claims
We may access, keep and disclose information, including messages, if we believe in good faith it is necessary to: comply with the law, a court order or a valid legal request from the police or other authorities (see our Law Enforcement Guidelines); report child sexual exploitation to the National Center for Missing and Exploited Children or another body as the law requires; prevent death or serious injury; investigate and act on breaches of our terms; protect the rights, property and safety of BikeLife, our riders and the public; or establish, exercise or defend legal claims. We share information with our professional advisers, insurers and auditors under duties of confidentiality.
11.5 If the business changes hands
If we are involved in a merger, acquisition, financing, reorganisation or sale of all or part of our business, your information may be transferred to the new owner, who will be bound by this policy or tell you about any change.
11.6 Aggregated information
We may share information that has been combined and made anonymous so that it can no longer identify anyone, such as the total number of rideouts in a country. We will not try to re-identify it.
12. No selling, no tracking
We do not sell personal information, and we do not "share" it for cross-context behavioral advertising, as those terms are used in US state privacy laws. We have not done so in the last 12 months. We do not use your information to target ads. We do not track you across apps and websites owned by other companies, and we do not use an advertising identifier. Because we do not sell or share, a "Global Privacy Control" or "Do Not Track" signal does not change anything, but we honor it as a request to opt out of any sale or sharing if we ever did.
13. International transfers
We are based in the United States. When you use BikeLife, your information is collected by us and processed in the United States, and by our providers in the other countries listed in section 11.1. Data protection laws in those countries may differ from the laws where you live. Where the law requires a safeguard for information leaving the UK, the EEA or Switzerland for a country that is not recognized as giving adequate protection, we use legal safeguards such as the UK International Data Transfer Agreement or Addendum, the European Commission's Standard Contractual Clauses, or a provider's certification under the EU-US Data Privacy Framework and its UK and Swiss extensions. You can ask for more information about these safeguards at [email protected].
14. How long we keep it
We keep information only as long as we need it for the purposes in this policy. When you delete your account, everything is deleted as set out in section 16. Until then:
| Information | How long |
|---|---|
| Account, profile, date of birth, settings | Until you delete your account |
| Clips and photos | Until you delete them or your account. The video and image files are removed from storage and our delivery network within 48 hours of deletion. When you delete a clip, a hidden record of it (its caption, dates, and the likes, comments and reports on it, but not the video) is kept until you delete your account, so that reports about it can still be dealt with. |
| Comments, likes, saves, follows, blocks | Until you remove them or delete your account |
| Messages | Until the sender's account is deleted, or the conversation is deleted. BikeLife does not currently let you unsend a single message. |
| Rideouts and participation | Until the host's account (for the rideout) or your account (for your participation) is deleted |
| Content removed by moderation | Hidden from everyone, and kept as a record of the decision (so that it can be reviewed on appeal) until the account that posted it is deleted |
| Reports and moderation decisions | Until the account or content they concern is deleted |
| Clip viewing, XP, ranks, streaks, notifications | Until you delete your account |
| Purchase records | Purchase event records: up to 180 days. Membership status and items owned: until you delete your account. Apple, Google and RevenueCat keep their own records under their policies and tax law. |
| Usage analytics and error reports | For as long as our analytics provider keeps it under our plan (currently between one and seven years). It is linked only to a random account number, never your name or email. If you ask us, we delete yours sooner. |
| Security logs (IP addresses) | Up to 90 days |
| Push notification tokens | Until you sign out, delete your account, or the token stops working |
| Emails you send us | For as long as we need them to help you, and no more than two years after your last message, unless you ask us to delete them sooner |
| Backups | Our database provider keeps encrypted backups to recover from disasters. They are overwritten on a rolling basis within 30 days. |
15. Deleting things
You can delete your own clips and comments, unfollow, unlike and leave crews at any time in the app. A deleted comment is erased straight away, with its replies. A deleted clip disappears for everyone straight away, and its video and poster image are deleted within 48 hours; a hidden record of it without the video is kept until you delete your account, as section 14 explains. Replacing your profile photo or banner deletes the old file within 48 hours.
16. Deleting your account
Delete your account in Settings, Delete account. If you cannot use the app, email [email protected] from the address on your account and we will do it for you. Deleting your account cannot be undone, and it does not cancel a subscription: cancel that in your App Store or Google Play settings.
| When | What happens |
|---|---|
| Instantly | Your account is locked and you are signed out. Your profile, clips, rideouts, comments and messages disappear from BikeLife for everyone. BikeLife's data is cleared from your phone. |
| Within minutes | Everything about you is erased from our database: your account, date of birth, profile, clips, comments, likes, saves, tags, clip viewing, follows, blocks, messages you sent, your one-to-one conversations and the group chats you created (for everyone in them), rideouts you hosted and everyone's participation in them, your participation in other rideouts, crews you own, your crew memberships, XP, ranks, streaks, stamps, notifications, reports by and about you, purchases and items, and push tokens. |
| Within 48 hours | Your photos and videos are deleted from storage and cleared from our content delivery network. |
| Within minutes to days | We revoke your Sign in with Apple link, and RevenueCat deletes your purchase record there at our instruction. |
| Within 30 days | Backups containing your information are overwritten. If a backup ever had to be restored, we would delete your information again before BikeLife went back online. |
What is not kept. We do not keep a copy, an archive or a "deactivated" version of your account. The only exception is where a law forces us to keep something specific: for example, when a court or the police formally order us to preserve particular information, or when we must report child sexual abuse material to the authorities. In that case we keep only what the law requires, only for as long as it requires, separately from BikeLife, and we use it for nothing else. Apple and Google keep their own records of purchases and sign-ins under their own policies. Usage analytics at PostHog (section 7) are linked only to a random account number and are removed when PostHog's retention period ends; if you ask us at [email protected], we delete yours straight away.
Other people's content. Clips that other riders posted stay theirs, but you are untagged. Messages other riders sent in group chats you did not create stay in those chats, without yours.
If you are refused for being under the minimum age on the sign-up screen, no account is created and nothing you entered is kept. If it happens during setup after signing in with Apple or Google, your account and date of birth are deleted immediately. Either way, your phone remembers only that a sign-up was refused, with no personal information.
17. Your rights
Depending on where you live, you have some or all of these rights. We give every rider the first five, wherever they live.
- Access: to know whether we have information about you and to get a copy.
- Portability: to receive the information you gave us in a structured, machine-readable format, and to have it sent to another company where that is technically possible.
- Correction: to correct inaccurate information. You can change most of it yourself in the app.
- Deletion: to have your information deleted. Deleting your account does this (section 16).
- Withdraw consent: for anything based on consent, such as location, notifications and usage analytics, at any time.
- Object to our use based on legitimate interests, and to any use for direct marketing (we do not do direct marketing).
- Restrict our use while a complaint is being resolved.
- Not to be subject to a decision based solely on automated processing that has legal or similarly significant effects, and to have a person review one (section 9).
- Complain to a data protection authority (section 18).
How to use your rights. Email [email protected] from the email address on your account and tell us what you want. We may need to confirm it is you before we act, and we will not ask for more information than we need to do that. You can use an authorized agent (such as a lawyer or, where the law allows, someone you have authorized in writing); we may ask them for proof. We will respond within one month (or within the time your local law sets, such as 45 days in US states), and we will tell you if we need longer, which the law allows for complex requests. Using your rights is free unless a request is clearly unfounded or excessive. We will never treat you differently for using your privacy rights.
If we refuse. If we cannot do what you ask, we will explain why. If you live in a US state that gives you the right to appeal, reply to our decision with the word "Appeal" and a person who was not involved will review it within the time the law sets, and tell you how to contact your state Attorney General if you disagree.
18. Extra information for your country or state
United Kingdom
UK data protection law (the UK GDPR and the Data Protection Act 2018) applies to our processing of information about people in the UK. Our UK representative is named in section 1. You can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113, though we would like the chance to help first.
European Economic Area and Switzerland
The GDPR (or the Swiss Federal Act on Data Protection) applies. You can complain to the data protection authority where you live or work, or where you think a breach happened. Swiss residents can contact the Federal Data Protection and Information Commissioner.
United States
This section is our notice under the privacy laws of California and other US states (including Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah and Virginia, as each applies). In the last 12 months we have collected these categories of personal information, from the sources and for the purposes in sections 3 to 7, and disclosed each of them for business purposes to the service providers in section 11.1 and to other riders as section 10 explains:
| Category | Examples |
|---|---|
| Identifiers | Name, username, email, account identifiers, IP address, push token |
| Customer records | Name and email address |
| Characteristics of protected classes | Age (date of birth) |
| Commercial information | Memberships and purchases |
| Internet or network activity | Use of BikeLife, clip viewing, interactions, analytics, logs |
| Geolocation data | Precise location for the features in section 4; approximate location from IP address |
| Audio, electronic and visual information | Photos and videos you post |
| Inferences | What clips you are likely to want to watch, for your feed |
| Sensitive personal information | Account log-in details, precise geolocation, and the contents of messages |
We use sensitive personal information only to provide BikeLife, keep it secure and safe, and for other purposes the law allows without offering a right to limit, so that right does not apply. We ask your consent before using precise location through your phone's permission prompt. We do not sell or share personal information, including of riders under 18. New York residents under 18: we process your personal information only as strictly necessary to provide BikeLife, or with your consent (for usage data), and your feed is not personalized. We do not collect consumer health data. We keep each category for the periods in section 14. California residents: we do not share personal information with third parties for their direct marketing purposes. Nevada residents: we do not sell covered information.
Canada
You have rights of access, correction and withdrawal of consent under PIPEDA and provincial law, including Quebec's Law 25. The person in charge of the protection of personal information is our Privacy Officer, contactable at [email protected]. You can complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information.
Brazil
Under the LGPD you may confirm whether we process your data, access, correct, anonymize, block or delete it, request portability, learn who we share it with, be told about the consequences of not consenting, and revoke consent. Our contact for data subjects (encarregado) is [email protected]. You may petition the ANPD.
Australia and New Zealand
We handle personal information in line with the Australian Privacy Principles and the New Zealand Privacy Act 2020. Your information is disclosed to providers in the countries in section 11.1. You can complain to the Office of the Australian Information Commissioner or the New Zealand Privacy Commissioner.
India
Under the Digital Personal Data Protection Act 2023, you may access, correct, complete, update and erase your data, withdraw consent, nominate someone to exercise your rights if you die or become unable to, and raise a grievance with us at [email protected] before complaining to the Data Protection Board of India. You can ask for this notice in any language listed in the Eighth Schedule to the Constitution.
Japan, South Korea and other countries
Your information is transferred to the providers, purposes, countries and retention periods listed in sections 11 and 14, by secure internet transfer when you use BikeLife. Where your local law gives you the right to refuse an overseas transfer or to receive more information about the foreign country's data protection system, contact us. Wherever you live, you can contact us to use the rights your local law gives you.
China
BikeLife is not offered in mainland China.
19. Children and teenagers
BikeLife is not for anyone under 16. We ask for a date of birth on the sign-up screen, before an account is created, in a way that does not suggest an answer. We refuse anyone under 16 (or under a higher minimum age where the law sets one) without creating an account, and a phone that has been refused stays refused. Anybody who reaches setup another way and is under the minimum age has their account and date of birth deleted straight away. We do not knowingly collect personal information from children under 13 or under the minimum age. If you believe a child is using BikeLife, email [email protected] and we will delete the account.
Teen accounts. Riders aged 16 and 17 need a parent's or guardian's permission to use BikeLife, and have a teen account until their 18th birthday. On a teen account: only riders they follow can message them or add them to a group chat; their feed is not based on what they have watched or who they follow; they get no push notifications between midnight and 6am in their time zone; they cannot host rideouts; and usage data is off unless they choose to share it. These are applied automatically from the date of birth and are shown in Settings. Parents and guardians can use the controls on their child's phone, such as Screen Time and Ask to Buy on iPhone, and can email [email protected] to ask about or delete their child's account, after we confirm they are the parent or guardian.
For everyone, including riders under 18: we never show dates of birth, never sell information, never use it for advertising, share live location only during a live rideout while the ride screen is open, and let riders block anyone and switch off message requests.
20. Security
We protect your information with encryption in transit (HTTPS), database access rules that let each rider reach only what they are allowed to, passwords stored only as hashes, sensitive information such as dates of birth and purchases kept in areas no rider can read, limited and logged staff access, and secrets kept out of the app. Messages are private to their conversation but not end-to-end encrypted. No system is perfectly secure. If a breach affects your information and puts you at risk, we will tell you and the authorities as the law requires.
21. What BikeLife stores on your phone
To work, BikeLife stores on your phone: your sign-in session (so you stay signed in), your theme choice, whether we have asked about notifications, whether you share usage data and a random analytics identifier, cached images and videos, and, if a sign-up was refused for age, a marker of that. These are needed for BikeLife to work, except the analytics identifier, which is covered by section 7. Signing out removes your session, and deleting your account clears BikeLife's data from the phone.
22. Our website
Our website, joinbikelife.com, shows information about BikeLife and these documents. It does not use advertising or analytics cookies. Cloudflare, which runs our network, may set strictly necessary cookies to protect the site from attacks. Photos and videos are delivered from media.joinbikelife.com, which records IP addresses in security logs as section 3.2 explains.
23. Changes to this policy
We will update this policy when what we do changes. If a change is significant, we will tell you in the app or by email before it takes effect, and where the law requires, ask for your consent. The date at the top shows when it last changed.
24. Contact and complaints
Email [email protected] or write to BikeLife Network LLC, 228 Park Ave S, PMB 362349, New York, NY 10003-1502, United States, marked "Privacy". We will reply as soon as we can and within the time the law sets. If you are not happy with our answer, you can complain to your data protection authority (section 18).