Zyflow Privacy Policy
Version: 2.7 · Effective date: 17 November 2026 · Replaces version 2.6 of 17 November 2026
This Privacy Policy explains how HERKO d.o.o. processes personal data when you use the Zyflow mobile app (iOS and Android) and the Zyflow websites zyflow.eu, app.zyflow.eu and navigate.zyflow.eu. It is written to meet the requirements of the EU General Data Protection Regulation (GDPR), the Slovenian Personal Data Protection Act (ZVOP-2) and the Slovenian Electronic Communications Act (ZEKom-2).
1. Who is responsible (controller)
HERKO d.o.o., Pševska cesta 10, 4000 Kranj, Slovenia
Registration number (matična številka): 8830045000 · Tax number: 56613555 · VAT ID: SI56613555
Director: Jakob Robič
Privacy contact: legal@zyflow.eu
We have not appointed a data protection officer. For any privacy question or request, write to legal@zyflow.eu.
2. Summary
- We collect only what we need to run Zyflow: your account, the routes and content you create, and technical data to keep the app working.
- Your routes are private unless you decide to share a specific route with the community.
- We do not sell your data and we do not show ads in the app.
- Until you decide, the app counts how it is used anonymously, without any identifier, so we can improve it; you can object in Settings. Detailed product analytics use a pseudonymous user ID, not your email address, and only run if you agree.
- Location is used only while the app is in use. There is no background location tracking.
- Push notifications reach you only if you allow them on your phone. News and offers, by push or by email, stay off until you turn them on.
- You can delete your account in the app at any time.
3. What data we process, why, and on what legal basis
3.1 Account data
Data: email address, full name, optional phone number, user ID, sign-in method, account creation date. If you sign in with Apple or Google, we receive your email address and, if you allow it, your name from that provider (with Apple you can hide your real email address). With Google sign-in we also receive a link to your Google profile picture, which we store with your profile and show only to you.
Purpose: to create and manage your account, sign you in and provide the service.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Profile photo (optional): if you add a profile photo, we store it in private file storage; it is visible only to you. You can change or remove it at any time in your profile, and it is deleted when you delete your account.
3.2 Location data
Data: precise location of your device, only while the app is in use and only if you grant the location permission. We do not collect location in the background.
Purpose: show your position on the map, plan and navigate routes, find nearby places and show weather and traffic alerts.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR). Access to location on your device is controlled by your operating system permission, which you can withdraw at any time in your device settings. Without it, some features will not work.
Your live position is not stored on our servers. It is stored only if it becomes part of something you save, share or submit (see 3.3 to 3.5). When you collect a stamp, your position is used to check that you are at the place and is not stored; the stamp records the place and the time (see 3.17). Some location data is sent to map, search and routing services to answer your request (see 3.11).
3.3 Routes (saved, planned and imported)
Data: routes you plan and save, routes you import from GPX, FIT or TCX files or from a connected service (3.15), route names, notes, distance, duration, elevation and other route details, and saved places.
Purpose: to let you plan, save, export and reuse routes.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Visibility: saved routes are private and visible only to you, unless you share a route with the community (3.4).
Please note that a saved route is a record of where you have been or plan to go.
3.4 Community route sharing (optional, per route)
You can choose to share an individual saved route with the Zyflow community. Nothing is shared automatically; you decide for each route.
What becomes visible when you share a route: the full route GPS track (all points, including the start and end point), route name, your optional description, region, difficulty, distance, duration, elevation and surface details, an automatically generated map image, and any photos you add.
Who can see it: all signed-in Zyflow users. Route photos and map images are stored in publicly accessible storage, which means anyone who has the link to a photo or image can open it, also without a Zyflow account. Your name and email address are not shown with the shared route, but the route is linked to your user ID in our database.
Important: the start and end points of a route can reveal where you live, work or regularly park your bike. Before sharing, consider starting and ending the route a little away from your home, and do not include personal details or photos that identify people, house numbers or licence plates.
Removing a shared route: you can remove a shared route at any time. This removes it from the community, so other users can no longer see it, and deletes its photos from our file storage. If you also want its map images removed from our file storage, write to legal@zyflow.eu and we will remove them within 30 days; they are also deleted automatically when you delete your account. Copies that other users have already saved to their own accounts may remain in their accounts.
Purpose: to let riders discover and reuse routes shared by others.
Legal basis: performance of a contract at your request (Art. 6(1)(b) GDPR) – sharing is a feature you actively choose to use for each route.
3.5 Place reports and missing-place submissions
Data: when you confirm or report whether a point of interest (for example a charger, repair station or water tap) exists or works, we store your report, any notes, the time and your user ID. When you report a missing or wrong place, we store the location, the details you enter, your user ID, your email address and the time.
Visibility: place reports are shown to other users as community signals without your name. Missing-place submissions are seen only by our team during review. Approved places become part of the Zyflow places database without any link to you.
Purpose: to keep place information accurate for all riders, and to inform you about the status of your submission by email.
Legal basis: legitimate interest in an accurate, community-verified places database (Art. 6(1)(f) GDPR). Please do not include personal data in notes.
3.6 Bike passport (optional)
Data: bike make, model, colour, frame number, purchase date, purchase value, notes and bike photos, and optionally your rider weight.
Purpose: to let you keep a record of your bike (for example to help in case of theft or for insurance) and to generate a bike passport document on your device. Rider weight is optional and is used only for route calculations (for example effort and time estimates). It is not used for any other purpose and is never shared.
Visibility: private to you. Bike photos are stored in private storage.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR). All fields are voluntary and you can delete them at any time.
3.7 Camera and photo library
If you allow it, the app uses the camera and photo library only when you choose to add a photo (bike photos, route photos, place reports, profile photo) or save an image. We do not access your photos in the background. You can withdraw the permission in your device settings.
3.8 Emails
We use Brevo to store your contact details (email address, full name and user ID) and to send emails from Zyflow. Creating an account adds your contact details to Brevo, but not to any mailing list.
Service emails: account and security emails (for example sign-in codes and confirmations when you change your email address) and updates about places you submitted. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Marketing emails ("Ride ideas and Zyflow news"): we send these only if you turn them on yourself in the app under Profile → Settings → Notifications → By email. The option is never switched on for you. When you turn it on, we add you to our mailing list at Brevo; when you turn it off, we remove you from it. We record your choice, when you made it and where in the app, so that we can show what you agreed to. You can withdraw consent at any time in the app, via the unsubscribe link in each email or by writing to legal@zyflow.eu. Legal basis: consent (Art. 6(1)(a) GDPR and ZEKom-2).
What we send today: marketing emails go only to people who turned them on. When you turn them on, you receive a short series of welcome emails about Zyflow, followed by occasional news. If you don't turn them on, you receive no marketing emails, including welcome emails.
3.9 Product analytics
Anonymous usage statistics. Until you decide about product analytics, and unless you object, the app sends anonymous usage events to PostHog (EU cloud, acting as our processor): which screens are opened and which steps are taken in the app (for example "onboarding finished" or "route planned"), the app version and basic device information (platform and operating system version). These events carry a random number that exists only while the app is open and is never stored on your device, so they cannot be linked to you, to your other app sessions or to your account. They contain no IP address (PostHog discards it), no location, no name, email address or user ID, and no error details. Separately, the app counts app starts and a few key moments (for example "onboarding finished" or "stamp collected") as daily totals in our own database, with no identifier of any kind; to count each moment at most once a day, the app keeps a short list on your device of the moments already counted today. We use these statistics only to measure and improve the app, never for advertising, and we do not share them.
Legal basis: our legitimate interest in measuring and improving the app (Art. 6(1)(f) GDPR). No identifier is stored on or read from your device for this purpose. You can object at any time in Settings → Anonymous usage statistics (shown until you decide about product analytics). If you said no to product analytics, the app sends nothing to PostHog.
Product analytics (with your consent). If you agree, we use PostHog (EU cloud) to understand how the app is used over time and to improve it. We send a pseudonymous user ID (not your email address or name), selected in-app events (for example "route planned" or "GPX exported"), app version and basic device information. If you agree, PostHog also records technical details of app errors (the error message and where in the app it happened) so we can fix them. Automatic capture of all interactions and session recording are not used in the app. PostHog is set to discard your IP address. When you agree, the app starts with a new identifier; what you did before agreeing stays anonymous and is not linked to you.
Legal basis: your consent (Art. 6(1)(a) GDPR and ZEKom-2). The app asks you before these analytics start; they are off until you agree. You can withdraw consent at any time in Settings → Share usage statistics; this does not affect processing before withdrawal.
3.10 Crash and performance monitoring
We use Sentry (EU data region) to detect and fix errors. Error and performance reports contain your user ID, technical details of the error, device model, operating system and app version, and your IP address, which is stored with error reports. Sentry's data scrubbing is enabled to remove sensitive values such as email addresses.
Legal basis: legitimate interest in a stable and secure app (Art. 6(1)(f) GDPR).
3.11 Maps, search, routing and weather
To answer your requests, some data is sent to the following services. Each of them also sees an IP address as part of normal internet traffic.
- Map tiles (MapTiler): your device requests map tiles directly, so MapTiler sees your IP address and the map area you view.
- Place search (Photon by komoot): your search text is sent through our own server, so Photon does not see your IP address.
- Reverse geocoding (Nominatim, OpenStreetMap Foundation): your device sends coordinates directly to turn them into an address, so Nominatim sees your IP address and those coordinates.
- Routing (our own OSRM server at osrm.zyflow.eu and GraphHopper): route coordinates are sent to our self-hosted routing server (hosted on Contabo servers in Germany, EU) and, through our backend, to GraphHopper.
- Fallback routing (public OSRM demo server): if our own routing server is unavailable, the app may use the public OSRM demo server (router.project-osrm.org, provided by the OSRM project, project-osrm.org, which is based on OpenStreetMap) to calculate your route. In that case your device sends the route coordinates directly to that server, which therefore also sees your IP address. We do not control this server.
- Weather (Open-Meteo): an approximate location is sent through our backend.
- Translation (DeepL): we translate public traffic-alert texts. No personal data about you is sent.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
3.12 Accommodation links (Stay22)
Some places show accommodation links from our affiliate partner Stay22. Only if you tap such a link, the link opens Stay22's service and passes the coordinates and name of that place (not your account data). Links to Stay22 may be affiliate links: if you book through them, we may receive a commission. After you open the link, Stay22 and the booking sites it uses are independent controllers and their own privacy policies apply.
Legal basis: legitimate interest in financing the free app (Art. 6(1)(f) GDPR); the transfer happens only on your action.
3.13 Security and abuse prevention
Our search function stores the IP address of the requesting device together with request counters for a short time to prevent abuse (rate limiting). We keep these records only as long as needed to prevent abuse and delete them regularly. Search texts are cached for up to 24 hours without any link to you or your IP address. Our hosting providers keep technical server logs (including IP addresses) for security.
Legal basis: legitimate interest in the security of our service (Art. 6(1)(f) GDPR).
3.14 Data stored on your device
The app stores your login session, your last known location, your recent searches, the date it last offered you notifications, stamps waiting to be sent while you have no signal (with the GPS reading taken at the place and any answers) and the places it reminded you about today locally on your device so that the app works quickly, you stay signed in, stamps collected without signal are not lost and we do not ask about notifications or remind you too often. This storage is strictly necessary for the service you request. It is removed when you uninstall the app.
If you agree to product analytics, PostHog also stores a pseudonymous identifier on your device; otherwise PostHog stores nothing on your device (anonymous usage statistics use a random number kept only in memory while the app is open). To count key moments at most once a day (see 3.9), the app stores today's date, the app version and the names of the moments already counted; this contains no identifier. If you object to anonymous usage statistics, the app stores that choice. Sentry stores a pseudonymous identifier for crash reporting (see 3.10).
3.15 Connected services (optional)
You can connect your Zyflow account to other cycling services. Connecting is always optional, you choose each service yourself, and you can disconnect at any time in Profile → Connected services.
| Service | What you can do | What we receive and store |
|---|---|---|
| Strava (Strava, Inc., USA) | Import your rides and your saved Strava routes; get stamps from your past rides (3.17) | Your Strava athlete ID; the rides and routes you choose to import (name, GPS track, distance, elevation, date); for up to 7 days, the route line of rides and routes shown in your list, for map previews; if you choose stamps from your rides, the positions and times of your past bike rides, used once to find where you stopped and not stored |
| Garmin Connect (Garmin Ltd. and its affiliates) | Send routes to your Garmin device; import finished rides | Your Garmin user ID and the permissions you granted; routes you send; rides you choose to import |
| Wahoo (Wahoo Fitness L.L.C., USA) | Send routes to your Wahoo bike computer; import finished rides | Your Wahoo user ID; routes you send; rides you choose to import |
| Hammerhead (SRAM, LLC, USA) | Send routes to your Karoo; import finished rides | Your Hammerhead user ID; routes you send; rides you choose to import |
| Ride with GPS (Ride with GPS, Inc., USA) | Import your routes and rides; send routes | Your Ride with GPS user ID; the routes and rides you choose to import; routes you send |
How it works: when you connect a service, you sign in on that service's own page; Zyflow never sees your password there. The service gives us an access token, which we store encrypted and use only to do what you ask: send a route you chose, list your rides or routes so you can pick what to import, import the items you select, and, if you choose stamps from your rides, read your past rides to find where you stopped (3.17). When you send a route, we keep a note of where it went, so we can show "Sent to …" and remove the copy if you delete the route in Zyflow.
Map previews (Strava): to show a small map behind each ride and route in your Strava list, we keep its simplified route line for up to 7 days and draw the picture on our own server (hosted by Contabo GmbH, Germany, EU) using MapTiler map tiles. MapTiler only sees which map area our server asks for, not who it is for. The lines and pictures are visible only to you. We delete them after 7 days, when you import the ride or route, or immediately when you disconnect Strava.
Visibility: data from connected services is shown only to you. It is never published to the community, and routes imported from Strava cannot be shared. We never sell this data or use it to train artificial intelligence models.
Disconnecting: when you disconnect a service, or delete your Zyflow account, we revoke our access at that service and delete the stored token and user ID. When you disconnect Strava, we also delete the rides and routes you imported from Strava. Stamps from your rides stay in your stamp book when you disconnect Strava (they contain no ride, ride ID or GPS track), and so does the record of how far your rides were read; both are deleted when you delete your account (3.17). Routes imported from other services stay in your saved routes until you delete them. Copies of routes we sent to a device service remain in your account there; delete them in that service's app if you no longer want them.
Legal basis: performance of a contract at your request (Art. 6(1)(b) GDPR). Each service is an independent controller for the data it holds about you; its own privacy policy applies.
3.16 Notifications (push and in the app)
When we ask: the app does not ask about notifications when you open it or when you sign up. After you save a route or a place, it may offer to let you know about it, for example when the weather is good for that route. You can also turn notifications on yourself in the app's notification inbox. Your phone's own permission prompt appears only after you tap "Turn on notifications". If you tap "Not now", the app does not offer again for at least 14 days. You can allow or block notifications for Zyflow at any time in your phone's settings.
What we store: if you allow notifications, the app gets a push token for your phone through our push provider Expo. A push token is an address for the Zyflow app on that phone; it contains no name, email address or location. We store the push token with your user ID, the date it was created and last updated, and the build number of your phone's operating system. We also store your notification settings and the notifications we send you, which you can read in the app's notification inbox: title, text, type, time, whether it was sent by push and when you read it.
How push notifications are delivered: we pass each push notification to Expo (650 Industries, Inc., USA), which hands it to Apple Push Notification service (iPhone) or Google's Firebase Cloud Messaging (Android) to deliver it to your phone; on Android we can also send it to Firebase Cloud Messaging directly. They receive the push token, the title and text of the notification and an internal notification ID. The text can name a route or place you saved. We do not send your email address or your location with a push notification. Apple and Google deliver push notifications under their own terms and privacy policies.
What decides what we send: the routes and places you saved, your notification settings and public data such as weather forecasts. We do not use your live location for notifications and do not track your location in the background.
Notification groups and defaults:
| Group | Examples | Default after you allow notifications | Legal basis |
|---|---|---|---|
| Your rides & places | Severe weather, battery and charging alerts for your rides and saved places | On | Contract, Art. 6(1)(b) GDPR |
| Your contributions | Updates on places you suggested, approved partner access | On | Contract, Art. 6(1)(b) GDPR |
| News & offers | Zyflow announcements, new offers and promotions | Off until you turn it on | Consent, Art. 6(1)(a) GDPR and ZEKom-2 |
The first two groups are part of the service you use. News & offers are sent only if you turn them on; you can turn them off again at any time, without affecting what was sent before.
Changing your choice: under Profile → Settings → Notifications you can turn each group of notifications on or off, both as push notifications and in the inbox. You can also block all Zyflow notifications in your phone's settings; then no push notifications reach you, but the groups you left on still appear in the app's inbox.
3.17 Stamp book
What it is: when you are at a place (within about 150 metres), you can collect a stamp for it in the app. You collect stamps yourself, on the spot. The only other way to get a stamp is from your past rides, and only if you connect Strava and choose it (see "Stamps from your rides" below).
Data: when you collect a stamp, the app sends your current position, its GPS accuracy and the time of the reading to our server. The server checks that you are at the place, that the reading is recent and that you could have travelled there since your previous stamp. Your position is used only for this check and is not stored. We store the stamp: the place, its level (bronze or silver), the date and time of each counted visit (at most one per place per day), how far from the place you were, the GPS accuracy and your user ID. If you answer questions about the place for a silver stamp, your answers are stored as place reports (3.5).
Reminders in the app: while the Home screen is open and you have allowed location, the app can remind you when you have been near a place you have not stamped yet for about two minutes. This happens only while you use the app. To find places near you, the app asks our server for places around your position; the position is not stored, and nothing about the reminder is stored on our servers.
Without signal: if you have no signal, the stamp, the GPS reading taken at the place and any answers wait on your phone and are sent when you are back online; the server then makes the same checks. Once sent, they are removed from your phone.
Stamps from your rides (Strava, optional): if you connect Strava and choose to get stamps from your past rides, we read the list of your activities on Strava and, for each bike ride with GPS, its positions and their times. From these we find the places where you stopped: you stayed within 60 metres for at least 2 minutes, not counting stops near the start or end of the ride. A stop gives a stamp only if a place in Zyflow that has a stamp is within 60 metres of it; for accommodation, the stop must have lasted at least 30 minutes. The positions and times are used once, only for this, and are not stored: we keep no ride, ride ID, GPS track or position of the stop. For each place found we store a bronze stamp marked "from a ride": the place, the date and time of the earliest and latest stop we found there, how far the stop was from the place, and your user ID. We also store how far reading your rides has got (number of rides, rides read, stamps added and the date of the oldest ride read), so that we can carry on later. The newest rides are read while you watch; older rides are read in the background, a few at a time about every 15 minutes, because Strava limits how many requests we may make. We read only the rides that were on Strava when you connected it for stamps; later rides are not read. Stamps from your rides are not counted in the numbers other riders see. When you later collect the same stamp on the spot, it becomes an ordinary stamp.
Before you have an account: you can do this in the app's first steps, before you sign up. The app then makes a random code (a guest pass) that stays only on your phone; our server stores only a fingerprint of it (a hash). Your Strava connection (encrypted token and athlete ID), the stamps found and the reading progress are kept under this code, not under a name or an account. When you sign in or sign up, they move to your account. If your account already has a different Strava account connected, your account keeps its own connection, and the one made in the first steps is revoked and deleted. If you do not sign in within 14 days, we delete them and revoke our access at Strava. After the move, we keep the code's fingerprint, its reading counts and the link to your account for 30 days, then delete them.
Visibility: your stamp book is private and visible only to you. Other users see only counts without names, for example how many riders have a stamp at a place or have finished a collection. Stamps from your rides are not included in these counts.
Purpose: to let you collect stamps for the places you visit by bike, and to keep stamps fair.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR); collecting stamps and getting stamps from your rides are features you choose to use. Before you have an account, we act on the same basis, at your request, to prepare your account.
Please note that your stamps are a record of the places you have visited and when, including places where you stopped on rides recorded with Strava.
3.18 Support and privacy requests
If you contact us, we process your email address, the content of your message and our reply to handle your request. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) or, for privacy requests, our legal obligation (Art. 6(1)(c) GDPR).
3.19 What we do not do
- We do not sell your personal data.
- We do not show third-party advertising in the app and do not use advertising IDs.
- We do not track your location in the background.
- We do not make decisions about you based solely on automated processing that have legal or similarly significant effects (Art. 22 GDPR).
- We do not process payment data (the app is free).
4. Legal bases at a glance
| Purpose | Legal basis (GDPR) |
|---|---|
| Account, routes, location features, stamp book, bike passport, community sharing, maps/search/routing/weather, service emails | Contract, Art. 6(1)(b) |
| Notifications about your rides, places and contributions (push and inbox) | Contract, Art. 6(1)(b) |
| Connected services (Strava, Garmin, Wahoo, Hammerhead, Ride with GPS), only if you connect them | Contract, Art. 6(1)(b) |
| Place reports and submissions, crash monitoring, security and rate limiting, Stay22 links, support | Legitimate interest, Art. 6(1)(f) |
| Anonymous usage statistics (PostHog without identifier, daily counts) | Legitimate interest, Art. 6(1)(f) |
| Product analytics (PostHog) | Consent, Art. 6(1)(a) |
| Marketing emails, news and offers notifications, website cookies and pixels (when introduced) | Consent, Art. 6(1)(a) (and ZEKom-2 for cookies and marketing emails) |
| Answering rights requests, accounting and legal obligations | Legal obligation, Art. 6(1)(c) |
Where we rely on legitimate interest, you have the right to object (see section 8).
5. Who receives your data
We use the following service providers. Processors act only on our instructions under a data processing agreement (Art. 28 GDPR).
| Recipient | Purpose | Data | Location / safeguard |
|---|---|---|---|
| Supabase, Inc. (processor) | Database, authentication, file storage, backend functions | All app data described above | EU (Ireland, eu-west-1); US parent company: see section 6 |
| Brevo (Sendinblue SAS, France) (processor) | Contact store and email delivery | Email, full name, user ID, mailing-list membership (only with your consent), email content | Company based in France (EU); safeguards for any transfer outside the EU/EEA: see section 6 |
| Expo (650 Industries, Inc.) (processor) | Push notification delivery, only if you allow notifications | Push token, notification title and text, notification ID | USA; see section 6 |
| PostHog (EU cloud) (processor) | Product analytics and anonymous usage statistics | With consent: user ID, app events, device/app info; anonymous statistics: app events and device/app info without any identifier; IP discarded | EU |
| Sentry (Functional Software, Inc.), EU data region (processor) | Crash and performance monitoring | User ID, IP address, device and error data | EU storage; US company: see section 6 |
| Vercel, Inc. (processor) | Hosting of our websites | IP address, technical request data | Global network incl. USA: see section 6 |
| Apple / Google (separate controllers) | Sign in with Apple / Google (if you choose it) | Sign-in data, email, name, profile picture link (Google) | Entities in the EU and the USA: see section 6 |
| Apple (Apple Push Notification service) / Google (Firebase Cloud Messaging) | Delivering push notifications to your phone, only if you allow them | Push token, notification title and text | Entities in the EU and the USA: see section 6 |
| MapTiler AG | Map tiles | IP address, map area | Company based in Switzerland; see section 6 |
| komoot GmbH (Photon) | Place search (via our server) | Search text, search area | Company based in Germany (EU) |
| OpenStreetMap Foundation (Nominatim) | Reverse geocoding | IP address, coordinates | Foundation based in the United Kingdom; see section 6 |
| GraphHopper GmbH | Route calculation (via our backend) | Route coordinates | Company based in Germany (EU) |
| Open-Meteo | Weather (via our backend) | Approximate coordinates | See section 6 |
| Own OSRM server (osrm.zyflow.eu) | Route calculation | IP address, route coordinates | Operated by us; hosted by Contabo GmbH (processor), Germany (EU) |
| Public OSRM demo server (project-osrm.org, based on OpenStreetMap) – fallback only | Route calculation if our own routing server is unavailable | IP address, route coordinates | Operated by a third party, not by us; see section 6 |
| DeepL SE | Translation of traffic-alert texts | No personal data | Germany (EU) |
| Stay22 (independent controller after you tap a link) | Accommodation affiliate links | Coordinates and name of the place; IP address once you open the link | See section 6 |
| Strava, Inc. (independent controller) | Importing your rides and routes, and stamps from your rides, only if you connect Strava | Strava athlete ID, access token; imported rides and routes; positions and times of past rides for stamps (not stored) | USA; see section 6 |
| Garmin Ltd. and affiliates (independent controller) | Sending routes, importing rides, only if you connect Garmin | Garmin user ID, access token; routes you send | Switzerland / USA; see section 6 |
| Wahoo Fitness L.L.C. (independent controller) | Sending routes, importing rides, only if you connect Wahoo | Wahoo user ID, access token; routes you send | USA; see section 6 |
| SRAM, LLC (Hammerhead) (independent controller) | Sending routes to Karoo, importing rides, only if you connect Hammerhead | Hammerhead user ID, access token; routes you send | USA; see section 6 |
| Ride with GPS, Inc. (independent controller) | Importing and sending routes and rides, only if you connect Ride with GPS | Ride with GPS user ID, access token; routes you send or import | USA; see section 6 |
Other users: see community sharing (3.4), place reports (3.5) and the stamp book (3.17).
Authorities: we disclose data only where we are legally required to, for example on a court order.
Business transfers: if HERKO d.o.o. or Zyflow is merged or sold, data may pass to the new owner, who must respect this policy; we will inform you in advance.
6. Transfers outside the EU/EEA
Your app data is stored in the EU (Ireland). Some recipients are based in, or may access data from, countries outside the EU/EEA, in particular the USA (for example Apple, Google, Vercel, Expo and the US parent companies of Supabase and Sentry). We transfer data only where an adequate level of protection is ensured. Depending on the provider, we rely on an adequacy decision of the European Commission (including the EU-US Data Privacy Framework for certified US companies) or on the European Commission's Standard Contractual Clauses (Art. 46 GDPR). Details on the safeguards used for a specific provider are available on request at legal@zyflow.eu.
If you connect Strava, Garmin, Wahoo, Hammerhead or Ride with GPS (3.15), the routes you send go to that service, which may process them in the USA or Switzerland under its own privacy policy and transfer safeguards.
7. How long we keep data
| Data | Retention |
|---|---|
| Account data (email, name, phone, user ID) | While your account exists; deleted immediately when you delete your account in the app |
| Profile photo | Until you remove it or delete your account |
| Saved and imported routes, saved places | Until you delete them or your account |
| Connected-service tokens and user IDs | Until you disconnect the service or delete your account |
| Rides and routes imported from a connected service | Until you delete them or your account; items imported from Strava are also deleted when you disconnect Strava |
| Strava route lines and map previews of rides and routes you have not imported | Up to 7 days; deleted sooner when you import the item or disconnect Strava |
| Record of routes sent to a device service | Until you delete the route or your account |
| Shared community routes, their photos and map images | The shared route and its photos are deleted when you remove the route or delete your account; its map images are removed from file storage on request within 30 days, and automatically when you delete your account (see section 9) |
| Bike passport and bike photos | Until you delete your account; a bike photo is deleted from file storage when you remove it or delete your account (see section 9) |
| Place reports and missing-place submissions | Until you delete your account; approved places remain in the places database without any link to you |
| Stamps and stamp visits (place, level, date and time, distance and GPS accuracy) | Until you delete your account |
| Stamps from your rides (place, level, date and time of the stop, distance) | Until you delete your account; they stay when you disconnect Strava |
| Progress of reading your rides for stamps (counts and a date; no rides or places) | Until you delete your account |
| Guest pass from the app's first steps (fingerprint of the code, Strava connection, stamps found, reading progress) | Until you sign in, when the connection and stamps move to your account; if you do not sign in, deleted after 14 days and our Strava access revoked. After the move, the fingerprint, reading counts and link to your account are kept for 30 days |
| Brevo contact (email, name, user ID) | While your account exists; deleted automatically when you delete your account (see section 9) |
| Your marketing email choice (on or off, when and where in the app) | While your account exists, also after you turn marketing emails off, so that we can show what you agreed to; deleted when you delete your account |
| Push token (with user ID and operating system build number) | Until you delete your account, or until Apple or Google tell us the token no longer works (for example after you uninstall the app) |
| Notification settings and notifications in your inbox | Until you delete your account |
| Email sending logs at Brevo | Only as long as needed to deliver emails and resolve delivery problems, in line with the provider's retention settings |
| Product analytics (PostHog) | 12 months; deleted automatically when you delete your account |
| Anonymous usage statistics (PostHog, no identifier) | 12 months |
| Daily counts of app starts and key moments (no identifier) | Kept as totals; they contain no personal data |
| Crash and performance reports (Sentry) | Up to 90 days |
| Search rate-limit data (IP address and counters) | Only as long as needed to prevent abuse; regularly deleted |
| Search cache (search text, no link to you) | 24 hours |
| Server and hosting logs (Supabase, Vercel) | Up to 30 days |
| Database backups | We currently keep no separate database backups |
| Support and privacy-request correspondence | As long as needed to handle your request and, afterwards, for a limited period to document it and to defend legal claims |
| Data on your device (session, last location, recent searches, date of the last notification offer, places reminded about today) | Until you uninstall the app or clear its data |
| Stamps waiting on your phone to be sent (with the GPS reading and answers) | Until they are sent, or until you uninstall the app or clear its data |
| Accounting records (if any) | As required by law (for example 10 years for invoices under ZDDV-1) |
8. Your rights
Under the GDPR you have the right to:
- access your personal data and receive a copy (Art. 15);
- rectification of inaccurate or incomplete data (Art. 16) – most data you can correct yourself in the app;
- erasure ("right to be forgotten", Art. 17);
- restriction of processing (Art. 18);
- data portability – receive data you provided in a structured, machine-readable format, or have it sent to another controller (Art. 20); routes can also be exported as GPX in the app;
- object to processing based on legitimate interest, for example crash monitoring or anonymous usage statistics (Art. 21) – for anonymous usage statistics also directly in Settings – and to object at any time to direct marketing;
- withdraw consent at any time, without affecting the lawfulness of processing before the withdrawal (Art. 7(3));
- lodge a complaint with a supervisory authority (section 10).
To exercise your rights, write to legal@zyflow.eu from the email address linked to your account. We may ask you to confirm your identity. We respond within 30 days (one month). In complex cases we may extend this by up to two further months; we will tell you within the first month. Exercising your rights is free of charge.
9. How to delete your account
- In the app: Profile tab → gear icon (Settings) at the top right → Delete account (below Log Out).
- On the web: https://www.zyflow.eu/legal-pages/delete-account.
- By email: write to legal@zyflow.eu from the email address linked to your account.
When you delete your account in the app, your account and profile data (name, email address, phone number, user ID and sign-in details) and the data stored with your account in our database (saved and imported routes, saved places, shared community routes, stamps (including stamps from your rides and the progress of reading your rides), bike passport, place reports and submissions, push tokens, notification settings, notifications and your marketing email choice) are deleted immediately. At the same time we automatically delete your files in our file storage (profile photo, bike photos, photos and map images of shared routes, and map previews of Strava rides), your contact at our email provider Brevo and your analytics records at PostHog. Error reports at Sentry linked to your user ID are deleted automatically within 90 days at the latest, or sooner on request: write to legal@zyflow.eu. We currently keep no separate database backups, so deleted data does not remain in backups. Approved places you suggested remain in the places database without any link to you. Data on your device is removed when you uninstall the app.
10. Complaints
If you believe that we process your data unlawfully, you can lodge a complaint with the supervisory authority in your EU country of residence or work, or with the Slovenian authority:
Informacijski pooblaščenec Republike Slovenije (Information Commissioner), Dunajska cesta 22, 1000 Ljubljana, Slovenia · gp.ip@ip-rs.si · +386 1 230 97 30 · www.ip-rs.si
We would appreciate the chance to resolve your concern first – please contact us at legal@zyflow.eu.
11. Children
Zyflow is intended for people aged 16 and over and is offered in the EU only. By creating an account you confirm that you are at least 16 years old. We do not knowingly process data of children under 16. If you believe a child under 16 has created an account, please contact legal@zyflow.eu and we will delete the account.
12. Website and cookies
Website and cookies (zyflow.eu, app.zyflow.eu, navigate.zyflow.eu)
Our websites are hosted by Vercel. When you visit them, Vercel processes your IP address and technical request data to deliver the site and keep it secure (legitimate interest, Art. 6(1)(f) GDPR).
We currently do not use analytics or marketing cookies on our websites. We plan to introduce Google Tag Manager, Google Analytics 4, PostHog (EU-hosted product analytics; no session recording on the marketing site) and the Meta (Facebook) Pixel. These tools will only load after you give consent in our cookie banner (Art. 6(1)(a) GDPR and ZEKom-2). You can change or withdraw your consent at any time via the "Cookie settings" link in the website footer. Before they are introduced, we will update this policy with details of Google, PostHog and Meta as recipients and of any transfers to the USA.
Details of all cookies are in our separate Cookie Policy: https://www.zyflow.eu/legal-pages/cookie-policy.
The mobile app does not use browser cookies; see section 3.14 for data stored on your device.
Without using cookies or running any code on your device, our hosting server counts page views anonymously: for each page request it sends only the page address, language and the referring website's domain to our analytics provider PostHog (EU cloud, acting as our processor), with no IP address, device information or identifier, to measure website reach (legitimate interest, Art. 6(1)(f) GDPR).
13. Security
We use appropriate technical and organisational measures, including encryption in transit, encryption at rest provided by our hosting provider, access controls and row-level security in our database, and restricted access to production data. If a personal data breach is likely to result in a high risk to you, we will inform you and the Information Commissioner as required by Articles 33 and 34 GDPR.
14. Changes to this policy
We may update this policy when our service or the law changes. We will publish the new version with a new version number and effective date. For material changes, we will inform you in the app and/or by email before the changes take effect.
15. Contact
HERKO d.o.o., Pševska cesta 10, 4000 Kranj, Slovenia · legal@zyflow.eu