nakvali.

YOUR DATA

Privacy, on the trail.

Your original ride recordings stay on your phone. You choose when to export or share them.

Last updated: 25 September 2026

Who runs Nakvali

Nakvali is an independent cycling recorder developed by Stas, known as whekin. This notice covers the Android app and this website.

For privacy questions or account-data requests, email whekins@gmail.com. Do not send GPS recordings or credentials unless needed for a support request you choose to make.

Recordings on your phone

When you start a recording, Nakvali uses location, timestamps and available motion and pressure sensors to record and process your ride. Recording can continue in the background until you stop it. Tracks, ride statistics, sensor recordings and diagnostic files are stored locally. Recording and local review do not require an account.

Raw GPS, motion and pressure recordings are not automatically uploaded to the Nakvali server. They remain on your device until you delete them or remove the app. Exports and backups you create may remain in the folders or services you choose. Android backup behavior also depends on your device settings.

Optional account and maps

If you sign in with Google, Firebase Authentication processes the sign-in. The Nakvali backend receives your verified account ID, email address, display name, avatar URL and email-verification status to maintain your profile. Signing out ends the app session; it does not itself delete the server-side account.

Online map requests go to OpenFreeMap and the resources referenced by its map style. Those services receive normal network information, including your IP address and the map tiles requested. Previously downloaded map data may be cached on your device.

See Firebase privacy information and OpenFreeMap’s privacy policy for how those providers handle their services.

Exports and connected services

A FIT, GPX or TCX export can contain precise locations, timestamps and altitude. Android’s save or share flow sends the file to the destination you select. Local diagnostic and backup exports may include raw sensor data; share them only with a recipient you intend.

If you connect BIKEYARD in a compatible Nakvali build, the app asks for profile access, permission to upload rides and permission to read your rides back, including private ones. Nakvali reads only your profile totals and BIKEYARD’s results for rides Nakvali uploaded: the ride page link, matched trails and honours. An earlier connection keeps uploading without read access until you allow it. Connection tokens, your connected profile and those results are encrypted on your phone outside the ride backup. You choose individual uploads or opt into automatic uploads of newly saved rides, with your selected visibility. Processed tracks and ride metadata go directly to BIKEYARD; original sensor files stay on the phone.

Jump sharing has a separate switch and starts off. When you enable it for new private rides, or choose to send it for one private ride, Nakvali sends airtime event times — air of 0.25 s or more marked as jumps, which BIKEYARD counts, and shorter air as uncounted candidates — with measured sensor coverage and sample rate, and the phone position you select. Jumps are a phone-sensor estimate, not a verified measurement. BIKEYARD associates those times with its copy of your ride. The app does not send raw motion samples, GPS coordinates in the metrics document, or phone G peaks. Turning off automatic airtime sharing stops future and queued automatic submissions; metrics already accepted by BIKEYARD remain with that ride until you manage the ride there.

Disconnecting removes local connection data and stops queued uploads. If the app cannot reach BIKEYARD to revoke access, it tells you to finish revocation in BIKEYARD’s connected apps. Already uploaded rides remain in BIKEYARD until you manage them there. Older development builds may have used other connected services; removing an integration does not itself delete data previously sent to those services.

This website and operational data

This website contains no analytics scripts, advertising trackers or tracking cookies. Its fonts and artwork are served from the same site. Hosting and proxy services process connection information such as IP addresses, requested paths, response status and timestamps to deliver and protect the service. The Nakvali API may retain operational logs for troubleshooting.

GitHub hosts the source and release downloads. Following a GitHub link or downloading a release is subject to GitHub’s privacy statement. Nakvali does not sell personal data.

Retention and your choices

You control local recordings through the app’s delete, export and backup actions. Server account information is retained while your account is in use or until you request deletion. Operational records are retained only as needed for service operation, troubleshooting and security; backup copies may take longer to expire. Data you publish to another service is managed separately by that service.

You can request access, correction or deletion of the account information held by Nakvali using the private contact above. You can also ask about retention and processing, object to processing where applicable, and complain to your local data-protection authority. We may need to verify account ownership before acting. Do not post personal data in public GitHub issues.

Changes

This notice describes an evolving early-stage app. Material changes to data handling will be reflected here with a new update date before the new functionality is offered.