Privacy Policy

Last updated: 20 September 2026

ContentsSummary

This Privacy Policy explains what happens to your information when you use WANDOO — the WANDOO mobile app for iOS and Android, and the route planner at wandooapp.com. WANDOO is developed by SimpleInnovation LLC, the developer listed on the App Store and Google Play. SimpleInnovation LLC is part of AppManage Group #1, LLC.

The short version: WANDOO has no user accounts, no sign-up and no advertising. We do not run a server that stores your hikes. Your tracks, routes and downloaded maps stay on your device.

Summary

No account, ever. There is no registration, no login and no profile. We never ask for your name, email address or phone number.
Your hikes stay on your device. Recorded tracks, saved routes, offline map packs and search history are stored in the app's own storage on your phone. We have no server that receives them.
No ads. The app contains no advertising SDKs and shows no ads.
The website sets no cookies and runs no analytics. No Google Analytics, no Tag Manager, no advertising pixels, no session recording.
Nothing is synchronised. Without accounts there is no sync between the website and the app, or between two devices.
We cannot see your payment details. Subscriptions are processed entirely by Apple and Google.
Your location leaves your device only to draw the map. Map tiles, search and routing are provided by Mapbox, MapTiler and OpenStreetMap, which need the coordinates of the area you are looking at.
We do use analytics and attribution tools — Firebase, Crashlytics and AppsFlyer — to understand how the app is used and whether it crashes. What they receive is described below.

1. Who we are

WANDOO is developed by SimpleInnovation LLC, the developer listed on the App Store and Google Play. SimpleInnovation LLC is the controller of your personal data. Its parent company is AppManage Group #1, LLC.

SimpleInnovation LLC
15127 NE 24th Street, Ste 132
Redmond, WA 98052
United States

Privacy enquiries: wandoohiking@simpleinnovation.us

2. What we collect, why, and who receives it

The table below covers everything that leaves your device. Section 3 covers what does not.

What	What exactly	Why	Legal basis (GDPR)	Who receives it	Retention
Precise location	Coordinates of the map area you view, waypoints you place, and your current position as a search proximity hint	To draw the map, search for places, and calculate routes	Art. 6(1)(b) — to provide the service you asked for	Mapbox, MapTiler, OpenStreetMap/Overpass (website only), AWS elevation tiles	Not stored by us. See each provider's policy
App usage	Screens opened, features used, session events. No coordinates are sent to analytics	To understand which features are used and improve the app	Art. 6(1)(f) — our legitimate interest in improving the app	Google (Firebase Analytics)	We keep no copy. Firebase deletes event data automatically after the retention period set on our project
Crash diagnostics	Crash stack traces, device model, OS version, app version	To find and fix crashes	Art. 6(1)(f) — our legitimate interest in a working app	Google (Firebase Crashlytics)	We keep no copy. Crash records expire automatically in Crashlytics
Advertising identifier (IDFA / Android advertising ID)	Collected only if you allow it in the App Tracking Transparency prompt on iOS, or the equivalent consent on Android	To measure which campaign led to an install and to connect that install to a purchase	Art. 6(1)(a) — your consent	AppsFlyer, RevenueCat	We keep no copy. Retained in those systems under their own retention settings
Vendor identifier (IDFV) and AppsFlyer ID	Anonymous identifiers generated for your device or app installation	Install attribution and purchase measurement	Art. 6(1)(f) / Art. 6(1)(a) where consent applies	AppsFlyer, RevenueCat	We keep no copy. Retained in those systems under their own retention settings
Purchase data	An anonymous RevenueCat App User ID, your entitlement status (Pro or not), the product purchased, purchase and expiry dates, trial and auto-renewal state, your store country, and the App Store or Google Play transaction record	To unlock the features you paid for, restore purchases and handle refunds	Art. 6(1)(b) — to perform the subscription contract	RevenueCat	We keep no copy. Subscription records are held by RevenueCat and by the app store for as long as the subscription and the store's own records require
Support messages	The text you write in "Send feedback" or "Suggest place", plus an automatically generated email address, platform, app name and version, OS version, device model, language and purchase status	To answer you and to act on the place you suggested	Art. 6(1)(f) — our legitimate interest in supporting users	Zendesk	We keep no copy outside Zendesk. Tickets stay in Zendesk until deleted
Map library telemetry (website only)	The Mapbox GL JS library sends map usage events to events.mapbox.com and stores an anonymous identifier (`mapbox.eventData.uuid`) in your browser	This is built into the map library, not something we add	See section 7	Mapbox	Set by Mapbox
IP address	Any service your device contacts sees your IP address, as with any internet request	Technically unavoidable	Art. 6(1)(f)	All providers listed above	Set by each provider

