VeloForthBack to site
PRIVACY POLICY

Your ride data,
handled clearly.

VeloForth is an offline-first cycling app. Most information stays in app-private storage on your Android device. This policy explains what the app accesses, why it is needed, and when an online service receives data.

LAST UPDATED23 July 2026APPLIES TOVeloForth for Android
THE SHORT VERSION

Local first.
Online when useful.

  • No VeloForth accountNo developer-run profile or cloud ride library.
  • Ride records stay localStored inside the app’s private device storage.
  • Google Play handles subscriptionsPayment details are not collected by VeloForth.
  • No sale or advertisingVeloForth does not sell data or use it for targeted ads.
AT A GLANCE

What happens to your data.

STAYS ON DEVICE

Rides, bikes & places

Ride tracks and statistics, bicycle details, service reminders, saved places, recent searches, route drafts, preferences, and offline-region records.

SENT WHEN ONLINE

Map and route requests

Mapbox receives information needed for maps, search, cycling routes, navigation, and offline downloads. Its mobile SDK also operates location telemetry.

WEATHER CHECK

Current coordinates

Open‑Meteo receives latitude and longitude when you request the pre-ride weather check. Battery status is read locally and is not included.

01

Who we are and what this covers

This is the privacy policy for VeloForth, Android packagecom.veloforth.app. “VeloForth”, “we”, and “us” in this policy refer to the developer of the VeloForth app. This policy covers information handled by the Android app. It does not replace the privacy terms of services you choose to use through Android’s sharing interface.

VeloForth does not provide user accounts, operate an app backend, or maintain a cloud copy of your ride library. No advertising SDK or developer-operated analytics service is included in the app.

02

Data the app accesses and stores

DataPurpose and storage
Precise and approximate location

Shows your position, records a ride, follows a route, calculates distance, speed and elevation, checks offline-map coverage, and supports maps, route planning, place search and weather. Recorded tracks and saved coordinates are stored locally.

Ride and fitness-like activity records

Route geometry, timestamps, distance, duration, speed, elevation, ascent and descent are stored locally so you can review your ride history and statistics. VeloForth does not treat this as medical or health-record data.

Search, route and place information

Search terms, recent destinations, route waypoints, saved places, route preferences and route drafts support planning and are retained locally unless you delete them.

Bicycle and maintenance information

Bike names, colours, tyre and suspension setup, chain care, service reminders and mileage are stored locally for garage and preparation features.

Device state

Battery percentage, charging state and network availability are read to prepare a ride and decide whether online features are available. VeloForth does not store these readings in your ride history or transmit the battery reading to its weather provider.

Files you choose

A GPX file is read only after you select it for import. GPX exports are written to a temporary app file and passed to Android’s share sheet only when you choose to export or share.

Subscription and free-ride status

VeloForth stores onboarding status, a monotonic count and identifiers for completed free rides, and a cached subscription entitlement, plan, trial timing, renewal status and one-way purchase-token digest. The full Google Play purchase token is handled transiently by Play Billing and is not written to VeloForth’s Dart data file or logs.

03

How location is used

Location is core to VeloForth. The app requests Android location permission when you use a feature that needs it. Precise location is required for reliable ride recording and turn-by-turn map positioning.

When a ride is active

After you start recording, VeloForth uses a foreground location service so the route can continue to be recorded while the app is minimised or the screen is locked. Android shows an ongoing ride notification. Recording ends when you stop or discard the ride; VeloForth does not request the separate AndroidACCESS_BACKGROUND_LOCATION permission.

Current location or route coordinates may be sent to Mapbox when you use online maps, search, routing, navigation or downloads, and to Open‑Meteo when you request ride-preparation weather. Location is not used by VeloForth for advertising.

04

Online services and recipients

MAPS · SEARCH · ROUTING

Mapbox

Mapbox’s Maps and Navigation SDKs and APIs may receive your IP address, device and network details, SDK/API request details, precise location, search text and proximity, selected destinations, route waypoints, and offline-download areas. This provides maps, search results, routes, navigation and offline content. Mapbox also describes mobile SDK location telemetry used to improve its products. VeloForth does not receive that telemetry on a developer server.

