Who is responsible
This policy applies to the Bikopía app for Android and iOS (package app.bikopia), to the web version at go.bikopia.app, to its API at api.bikopia.app, and to this website, bikopia.app.
The controller of your data is the operator of Bikopía. You can write to us at gajosu15@gmail.com about anything related to your data.
What data we collect and why
You can explore the map and plan routes without an account. To save routes, report issues, record rides, or receive notifications, you need to sign in.
1. Account data
- What: name, username (@username), email, and password.
- Why: to create your account, identify you when you sign in, and show your @username next to content you publish.
- How: the password is never stored in plain text; we keep only a hash (PBKDF2-SHA256). To keep you signed in we use an access token and a refresh token; of the refresh token we store only its hash. It is renewed with use and expires after 30 days. Signing out revokes it.
Today you can only sign in with email and password. There is no Google or Apple sign-in.
2. Precise location
- What: your GPS position, only if you grant the app location permission. The permission is optional, but without it the map features that depend on where you are will not work.
- Why: to show you on the map, plan a route from where you are, record a ride, and give you turn-by-turn navigation.
- When: while you are using the app. On Android, during navigation the app uses a foreground service that shows a persistent notification for as long as it is active. We do not request background location when you are not using the app.
3. Sharing your live location (optional)
- What: the map has a “Share my location” switch. It comes off. If you turn it on, we send your precise position, heading, identifier, and @username in real time.
- Who can see it: other cyclists looking at the same area of the map (cells of about 5 km).
- How to stop: turn the switch off whenever you want; you stop sharing at that moment.
4. Recorded rides
- What: the GPS trace, date and time, distance, duration, elevation, the split by type of road, the title, and, if applicable, the planned route you followed. You can also upload a GPX file.
- Why: so you have your history and your stats.
- Who can see it: your rides are private to your account, unless you choose to save one as a public community route. During navigation, the live trace is stored temporarily on our server until the ride ends.
5. Community routes
- What: title, description, path, elevation profile, author, votes, favorites, and edit proposals.
- Who can see it: routes you publish are visible to other users, with your @username as the author. Drafts or unpublished routes are only visible to you.
6. Map reports
- What: type of report (pothole, closure, works, car in the bike lane), location, place name and note if you add them, your @username, and a photo if you attach one.
- Who can see it: anyone looking at that area of the map.
- How long it lasts: reports expire or are marked as resolved.
7. Push notifications
- What: the notification token for your device (Expo Push) and its platform (Android or iOS), tied to your account.
- Why: alerts such as “send to phone” for a route or a plan from the web.
- How to stop: when you sign out, the device is no longer registered. You can also turn off notifications in your phone settings.
8. Routes sent to your phone
If you send a route or a plan from the web to your phone, we store the title, destination, stats, and the plan’s path so it can appear in the app.
9. Place search
When you search for an address or a place, the text you type goes through our API, which looks it up in Photon (from Komoot) and, if that fails, in Nominatim (from OpenStreetMap).
10. Data stored on your device
The character you choose and your session are stored on your own device: in the system’s secure store on mobile, or in the browser’s local storage on the web.
11. The “Count me in” form on this website
The beta form on bikopia.app is a mockup for now: it validates the email in your browser and does not send it or store it on any server. If we later connect it to a waitlist, we will update this policy before doing so.
What we do not do
- We do not sell your data or use it for advertising. The app does not show third-party ads.
- We do not use third-party analytics or crash-reporting tools inside the app.
- There are no in-app purchases.
- There is no chat between users. The only real-time features are reports and, if you turn it on, your presence on the map.
- Group rides do not exist yet (“coming soon”); we do not collect data for them today.
What other people can see
- Whenever you publish something: your @username next to your published routes and your reports.
- Only if you turn it on: your live position, for anyone looking at your area of the map.
- Never: your email, your password, your private rides, or your unpublished routes.
Providers that process data
To make Bikopía work we use these services. They process data on our behalf and only as needed for the service they provide to us:
- Cloudflare: hosting for the website and the API (Workers), content delivery, the database for accounts and sessions (D1), files such as GPX and photos (R2), real time and in-progress rides (Durable Objects), and the database connection (Hyperdrive).
- Supabase: a Postgres database with PostGIS for geographic data: routes, rides, reports, and the road network.
- Mapbox: the map. To draw it, your device requests the tiles and styles for the area you are looking at.
- Expo: delivery of push notifications.
- Google Firebase Cloud Messaging: delivery of push notifications on Android.
- Komoot Photon and Nominatim (OpenStreetMap): place search.
- Google Fonts: the typefaces on this public website; your browser downloads them from Google’s servers.
Some of these providers may process data outside your country. We may also disclose data if a law or a competent authority requires us to.
How long we keep the data
- Your account data, rides, and routes, for as long as you have the account.
- Sessions expire after 30 days without renewal and are revoked when you sign out.
- Reports, until they expire or are resolved.
- The shared live location is used in real time and stops being sent when you turn the switch off.
If you delete your account, we delete your data as explained in Delete account.
Security
All traffic between the app, the website, and our servers is encrypted with HTTPS (TLS). Passwords are stored as hashes, and refresh tokens are too. Your data is stored with the providers listed above. No system is infallible; if we detect a security issue that affects your data, we will tell you.
Your rights and how to exercise them
You can ask us at any time to:
- Access the data we have about you and receive a copy.
- Correct inaccurate data.
- Delete your account and your data (here is how).
- Object to a processing activity or ask us to restrict it.
Write to us at gajosu15@gmail.com from the email on your account and include your @username. We respond within 30 days. If you are not satisfied, you can go to the data-protection authority in your country; in Ecuador, the Superintendencia de Protección de Datos Personales.
You can also, without writing to us: turn off “Share my location,” remove location or notification permission in your phone settings, leave routes unpublished, and sign out.
Children
Bikopía is not directed at children under 13, and we do not knowingly collect data from children under that age. If you believe a child has given us their data, write to us and we will delete it.
Changes to this policy
If we change how we process your data, we will update this page and the date above. If the change is significant, we will let you know in the app or by email before it takes effect.
Contact
Operator of Bikopía · gajosu15@gmail.com · bikopia.app
See also the Terms and conditions.