Back to home

Privacy Policy

Last updated: 8 November 2026

This policy explains what RidePals collects, why, and who can see it. It was written from what the app actually does today, not from a template.

What this covers

The RidePals app and this website. RidePals is for adults (18 or over) and we do not knowingly collect information from anyone younger. If what we collect changes, this page changes with it.

Who is responsible for your data

RidePals is run by Eduardo José Fernández Díaz, as an individual, at Condominio Caoba, San José, Mora, Ciudad Colón 10701, Costa Rica, who is responsible for your data. For anything about it, write to us through the contact form on this site.

Why we can use your data

Each use of your data rests on a legal basis:

  • Your account and running the app (your profile, rides, clubs and Pals): the contract you accept when you create your account, that is, the terms of use and this policy.
  • Your emergency contact, Strava verification, notifications and your location: your consent, which you give when you turn each one on and can withdraw at any time (see “Withdrawing your consent”).
  • Reports, blocks and the log of who viewed an emergency contact: our legitimate interest in the safety of the people who share a ride and in being able to follow up a safety report, where the law of your country recognises it. Where it does not, they rest on the consent you give when you create your account.
  • What the law requires us to keep or hand over, such as copyright notices: compliance with a legal obligation.

Your account

When you sign up we store your name, your email address and your profile photo: the one your provider supplies, if it does, or one you upload. You can create an account with an email and password, with Google, or with Apple. If you use “Sign in with Apple” and choose to hide your email, we receive the private relay address Apple generates and that is the only address we hold. We also store the preferences you set on your profile, such as your discipline and your country, and what you do in the app so that it works: which rides you join, who you save as a Pal, who you block or report, and when you accepted the terms. When you create your account we ask for your birth year to confirm you are 18 or over. The check happens on your phone: we don't keep the year, only the date you completed that step.

Your emergency contact

You can save the name and phone number of a person to contact in an emergency. The contact's name and number are information about someone else, so please only add them with that person's permission.

Who can see it