We run no servers of our own. There is no WANDOO database and no WANDOO cloud. Everything in the table above lives either on your own device or inside the systems of the providers named, under their retention settings and their security programmes. We hold no separate copy that outlives them.

We do not sell your personal data and we do not share it for cross-context behavioural advertising.

3. What stays on your device

This is the part most hiking apps cannot say, so we want to be precise about it. We do not operate a server that stores your hiking data. The following never leaves your phone:

Recorded tracks. Every hike you record is written to the app's own private storage on the device.
Saved and planned routes, including waypoints you place yourself.
Activity and fitness metrics — distance, ascent and descent, pace and duration. These are calculated on your device from the GPS track and the barometer. They are not transmitted anywhere.
Offline map packs you download, including the separate satellite layer, plus the cached elevation data, route preview images and your search history.

Two consequences follow, and you should know both:

Your hiking history is private by default. There is no account to breach, and we could not hand over your tracks even if we were asked for them, because we do not have them.
If you delete the app, this data is gone. There is no backup on our side and no way to restore it on a new device.

On the website, your favourite routes, the last map position, planner settings, onboarding progress and interface state are kept in your browser's local storage. They stay in that browser and are never sent to us.

4. Location

WANDOO is a navigation app, so location is the one permission it genuinely needs.

Accuracy. The app requests precise location. Without it, the map cannot show where you are on the trail.
Background use. Location updates continue in the background only while you are actively recording a hike. Your operating system shows its own indicator while this happens — the blue status bar on iOS. When you stop the recording, background updates stop.
What leaves the device. Your track is not uploaded. Coordinates leave your device only as part of map requests: Mapbox receives the coordinates of the area being displayed and of the points you place when building a route; MapTiler receives your search text together with your current coordinate, so that nearby results come first, and receives a coordinate when the app converts it into a place name. On the website, the planner additionally asks OpenStreetMap (via Overpass) for the footpath network inside the map area you are viewing, and fetches public elevation tiles from AWS.
Analytics never receives coordinates.
Turning it off. You can revoke location access at any time in your device settings. The map will still work; live positioning, recording and "near me" search will not.

5. Activity and fitness data

Distance, elevation gain and loss, pace and moving time are computed locally on your device from the GPS track and the barometric sensor. They are stored on the device and are not sent to us or to anyone else.

WANDOO does not use Apple HealthKit or Android Health Connect. It does not read anything from your health data and does not write anything into it.

6. Advertising and tracking

WANDOO contains no advertising SDKs and shows no ads. There is no Google Mobile Ads SDK in the app and no advertising pixel on the website.

We do use attribution measurement. When you install the app, AppsFlyer helps us understand which campaign or link brought you, and RevenueCat connects that information to a subscription purchase so that we can tell which channels are worth continuing. For this, AppsFlyer and RevenueCat may receive your device's advertising identifier.

On iOS, the advertising identifier (IDFA) is collected only if you allow it. We show a short explanation and then Apple's App Tracking Transparency prompt during your first session. If you decline, the identifier is not collected and the rest of the app works exactly the same.

7. The website

wandooapp.com is a static site. There is no back end, no database and no account system, and there are no forms anywhere on it — so there is nothing on the site through which we could collect personal data about you.

