GREENLANE NAVIGATOR — PRIVACY POLICY Last updated: 21 October 2026 Who is responsible GreenLane Navigator is operated by Anton MacMinn. For privacy questions or requests, contact Anton.MacMinn@hotmail.com. This policy describes the current Android app. GreenLane Navigator helps you plan and follow routes. You do not need an account for the ordinary app. It contains no advertising, advertising identifiers, analytics SDK or automatic crash-reporting service. We do not sell your personal information or use your location for advertising. Location and navigation With Android location permission, the app uses your position, location accuracy, speed and direction to show your location, centre the map, display speed, follow your trip and update waypoint progress. It may request location when the map opens, as well as when you select Locate or Navigate. You can refuse or revoke permission in Android settings; location-based features will then be unavailable, but you can still use available planning and saved-route functions. During active navigation, switching apps or locking the screen allows navigation to continue for up to 30 seconds through an Android location foreground service. The service posts a navigation notification and can keep the CPU awake for location processing; it does not keep the hidden screen on. If Android reports ringing or active call audio, navigation continues for the call, including supported internet calls. The app checks only the audio mode; it does not access phone numbers, contacts, call logs or call audio. Once call audio ends, the normal 30-second grace period restarts. Call detection may vary by phone or calling app. Returning within the grace period continues the same trip. Staying away longer pauses GPS and saves the latest progress; returning later requests fresh location and resumes the trip. Planning does not receive this grace period. A checkpoint is also saved on backgrounding, and on completion or GPS failure during the grace period. Apart from detected call audio, the app does not offer indefinite background navigation. It does not maintain a separate history of every GPS fix. Route progress and selected destinations may nevertheless reveal where you have travelled or intend to travel. Information stored on your device The app stores named routes, route names, waypoints, road/trail geometry, selected destination labels, imported GPX data, display preferences and map/network caches, including any map areas retained from older versions. It also automatically stores the current plan or trip, including the next waypoint and travelled route distance, so it can recover after interruption. Stop retains the route as a plan; it is not a delete command. Saved routes remain until you delete them from the route folder or clear the app's storage. The running plan and trip are retained when you minimise and return to the app. A fresh app launch clears the previous working trip and legacy working-plan data; it does not delete named saved routes. Clear all and Done also clear the corresponding working plan. These controls do not delete named routes. Successful search results, search text and the location used to bias that search may be cached locally for reuse for up to seven days. Successful road calculations, including their exact endpoints, geometry and instructions, may be cached locally for reuse for up to 24 hours. The persistent search/routing cache is limited to 2 MiB, with up to 128 search entries and 32 route entries; older entries can be evicted sooner, and expired entries are discarded during cache maintenance. Options > Clear search and routing cache removes these caches without deleting named saved routes. This cache does not send usage reports or analytics to us. The renderer may retain previously fetched map detail and older offline areas, but the current app provides no detailed-area download control. Cached detail can be incomplete or evicted and is not guaranteed offline coverage. Map/network caches are replaced or limited as the app manages them; clearing Android app storage removes the app's local data. GPX import reads the file you choose through Android's file picker. GPX export writes route information to the destination you choose. Exported files may contain location information. Their storage provider, access permissions and later sharing are under your control; deleting a route in the app does not delete an exported file. Android backup or device-transfer services may copy app data, depending on your device and account settings. Clearing or uninstalling the app does not necessarily remove exported files or existing backup copies. Check your Android and backup-provider settings if you want to remove those copies. Online requests and service providers Some features send information to external services. Requests use HTTPS. Providers receive your network IP address and normal request metadata, and may keep service, security or usage logs under their own policies. The app does not upload your whole saved-route library to an operator-owned cloud service. • Geoapify provides primary place/address search in configured builds. It receives your search text and may receive your current latitude/longitude to prefer nearby results. Photon, hosted by komoot, receives similar information if Geoapify is unavailable or rejects a request, or in builds without Geoapify configuration. Autocomplete can send partially typed searches before you press Search. • Postcodes.io receives a full Great Britain postcode when you request postcode lookup. Northern Ireland BT postcode queries are blocked. Avoid entering sensitive information that is not needed to find a destination. • Geoapify receives start and destination coordinates to calculate a road route or reroute. If primary routing fails, the app automatically tries the public OSRM service, which receives those coordinates instead. There is no user-facing fallback switch. Builds without Geoapify configuration can also use OSRM for nearest-road lookup. We do not send it your saved-route names or the whole route library. • Trail/path recognition and byway display use data included in the app. This does not send your planned off-road points to a trail-query service. Road/destination positioning uses GPS, available route geometry and road geometry already loaded for the map. This on-device matching makes no separate road-data request. • OpenFreeMap supplies online map tiles, styles and related map resources. Requested tile coordinates identify the map areas being viewed or downloaded. Locally bundled or fully cached resources do not require a new provider request for those resources. Opening attribution links opens your browser and is also subject to the relevant website's privacy practices. Provider information: Geoapify: https://www.geoapify.com/privacy-policy/ Photon: https://github.com/komoot/photon Postcodes.io: https://postcodes.io/ OSRM service operator: https://routing.openstreetmap.de/about.html OpenFreeMap: https://openfreemap.org/privacy/ These organisations operate their own infrastructure. Their retention periods and processing locations may differ from the app's local storage. Online requests may be processed outside the UK. Before public commercial distribution, the operator must confirm applicable provider arrangements, processing locations and any required international-transfer safeguards; this policy does not claim that those checks are already complete. Purposes and legal basis Where UK data-protection law applies, our proposed basis for the current app's essential processing is legitimate interests: providing the mapping, search, route-planning, navigation and recovery functions you request, while limiting information to what those functions need. You can object to processing based on legitimate interests by contacting Anton MacMinn. Android permission controls whether the app can access location; granting that permission is not a blanket agreement to unrelated data use. If you contact us, we use your message and contact details to respond and resolve your enquiry, on the basis of our legitimate interests in providing support. We keep that correspondence only as long as needed to resolve the enquiry and retain records reasonably necessary for follow-up, disputes or legal obligations. We may retain or disclose information where required by law. The proposed basis and provider arrangements require the operator's review before public release. Your choices and rights You can revoke location permission, stop navigation, delete saved routes, clear the current plan, manage Android backup settings, and clear app storage. Online search, new road routing and uncached map detail need connectivity. Bundled trail recognition works locally. Offline mode concerns map display and does not guarantee that every other feature avoids network requests. Depending on the circumstances and applicable law, you may request access, correction, deletion, restriction or portability of your personal information. You also have the right to object to processing based on legitimate interests. Contact Anton.MacMinn@hotmail.com to exercise these rights. We cannot directly read routes stored only on your device; we will explain available local controls or ask only for information necessary to handle your request. You can raise privacy concerns with us using the contact details above. You also have the right to complain to the Information Commissioner's Office (ICO): https://ico.org.uk/make-a-complaint/. Private beta builds A separately configured private beta may additionally send an activation code, installation public key, signed request and request time to its activation service. That service uses an invitation record and signed permissions to control beta access. The private installation key remains on the device. This does not apply to the ordinary release unless a beta activation service is configured. The beta operator must disclose its actual service contact, hosting and record-retention arrangements before inviting testers. Changes and release status We will update this policy if the app's data handling changes and update the date above. Material new uses of personal information will be explained before they begin, with any permission or consent required for that use. This policy is a draft for the current development release. Operator approval of the legal basis and provider/transfer arrangements, and a publicly accessible policy URL, are still required before a commercial release.