Every rider who has joined the same ride as you (not only that ride's host), and only from 2 hours before the start until 1 hour after the ride ends. If the ride does not say how long it lasts, we count 4 hours. Outside that time, or if the ride is cancelled, it cannot be read. It is never public, never shown to anyone who has not joined your ride, and is not used for any other purpose. Someone you have blocked cannot see yours, and you cannot see theirs.

Every view is logged: we record who viewed it, whose it was, which ride, and when. Platform administrators can review that log.

So that it still opens after a crash with no signal, the app copies the emergency details of everyone on a ride onto the phones of the other riders on that ride. That copy sits in the app's own storage on their device, and we cannot reach into it to erase it. It is only made inside that same window, the app deletes it the next time they open the app after the window closes, and it goes when they uninstall the app.

The person you add is not a user of the app and cannot be notified by us, which is why we ask you to add them only if they agreed to it.

You can change or remove it at any time from your profile, and it is deleted along with your account.

Rides and clubs you create

When you create a ride or a club we store what you write: the title, description, date, meetup point and any images you upload, such as a club logo or banner. This is visible to other people using RidePals, and public rides and clubs can also be seen on this website without signing in. The public map publishes only an approximate area for the meetup point. The exception is the ride link a participant shares: anyone with that link sees the exact meetup point and who is going, without needing an account. If you attach a route file to a ride, we store that route and show it to the riders who joined; route files are not public and are not published on this website.

If you join a ride as an “Anonymous Rider”, the other riders on it see that name instead of yours, and the ride's shared link does not show your name either. The ride's host does see who you are. From 2 hours before the start until 1 hour after it ends, the riders who joined it can see your emergency contact, as with everyone else. If someone reports you, the report reaches the administrators linked to your account, and so does the log of who viewed your emergency contact.

Strava, if you choose to verify

Linking Strava is optional to use RidePals, but it is the only thing that grants the “Verified” badge, and you need to be verified to create a ride or a club. If you only join rides, you never need to link anything. If you do, we read your profile and recent activities once, to count how many cycling rides you have in the previous six months. If you have at least three, which is what the “Verified” badge requires, we keep only that: that you are verified and the date we checked. If you have fewer than three, we keep nothing. We revoke the permission immediately afterwards. We do not store your Strava tokens, we do not keep your activities, and we have no ongoing access to your account. Other riders see only your “Verified” badge, never your Strava activities or your Strava profile. We do not keep your Strava id or username. So that one Strava account verifies only one RidePals account, we keep a code computed from your Strava id, from which the id cannot be recovered, and it is deleted with your account.

You can withdraw your consent at any time. Because we lose access to your Strava account right after the check, all that is left is what we keep: that code and your badge. To have them deleted without deleting your account, write to us through the contact form (see “Your rights”); you lose the badge, and with it the ability to create rides and clubs. Deleting your account deletes them too. Either way, we confirm it is done: the app tells you when your account is deleted, and we write to your account email when we delete them because you asked.

Strava may also collect data about how RidePals uses its services and use it for any business purpose. That is governed by Strava's privacy policy, not this one.

Automated decisions

The app makes two decisions automatically, without a person reviewing them. The first is Strava verification: if you have at least three cycling rides in the previous six months, you get the “Verified” badge, which is needed to create rides and clubs. The second is the age check: it uses the birth year you give and, where the app store offers one, the store's age signal, and it does not let anyone under 18 use the app. We do not build profiles about you or make any other automated decisions. If you think one of them is a mistake, write to us through the contact form.

Notifications

If you turn on notifications we store your device's notification identifier, whether it is iOS or Android, and the app's language, so we can tell you what is happening on your rides. It is deleted along with your account.

Your location: used for a moment, never kept

The app asks for your location only while you are using it, never in the background, and uses it in three ways: to centre the map where you are; to find rides within 10 km for Near Me, which sends your coordinates to our server for that one search; and, when you create a club, to suggest your city, which sends them once to Google to look it up. We do not save your location or share it for any other purpose. If you decline the permission the map still works: it opens on the national view.

The permissions you will see on the store

The app's Google Play listing names the permissions the package declares, and there are more of them than the app's features use. Only two are ours: location, to centre the map and find rides near you. The rest are added by the libraries the app includes: notifications, the map, the image picker, the secure storage that keeps you signed in. We removed the ones with no feature behind them: RidePals does not ask for the camera, the microphone, or permission to draw over other apps. We do not take photos, we do not record audio, and we do not read your biometrics. Android will ask you at the moment we need the ones we do use, and you can say no.

This website

If you write to us through the contact form we store your message, your email address, your name if you choose to give one, the IP address the message was sent from, and your browser's identifier (user agent). The IP is kept to limit abuse of the form. Beyond that, this site asks nothing of you to browse it.

Copyright notices

If we receive a copyright notice about your content, we may share it with you. If you send a counter-notice, we give your name, address and phone number to the person who sent the notice, because the law requires it. We keep notices and counter-notices as records. Those sent by email to support@ridepalsapp.com pass through Namecheap's email forwarding and are received in our Gmail inbox, provided by Google.

Who else processes this data

We do not sell your data and we do not share it with advertisers. The services we use to make RidePals work are:

  • Supabase: our database, sign-in, and image storage. Its servers are in the United States.
  • Amazon Web Services: hosts this website, in the United States.
  • Expo: delivers notifications to your device.
  • Namecheap: forwards email sent to support@ridepalsapp.com, including copyright notices, to our inbox.
  • Resend: sends the account emails (confirming your address, resetting your password) and emails us the notification when someone uses the contact form.
  • Google: Google sign-in if you choose it, the map on Android, and place search inside the app. What you type when searching for a meetup point is sent to Google to fetch the suggestions. When you create a club, your location is sent to Google once to suggest your city. Our inbox is also in Gmail: that is where email sent to support@ridepalsapp.com is received.
  • Apple: “Sign in with Apple” if you choose it, and the map on iOS.
  • Strava: only if you choose to verify, and only that once.
  • OpenStreetMap: supplies the map imagery on this website, so their server receives the IP address of anyone who visits it.

Several of these services, starting with Supabase and Amazon Web Services, store or process data in the United States. Chile and Argentina do not recognise the United States as offering an adequate level of protection, so we do not rely on your consent alone: Supabase, Amazon Web Services and Resend are bound by contract to protect your data under the standard contractual clauses approved by the European Union, and Resend is also certified under the EU-U.S. Data Privacy Framework. Whether those guarantees are enough in Chile is for its new Agency to decide. Two services offer no such contract: Expo, which delivers notifications, and our Gmail inbox, which is a personal account. Google, Apple and Strava receive what is described above as independent controllers, under their own terms. We send your data there because that is needed to provide the service you asked for, and with the consent you give when you create your account and accept this policy. If you only use this website, for example to write to us, we send your message there in order to answer it.

Cookies and analytics

This site uses no tracking cookies and no analytics tools, and the app ships no advertising or tracking SDK. There is no cookie banner because there is nothing to consent to.

Because neither this website nor the app tracks you across other sites, your browser's “Do Not Track” signals change nothing about what we do.

How we protect your data

Your data travels encrypted between the app, this website and our servers, and our hosting providers (Supabase and Amazon Web Services) store it encrypted. In the database, access rules decide what each account can read: for example, an emergency contact can only be read by riders on the same ride, and only inside the window described above. Every time someone views it, it is logged. If a security breach happened, we have a written plan to contain it, assess it and notify the authority and the people affected when the law requires it. No system is infallible, and we do not promise you otherwise.

How long we keep data

Your account's data is kept for as long as you have the account. For the rest:

  • contact form messages, including club reports sent from this site, the IP address and the browser identifier, are kept for 12 months from when they arrive. Each message also reaches us by email, and that copy is kept separately in our inbox, without that limit;
  • reports made in the app are kept for up to 24 months after they are closed, and then deleted;
  • the log of who viewed an emergency contact is kept until the viewer's account, the viewed rider's account or the ride is deleted; until then it has no time limit.

We delete contact messages and reports by hand, at least once a year, so one can stay up to a year past its limit.

How to delete your account

You can delete your account at any time from your profile in the app, without writing to us or asking permission. Doing so deletes:

  • your profile, your name and your photo;
  • your emergency contact;
  • any route files you attached to rides you hosted;
  • the log of who viewed your emergency contact;
  • your devices' notification identifiers;
  • the rides you hosted and the clubs you own, along with their sign-ups.

No longer have the app, or can't open it? Ask us to delete your RidePals account through the contact form on this site, writing from the email address on the account so we can confirm it is yours. We delete the same data listed above.

Images you uploaded for a club or as a profile photo are deleted along with your account. Copies already downloaded to a device, or briefly held in our content cache, may persist for a short time. The same is true of the emergency details copied onto the phones of riders you rode with, described above.

Reports you filed, or that others filed about you, are kept after your account is deleted so that a safety case can be followed up. They are no longer linked to a profile, keep their text as it was written, and are deleted within the period given above.

Your rights

You can ask us to show you the data we hold about you, to correct it, to delete it (except what this policy says we keep, such as reports), to object to our using it, or to receive a copy to take to another service.

Write to us through the contact form giving the email address on your account. We confirm the request by writing to that address; if you hid your email with Apple, tell us and we will confirm it another way. We answer within 5 business days. Deleting your account needs no request: you can do it yourself in the app, as described above.

If you ask for a copy, we send it to your account email in a common file format other services can read (JSON or CSV), within the same time. We prepare it by hand: the app has no download button.

Withdrawing your consent

You can withdraw your consent at any time, for each use that depends on it:

  • Emergency contact: remove it from your profile.
  • Notifications: turn them off in your phone's settings.
  • Location: remove the permission in your phone's settings.
  • Strava: ask us to delete your verification, as explained in “Strava, if you choose to verify”.

Withdrawing it does not make unlawful what we did with your data while you had given it.

If you disagree with our answer

If we do not answer in time, or you disagree with how we handled your request, you can complain to the data protection authority of your country:

LA AGENCIA DE ACCESO A LA INFORMACIÓN PÚBLICA, en su carácter de Órgano de Control de la Ley N° 25.326, tiene la atribución de atender las denuncias y reclamos que interpongan quienes resulten afectados en sus derechos por incumplimiento de las normas vigentes en materia de protección de datos personales.

Translation: The Agency for Access to Public Information, as the supervisory body of Law No. 25,326, has the power to handle the complaints and claims filed by anyone whose rights are affected by a breach of the rules in force on personal data protection.

Changes to this policy

This policy may change. The current version is always at this URL, and the date shown above is when it was last updated.

Contact

Questions about your data, or want something deleted? Get in touch through the contact form on this site.