Privacy policy

01

Activity data stays on your device

Recorded routes, activity measurements, markers, photos and statistics are stored locally. Waykeep does not require an account and has no cloud sync, advertising, analytics or Google Play Services dependency.

02

Maps use a network connection

The app requests map tiles to display the basemap. Those requests go to the map provider, which receives the requested tile and the network information needed to deliver it, such as your IP address. Viewed tiles are cached. Enable offline mode to stop tile requests; recording itself does not need internet access.

03

Export and sharing are your choice

You can export activities as GPX, KML or KMZ, including photos in KMZ, or share a rendered statistics image. Automatic export runs only if you configure it. The destination or app you choose then handles that copy under its own privacy practices.

04

Diagnostics are local, too

Waykeep keeps a local recording diagnostics journal to help investigate recording issues. Sharing a diagnostics journal is an explicit action. Review it before sharing, especially if you plan to post it publicly.

05

Retention and deletion

Activity data stays on the device until you delete the recorded activity or uninstall the app. Exports and copies you have shared are separate: deleting an activity in Waykeep does not remove those copies.

This website is separate from the app

The statements above describe the Android app. This website sets no cookies, runs no analytics and loads no third-party scripts; its fonts are served from this site. Links to the repository and releases go to GitHub, which applies its own logging when you follow them. The site is hosted on Lovable.

Questions and source material

This page explains the behavior documented by Waykeep and its upstream project, OpenTracks. The repository’s inherited policy still uses the OpenTracks name. For questions, open an issue without including private activity data.