No analytics or marketing scripts. No Google Analytics, no Google Tag Manager, no Meta Pixel, no Hotjar or Clarity, no advertising pixels. We verified this against the production build.
No cookies. The site sets none at all, which is why you see no cookie banner.
Local storage only, for the things you would expect to persist: your favourite routes, the last map position, planner settings, onboarding progress and interface state. This stays in your browser.
Fonts are self-hosted. The site makes no requests to Google Fonts.
Links only, no embeds. Links to the App Store, Google Play, our social profiles, Telegram and WhatsApp sharing, and Wikipedia for photo attribution are ordinary links. They carry no tracking pixels, but once you follow one, that site's own privacy policy applies.

There is one exception we want to name rather than bury. The interactive map is built with Mapbox GL JS, and that library sends its own map usage telemetry to events.mapbox.com and stores an anonymous identifier in your browser's local storage under mapbox.eventData.uuid. This is behaviour of the Mapbox library itself, not something we added.

8. Subscriptions

WANDOO Offline Pass is an optional subscription sold through the app stores.

The payment itself is handled entirely by Apple or Google. We never see your card number or any other payment instrument.

Through RevenueCat, which manages subscription state for us, we see: an anonymous RevenueCat App User ID, whether your subscription is active, which product you bought, the purchase and expiry dates, whether you are in a trial and whether auto-renewal is on, your store country, and the store's transaction record. We do not send your name or email address to RevenueCat, because we do not have them.

To manage or cancel a subscription, use the subscription settings in your Apple ID or Google Play account. Refunds are handled by the store, not by us.

9. Using WANDOO without an account

There is no registration, no login and no password. You do not create a profile, and we do not maintain one.

Because there is no account, nothing is synchronised. Routes you save in the web planner stay in that browser. Routes and tracks in the app stay on that phone. They do not travel between the website and the app, and they do not travel between two devices.

If we introduce accounts in a future version, we will update this policy before that feature ships and say plainly what changes.

When you share a route or a Share Card, your device's own sharing menu sends it to whichever app you choose. From that moment the receiving app's privacy policy applies.

11. Your rights

If you are in the European Economic Area or the United Kingdom, you have the right to access your personal data, to have it corrected or erased, to restrict or object to processing, to data portability, to withdraw consent at any time, and to lodge a complaint with your national supervisory authority.

If you are a California resident, you have the right to know what personal information is collected, to have it deleted or corrected, to opt out of sale or sharing, and not to be discriminated against for exercising these rights. As described above, we do not sell personal information and do not share it for cross-context behavioural advertising.

In practice, the most direct controls are in your own hands:

Location — revoke the permission in your device settings.
Advertising identifier — decline the tracking prompt, or reset or disable the identifier in your device settings at any time.
Everything stored on the device — delete the app.
Website local storage — clear site data for wandooapp.com in your browser.

For anything else, write to wandoohiking@simpleinnovation.us. We may ask you for information that helps us identify the records in question; because we do not hold accounts, there is often no identifier that links data to you personally.

12. Deleting your data

Data on your device: delete the app. Tracks, routes, offline maps, cached elevation data, route previews and search history are removed with it. This cannot be undone.
Website data: clear site data for wandooapp.com in your browser.
Data held by our providers — analytics and crash records, attribution data, subscription records and support tickets: email wandoohiking@simpleinnovation.us and we will process the request.

There is no "delete my account" button because there is no account to delete.

13. International transfers

We are based in the United States, and the providers listed in section 2 process data in the United States and other countries.

14. Children

If you believe a child has provided us with personal data, write to wandoohiking@simpleinnovation.us.

15. Security

Data in transit is encrypted. The strongest protection here is structural rather than procedural: your hiking data never reaches a server of ours, so there is no central store of user tracks to be breached. The data held by our providers is protected under their own security programmes, linked in section 2.

16. Changes to this policy

If this policy changes, we will update the date at the top and publish the new version at this address. Material changes will be announced in the app.

17. Contact