Privacy Policy
Last updated: October 21, 2026
This Privacy Policy explains how Velora ("the app", "we", "us"), a mobile application by kodmap, handles information when you use it on iOS, Android, Apple Watch and Wear OS. Velora has no account and no sign-in, and there is no Velora server that receives your activities: your activities, your routes and the videos and posters you make are stored on your device and rendered on your device.
The short version. We do not have a database with your name in it, and we never receive your routes, your GPS tracks or your health data. We do not ask for your name, email or address, we show no ads, and we sell nothing. What does leave your device is this: map, elevation and (in the satellite style) imagery tile requests, which carry no identifier but reveal roughly where a route goes (section 6); usage analytics and crash reports sent to Google Firebase, tied to a random install identifier and never to your name (section 9); a push-notification token (section 10); ad-measurement events from the Meta SDK and, on iOS only if you allow tracking, your advertising identifier (sections 9 and 9a); and your subscription status, handled by RevenueCat under a random, anonymous identifier (section 11). Analytics events describe what you do in the app — screens opened, a video rendered, a paywall shown — never what your body or your route did: no coordinates, place names, distances, times, paces, heart rate or other health values. The one other thing that leaves your device is a route link that you choose to send someone — section 7 explains what one contains.
1. What stays on your device
Everything you make with Velora is stored locally and is never uploaded to us:
- Activities you record — on your phone or on your watch: the GPS trace, timestamps, distance, pace and speed, elevation, laps and splits, and heart rate, cadence or speed when a watch or sensor provides them.
- Activities you import — the contents of any GPX, TCX or FIT file, or of a whole export archive (ZIP) from another service such as Strava or Garmin, parsed entirely on your device. Velora does not connect to those services; you hand it the file.
- Workouts you import from Apple Health or Health Connect — see sections 3 and 4.
- Photos you attach to an activity or choose as a template background.
- The videos and posters you generate, together with the settings you generated them with, so you can render them again later.
- Place names worked out for a route (section 6), stored next to the activity and deleted with it.
- Your settings — units, themes, template choices, privacy zones, and an optional body weight used to estimate energy burned.
On iOS this lives in the app's own container (Application Support, plus an app group shared only with Velora's own widgets) and in the app's preferences; on Android in the app's private internal storage and its DataStore. Neither is readable by other apps. Velora has no cloud sync, no online backup and no web version — there is nowhere for your activities to sync to.
Your device's own backup is a separate matter: on iOS, data that is not a regenerable cache is included in whatever backup you have configured with Apple (iCloud or a computer), under Apple's terms and your settings, not ours. On Android and Wear OS, Velora sets allowBackup="false", so its data is excluded from Google's automatic backup.
2. Location
Velora uses your device's location to record the route of an activity, and only while an activity is being recorded. You are asked for permission either on the location step of the welcome screens, which you can skip, or at the moment you first tap Start.
- iPhone and Apple Watch. Velora asks for "While Using" and then "Always" location. With "Always", recording continues while your phone is locked or the app is in the background, and on the watch while your wrist is down. That is the whole reason it is requested: without it iOS stops delivering location to a backgrounded app and a training session is cut short. Velora switches background location updates on only for the duration of a recording.
- Android and Wear OS. Velora does not request background location (
ACCESS_BACKGROUND_LOCATION). While you record, a foreground service with a visible, ongoing notification keeps the recording running when the screen is off; when the recording stops, so does location.
Your location is not transmitted to us. It is written to the activity on your device, and it is never included in analytics events or crash reports. What the map-tile requests in section 6 reveal about it is explained there. Note that Google Analytics, like any internet service, sees the IP address of a request and derives an approximate region (such as country or city) from it (section 9).
3. Apple Health (iPhone and Apple Watch)
Reading. If you choose to import from Apple Health, Velora asks for permission to read the following, and reads nothing else: workouts, workout routes, heart rate, step count (used as running cadence — Health has no cadence type of its own), distance (walking/running, cycling, swimming, paddle sports and rowing), and active energy burned.
If you also turn on background delivery, iOS wakes Velora when a new workout is written so that a run recorded with another app is already in your archive when you next open the app.
Writing. If you allow it — on the last welcome screen or later in Profile — Velora writes the activities you record in Velora to Apple Health, so they count towards your rings and other apps you use can see them: the workout itself, its route, its distance, heart rate if it was measured, and active energy. Velora never writes back anything it read from Health or imported from a file.
On Apple Watch. When you record on the watch, it asks for permission to read heart rate, steps, active energy, distance and, for swims, stroke count, underwater depth and water temperature, so that it can show them live; and to save the workout and its route to Apple Health. The iPhone does not write that workout a second time.
Health data is read into the same local storage as everything else in section 1. Health values (heart rate, steps, energy, distance, times) are never transmitted anywhere, and are never used for advertising or analytics. You can withdraw any of these permissions at any time in the iOS Health app, under Sharing → Apps → Velora.
4. Health Connect (Android)
On Android, Velora can exchange data with Health Connect, only with your permission and only for the purposes below. No health permission is requested when the app starts; you are asked only when you use one of the features described here.
What Velora reads, and why. When you tap the Health Connect import button, Velora asks to read: exercise sessions, exercise routes, heart rate, steps, distance, active calories burned and elevation gained, and access to records older than 30 days (without it, Health Connect limits every read to the last 30 days). Distance, active calories and elevation are read only for sessions that have no route (a treadmill run, an indoor row), because a session with a route is measured from the route itself. Heart rate and steps are used only for that activity's heart-rate and cadence figures. All of it serves one purpose: adding the workouts you choose to Velora's archive on your device, and drawing maps, charts, videos and posters from them.
Reading in the background. If you turn on Health Connect sync in Profile (off by default), Velora also reads new workouts that other apps write to Health Connect while Velora is closed, roughly once an hour, so that a run recorded with your watch is already in your archive when you open the app. For this it asks Health Connect for a separate background-access permission — only when you turn the switch on. The data read is the same as above; the permission changes only when it is read. Turning the switch off stops background reading.
What Velora writes, and why. If you turn on Write to Health Connect (on the last welcome screen or in Profile), Velora writes to Health Connect the activities you record in Velora — on your phone or on your Wear OS watch — so that your other health apps can see them: the exercise session (sport, start, end, laps), its route, its distance, heart rate if it was measured during the recording, and total calories burned if you have entered your weight. Velora never writes back anything it read from Health Connect or imported from a file.
Where it goes. Velora has no account and no server. Data read from Health Connect is stored only in Velora's private storage on your device, until you delete it or uninstall the app. Health values — heart rate, steps, distance, calories, elevation, times — never leave your device. The one thing derived from a route that does leave it is a request for map tiles along the route, used to name the place the activity was in (section 6): it contains no route points, no times, no health values and no identifier, but which tiles are requested shows the approximate course of the route.
Limited Use. Velora's use of information received from Health Connect complies with Google Play's Health Connect permissions policy, including its Limited Use requirements. Data from Health Connect is used only to provide the features described above, which you can see in the app. It is not used for advertising, marketing, analytics or profiling; it is not sold; it is not used to determine credit-worthiness or for lending; it is not read by any person at kodmap; and it is not transferred to anyone, except for the place-name tile requests described in section 6.
You can withdraw any Health Connect permission at any time in Health Connect's own settings (on Android 14 and later, under the system Settings), and turn off sync or writing in Velora's Profile. Workouts Velora wrote stay in Health Connect until you delete them there.
Google Fit is not used.
5. Watch apps (Apple Watch and Wear OS)
Velora's watch apps can record an activity on their own, with the phone left at home.
- Apple Watch records with the watch's own location and workout sensors (heart rate, and motion for cadence), shows the figures live, and saves the workout and its route to Apple Health (section 3). The recording is then delivered to your iPhone over Apple's WatchConnectivity — directly between your own devices — and appears in Velora's archive there.
- Wear OS records with the watch's location and Google's Health Services (heart rate, steps, distance), which is why it asks for location, body-sensor and physical-activity permissions; Health Connect does not run on Wear OS. The recording is delivered to your Android phone over Google Play services' Wearable Data Layer, which carries it between your paired devices; it never reaches a server of ours. On the phone, it is written to Health Connect only if "Write to Health Connect" is on (section 4).
6. Map, place-name and imagery requests (third-party recipients)
Velora draws maps from tiles fetched from the three services below. Each request goes directly from your device to that service over HTTPS; we do not operate, log or receive any of them.
What is sent, for all three: only the coordinates of the map tiles needed (zoom/x/y) for the area of a route — which reveals the approximate location of that route. No raw GPS points, timestamps, health data, account, name or identifier of yours is sent. Like every request on the internet, each one also reaches the host with your device's IP address and the platform's standard request headers (on Android, for example, the default User-Agent names the Android version and the device model). Each service processes these requests only to return map images.
- Google Maps Platform (Map Tiles API) —
tile.googleapis.com(Android). Google LLC. Used only when you choose the Satellite theme for a render; the other themes make no request to Google. Besides the tile coordinates, the request carries Velora's own API key, a session token and the language and region the imagery session is opened with. Governed by Google's privacy policy. (On iOS, the Satellite theme uses Apple's MapKit, which fetches imagery for the area of the route from Apple, under Apple's privacy policy.) - OpenFreeMap —
tiles.openfreemap.org(iOS and Android). An open map-tile service used with no API key and no account. It supplies the vector tiles for the dark and light map themes (the basemap, labels, fonts and 3D building shapes), and the place names below. Map data is © OpenStreetMap contributors, © OpenFreeMap, © OpenMapTiles. - AWS elevation tiles —
s3.amazonaws.com/elevation-tiles-prod(iOS and Android). Public terrain elevation rasters hosted on Amazon Web Services, used to draw hillshade and relief under a route.
Place names. To give an activity a name like "Kadıköy → Moda", Velora reads place names out of OpenFreeMap vector tiles. It requests the zoom-14 tiles the route passes through and the tiles around them — up to 80 tiles per activity — plus one request for the tile index. A zoom-14 tile is roughly 1.5–2.5 km across, so the set of tiles requested reveals the corridor of the route at about 2 km resolution, not just the general area. This happens automatically, without you tapping anything: on Android when a recording finishes, when an import (including Health Connect sync) adds an activity, when you open an older activity that has no name yet, and when you export a video; on iOS when an activity is first drawn in the studio or rendered. It happens once per activity: the names found are stored on your device and no further request is made for that activity. Please note: privacy zones and the setting that hides place names stop a name from being shown, and zones remove the covered part of a route from anything you export or share — but today they do not stop these tile requests, which are computed from the whole route.
Caching on your device. Satellite imagery from Google is cached on your device for at most 30 days (as Google's terms require) and then deleted, or earlier with the activity. Map images drawn from OpenFreeMap and elevation tiles are kept with the activity until you delete it, and on Android the map engine's own tile cache is limited to 300 MB and overwritten as it fills. So an area you have already rendered generally needs no further requests. Retention on each service's side is governed by that service's own policy; we have no account with them and receive nothing from them about you.
7. Route links you choose to share
Velora can turn a route into a link that looks like this:
https://velora.kodmap.co/applinks/r/#<payload>
Two things about it matter, and both are deliberate:
- The route is in the part after the
#. That part of a URL is a fragment, and by the design of the web a fragment is never sent to the server. So when someone opens your route link — in the app, or on this website — the route is decoded and drawn in their browser. It does not reach our hosting, it is not logged, it is not stored, and we never see it. There is no short-link service and no upload step. - Privacy zones are applied before the link is made, not after. If you have drawn a privacy zone around your home or workplace, the parts of the route inside it are removed before anything is encoded, and only the longest remaining stretch is included. The full route stays visible to you inside the app.
A route link carries the shape of the route, the name of the place it is in (from map data, and omitted entirely if you have place names switched off), and its total climb. It deliberately carries no times, dates, speeds, heart rate, your name, or any identifier.
It does, however, carry real coordinates. Anyone who has the link can see where that route goes — that is what sharing a route means. Send it to people you mean to send it to.
8. Photos, camera, microphone, music, sensors and notifications
- Photos — when you pick a photo as a template background, or attach one to an activity, Velora receives only the images you chose (on iOS after asking for photo access; on Android through the system photo picker, which needs no permission). Velora never browses or uploads your library. Saving a finished video or poster asks, on iOS, for add-only permission; on Android it needs none.
- Camera (iOS) — used only when you take a photo during a recording, to attach it to that point of the route.
- Music (iOS) — used to show the title and artist of whatever is already playing, with play/pause controls, on the recording screen. Video soundtracks come from tracks bundled with Velora; if a song from your own library is used as a soundtrack, it is read and mixed into the video on your device. Velora does not copy or upload your music library. On Android, soundtracks are only the bundled tracks and no music permission is requested.
- Bluetooth (iOS) — used only to connect to an external cycling cadence or speed sensor, when you go looking for one.
- Motion — used on iPhone and Apple Watch to show your cadence while recording; on Wear OS the physical-activity permission serves the same purpose.
- Microphone — Velora does not request or use microphone access on any platform.
- Notifications — Velora asks to show notifications (on the notifications step of the welcome screens, which you can decline). On Android and Wear OS, a recording in progress, or a video being exported, appears as an ongoing notification; on iOS a recording in progress can appear as a Live Activity. Those are generated on your device. Velora can also receive push notifications from us — see section 10.
- Android requests no camera, music or Bluetooth permissions.
9. Analytics, crash reporting and app configuration (Google Firebase)
Velora's phone apps use Google Firebase. The watch apps and widgets do not. None of it shows you ads; how we measure our own ads is described at the end of this section and in section 9a.
- Firebase Analytics — which screens are opened and which features are used, so we know what to improve. The events are: screen views; the steps of the welcome screens; your answer to the notification prompt; the steps of the Velora Pro screen (shown, plan selected, purchase tapped, result, restore, dismissed) and a purchase, which carries the product, price, currency and store transaction ID; that a video or poster was rendered, with its format (video or image) and the template's ID; that a recording was saved, with its sport (for example "run" or "ride"); that activities were imported, with where from (file, Apple Health or Health Connect, watch) and how many; and taps on the rating and feedback sheets (including the 1–5 rating you pick — the text of any feedback goes only into the email you choose to send). A few summary properties are kept with the install: whether onboarding is finished, whether you have Velora Pro, how many videos or posters you have rendered, how often and why the Pro screen was shown, and the app language. Events never contain coordinates, routes, place names, distances, durations, paces, heart rate or any other health value — the app's analytics vocabulary has no field that could carry them. Firebase also records standard information about the install: device model, OS version, app version, language, and an approximate region derived from the IP address.
- Firebase Crashlytics — when the app crashes, the stack trace, device model, OS version, app version, and state such as free memory and disk space, so the bug can be found and fixed. Crash reporting is switched off in development builds.
- Firebase Remote Config — the app downloads settings from us, for example whether an update is required. The request carries the Firebase installation ID, app version and device language.
Identifiers. Firebase assigns your install a random app-instance identifier. Analytics and crash reports are additionally tagged with the anonymous RevenueCat user ID described in section 11, so analytics, crash reports and your subscription record share one random ID; the app-instance identifier is also passed to RevenueCat so that a purchase can be matched to the analytics of the same install. That ID identifies an installation of the app, not you: it is not linked to your name, email or phone number, and reinstalling the app produces a new one. On Android, the device's Google advertising ID is passed to the Meta SDK only while Share usage data is on, and the Firebase SDK can also read it; Velora shows no ads, and you can delete or reset that ID in your Android settings. On iOS, the advertising identifier (IDFA) is available only if you allow tracking — see section 9a.
Analytics data is processed by Google in its Google Analytics service and is also exported to our own Google BigQuery storage, located in the EU, which we use to measure the app and to choose which notifications are relevant (section 10).
Install source and ad measurement. When you first open the app, Velora records how it was installed — for example an ad campaign, an App Store or Google Play search, or a web link — using the Google Play Install Referrer on Android and Apple's AdServices framework on iOS. Velora also includes the Meta SDK (Meta Platforms, App Events) to measure the performance of our own ads on Facebook and Instagram: it reports app installs and a few in-app milestones (finishing the welcome screens, first use of a core feature), linked to a pseudonymous device identifier. It never receives routes, locations or health data, and Velora shows no ads. On iOS, the advertising identifier (IDFA) is used only if you allow tracking (section 9a).
9a. Tracking & advertising identifiers (App Tracking Transparency)
On iOS, Velora asks for your permission once, with Apple's App Tracking Transparency (ATT) prompt, near the end of the welcome screens (or, if you finished them before this was introduced, once after the app opens). What happens next depends on your answer:
- If you tap “Allow” — your device's advertising identifier (IDFA) is shared with Meta (Facebook) through the Meta SDK and used to measure and attribute our ads on Facebook and Instagram, that is, to learn which ad led to an install or a purchase. RevenueCat also records your device identifiers (the IDFA and the IDFV, Apple's identifier for vendors) with your subscription record, so that a purchase can be attributed to the ad campaign that brought you to the app. Your routes, locations and health data are never shared with Meta, Velora shows no ads, and we do not sell these identifiers.
- If you tap “Ask App Not to Track” — nothing changes. The IDFA is not accessed, and our ads are measured only with aggregated, privacy-preserving methods: Apple's SKAdNetwork, Meta's Aggregated Event Measurement and Google's on-device conversion measurement.
If you have turned off Share usage data in the app's Settings, the prompt is not shown at all.
Changing your mind. On iOS, open Settings > Privacy & Security > Tracking and switch Velora off (or turn off “Allow Apps to Request to Track” for every app); sharing stops from that moment. Android has no tracking prompt: on Android, the device's Google advertising ID is passed to the Meta SDK, to measure our own ads, only while you have left Share usage data on (turning it off stops this on that device); the Firebase SDK may also read it, and you can delete or reset it in Settings > Google > Ads (on some devices Settings > Privacy > Ads).
10. Push notifications
Velora uses Firebase Cloud Messaging (FCM), which gives your install a push token. The app subscribes that token to a general topic and to a topic for your app language, so we can send announcements in your language. The token is also stored with your analytics properties and your RevenueCat record, so we can send a notification to groups of users defined by the attributes in sections 9 and 11 (for example, users who have not yet rendered a video). Notifications are shown only if you allow them; you can turn them off at any time in your system settings.
10a. Campaign & notification measurement
When you open Velora from a push notification, from one of the reminder notifications described in section 10b, or from a link, we record which campaign it belonged to — a campaign identifier, its type and its source (for example a push notification, a reminder or a link) — in Google Analytics for Firebase and as an attribute of your subscription record at RevenueCat. For the next 72 hours, that campaign identifier is attached to a few in-app events (the Velora Pro screen being shown, a purchase being started or completed, and reaching a key milestone in the app), so we can tell whether a campaign was useful, including whether it led to a purchase. The campaign identifier describes the message or link, not you, and it never contains anything you created in the app.
10b. Reminder notifications scheduled on your device
Velora can schedule a few reminder notifications locally on your device — they are not sent from a server: for example a reminder if you have not opened the app for a few days, a reminder to finish setting up the app if you left the welcome screens halfway, a note shortly before a free trial ends, or a reminder a day after you looked at Velora Pro without subscribing. They appear only if you have allowed notifications; the inactivity reminders are re-planned every time you open the app, so they do not reach someone who is using it; and they never contain prices or discount offers. Opening one is measured as described in section 10a. You can turn them off at any time with Suggestions & reminders in the app's Settings, or by turning off notifications for Velora in your system settings.
11. Purchases and subscriptions
Velora Pro is an auto-renewing subscription. Purchases are processed by the Apple App Store and Google Play, and subscription status is managed with RevenueCat.
We never see or store your payment card details; billing is handled entirely by the stores. RevenueCat identifies your installation by a random, anonymous identifier that it generates, and receives your store receipts in order to confirm your subscription, basic device and app information (OS, app version, country, and the IP address of the request), and these attributes from the app: whether you have Velora Pro, whether onboarding is finished, whether you have rendered your first video or poster and how many, how many times and for what reason the Pro screen was shown, the Firebase app-instance identifier, your push token (section 10), the last notification or link campaign you opened (section 10a), and — on iOS, only if you allow tracking — your device identifiers (IDFA and IDFV, section 9a). We use these to know whether to unlock Velora Pro and to choose which in-app messages and notifications are relevant to you. Velora never sends RevenueCat your name, your email, your activities or any health data, because it does not have an identity to send. On iOS, an Apple-provided attribution token (Apple's AdServices framework) is passed to RevenueCat so that a purchase can be attributed to an Apple Search Ads campaign; it identifies a campaign, not you, and involves no tracking across other companies' apps.
12. What Velora does not do
To be explicit, because several of these are things comparable apps do:
- No routes, GPS tracks or health data in analytics. Analytics and crash reports (section 9) say what happened in the app, never where you went or what your body did.
- No ads, and tracking only if you allow it. No ads are shown in Velora. The only advertising-related component is the Meta SDK, used solely to measure our own ads (section 9). On iOS your advertising identifier is shared only if you tap “Allow” in the App Tracking Transparency prompt, and never together with routes, locations or health data (section 9a). On Android, see section 9 about the advertising ID.
- No use of health data beyond the features you see — never for advertising, analytics or profiling, and never sold.
- No accounts, no profiles, no feed, no followers, no leaderboard.
- No sale of personal information, in any sense including those used in the CCPA/CPRA. The only disclosure for advertising purposes is the iOS advertising identifier, with your permission (section 9a).
13. Legal basis and your choices (GDPR / UK GDPR)
If you are in the EU, the UK or Switzerland: the processing Velora performs on your device to deliver the app you asked for, including the map and place-name requests in section 6, the subscription check in section 11 and the update check in section 9, is necessary for the performance of the contract between us (Art. 6(1)(b)). Analytics and crash reporting (section 9) and push notifications (section 10) are based on our legitimate interest in understanding how the app is used, why it crashes, and telling you about the app, so we can fix and improve it (Art. 6(1)(f)); campaign measurement (section 10a) and reminder notifications (section 10b) rest on the same legitimate interest. Sharing your advertising identifier on iOS (section 9a) happens only with your consent (Art. 6(1)(a)), given in the App Tracking Transparency prompt, which you can withdraw at any time. Health data and precise location are special or sensitive categories, and Velora processes them only with your explicit consent (Art. 9(2)(a)), given through the system permission prompts and the in-app switches described above, which you may withdraw at any time in your device settings or in Velora's Profile. Health data and location are never used for analytics.
Your choices:
- Share usage data — turning off Share usage data in the app's Settings stops Google Analytics, Firebase Crashlytics and the Meta SDK together on that device. The choice is re-applied every time the app starts.
- Tracking — on iOS, allow or decline tracking in the App Tracking Transparency prompt, and change it at any time in Settings > Privacy & Security > Tracking. On Android, delete or reset your advertising ID in Settings > Google > Ads.
- Notifications — turn off reminder notifications with Suggestions & reminders in the app's Settings, or turn off all notifications for Velora in your system settings. The Suggestions & reminders switch does not affect recording and export notifications.
- Object, or ask for deletion, by contacting us (section 17). Because we do not know who you are, tell us something that lets us find your install — the store order number of a Velora Pro purchase is the most reliable — and we will delete the matching analytics, crash and subscription records and stop processing them. See Data Deletion.
- Uninstall Velora. This stops all collection; a new install gets new random identifiers.
Your activities, routes and health data are on your device, so they are already in your hands, and deleting the app deletes them. You may also complain to your local data protection authority.
California residents: we do not sell personal information. If you allow tracking on iOS, your advertising identifier is disclosed to Meta to measure and attribute our own ads; you can stop this at any time in Settings > Privacy & Security > Tracking, which also serves as your opt-out of “sharing” as that term is used in the CCPA/CPRA. The contact address in section 17 is your request channel.
14. Retention
Activities, routes, health data and everything else in section 1 stay on your device until you delete them or uninstall the app. Analytics data is kept by Google Analytics for the data-retention period set in our project (Google's settings allow two to fourteen months for event-level data) and in our BigQuery export for as long as we need it to measure the app; crash reports are kept by Crashlytics for 90 days; both are then deleted automatically. A push token stops working when you uninstall the app or it is refreshed. Your subscription record is kept by RevenueCat and the app stores for as long as needed to manage the subscription and to meet legal and accounting obligations.
15. Children
Velora is not directed at children under 13, and we do not knowingly collect information from them.
16. Changes to this policy
If this policy changes materially — in particular if we ever begin collecting a category of data we do not collect today, or add a processor or a network request — we will update this page and change the date above.
17. Contact
Questions or requests: kodmapdev@gmail.com, or use our Contact page. See also Data Deletion.