Mapbox privacy policy ↗Mapbox telemetry information ↗
RIDE-PREPARATION WEATHER

Open‑Meteo

When online weather is requested, VeloForth sends latitude and longitude to Open‑Meteo and receives temperature, wind, rain probability and sunset data. As with any internet request, Open‑Meteo also receives an IP address. Open‑Meteo states that API server logs may contain coordinates and are deleted after 90 days.

Open‑Meteo terms and privacy ↗
ANDROID PLATFORM

System services

Android supplies location, battery and connectivity state, displays the foreground-service notification, lets you choose GPX files, and shows the share sheet. Android or Google may include VeloForth’s app-private files in device backup according to your device and Google backup settings. VeloForth does not operate or control that system backup.

SUBSCRIPTIONS · PURCHASE RESTORE

Google Play

Google Play Billing supplies available plans, trial eligibility, localised prices and owned-purchase status, and displays the purchase and subscription-management screens. Google processes payment details under its own privacy policy; VeloForth does not receive card or bank details. The app receives purchase state, renewal and acknowledgement information needed to unlock Premium and restore access.

Google privacy policy ↗Google Play terms ↗
05

Sharing, sale and advertising

VeloForth does not sell personal or sensitive user data. It does not include advertising, use an advertising identifier, or share ride data with advertisers or data brokers. Data is transmitted to Mapbox, Open‑Meteo and Google Play only for the app functions described above. Those providers process information under their own policies.

If you export or share a route or ride as GPX, Android sends the file to the app, service or person you select. That transfer is initiated and controlled by you, and the recipient’s privacy practices apply after the file leaves VeloForth.

06

Retention and deletion

Local information remains on your device until you delete an item in the app, clear VeloForth’s storage in Android settings, or uninstall the app. Temporary GPX export files are stored in the app’s temporary directory and may remain until Android or the app clears that cache.

Deleting a saved ride does not delete its free-ride usage event or restore a free ride credit. Because there is no VeloForth account or backend, clearing all app data can reset device-local free usage. An active Google Play subscription can be restored from the Play account even when local app data has been removed.

Because VeloForth has no account or developer backend, there is no server-side VeloForth account data to request for deletion. Android backups and information held by Mapbox or Open‑Meteo are governed by those providers and your platform settings.

07

How data is protected

VeloForth stores its local record in Android’s app-private documents area, protected by the Android application sandbox. Protection at rest also depends on your device’s security, encryption and backup settings. Online requests to Mapbox and Open‑Meteo use HTTPS. No security measure can guarantee absolute protection, so keep your device updated and protected with a screen lock.

08

Your choices and controls

  • Location: change VeloForth’s location permission at any time in Android settings. Recording, live positioning, local weather and some routing features will not work without it.
  • Notifications: control ride and subscription-reminder notifications in Android settings. VeloForth asks about the trial reminder only after a monthly trial is confirmed. Android may still show notices required for an active foreground service.
  • Subscriptions: restore a Play purchase in VeloForth or open Google Play subscription management to review renewal, payment, cancellation and expiry information. VeloForth does not provide a local cancellation control.
  • Local data: delete individual rides, places, routes, bikes or offline regions in the app where available, or clear all app storage through Android settings.
  • GPX sharing: do not use export or share if you do not want a route file transferred to another app or person.
  • Online services: use downloaded maps and routes when offline; online search, fresh route requests, map content and weather require the third-party services described above.
09

Changes to this policy

We may update this policy when VeloForth’s features, data practices, providers or legal obligations change. The “Last updated” date at the top identifies the current version. Material changes should be reflected in the app and its Google Play Data safety information before the changed practice is used.

10

Privacy questions

For a privacy inquiry about VeloForth, use the public developer contact method shown on VeloForth’s Google Play store listing and include “Privacy” in the subject or first line. Please do not send a ride track or other sensitive location information unless it is necessary to resolve your request.