Corridor · last updated 14 October 2026
The app has no account, no sign-in, and no server running code I wrote. Almost everything the app knows about you stays on your phone: where you are, where you have walked, where you slept, what you have planned. None of that is ever sent anywhere.
The app does count how it is used, anonymously. Which screens and trails get opened and for how long, and which features get tapped — never where you are, never who you are. There is a section on it below, and a switch in Settings that turns it off.
This website is a different thing, and it does count its visitors. That is new as of today and there is a section on it below. Nothing joins the two: the site learns nothing about your phone, and the app sends nothing here.
Two things you can choose to share: a comment about a place, and a report on a water source. If you write one, it goes to Apple’s iCloud so other hikers can read it. Those and the anonymous usage counts below are the only things this app ever sends.
Every waypoint has a place to write a note for the next hiker — the tank is dry, the door sticks, the creek below is running. Writing one is entirely optional and the app is complete without it.
If you write one, these things are stored in Apple’s iCloud and are public: what you wrote, when you wrote it, which place it is about, and the trail name you chose if you chose one. Your comment is signed anonymous if you did not.
I never learn who you are. There is no sign-up and nothing to fill in. iCloud identifies you to the app by an opaque code that is different for every app you use and cannot be turned back into a person — not by me and not by anyone else. I never receive your name, your email address, your phone number or your Apple Account.
You can delete any comment you have written, at any time, from the place it is about. You can hide any other hiker’s comments by blocking them, and report anything that should not be there — a reported comment disappears from your phone at once, and reports are read and acted on within 24 hours.
Everything you write is checked on your own phone before it is sent, against a list of words that are not allowed. That check happens on the phone and the text is not sent anywhere to perform it.
A comment stays in the app until you delete it or it is removed for breaking the rules.
A water source can carry a report: whether it had water, almost none, or was dry, and when you saw it. If you send one, these things are stored in Apple’s iCloud and are public: the reading, the day you saw it, which water source it is about, and the trail name you chose if you chose one. The location stored with it is the water source’s, not your phone’s.
You can delete any report you have sent, from the water source it is about. A report stays in the app until you delete it or it is removed for breaking the rules.
Before your first comment or water report, the app asks you to agree to one thing: that Corridor may publish what you write and report — in the app, and as part of a free, open dataset (under the ODbL or a similar open licence) that anyone, including other trail apps, may download and reuse. Nothing is posted until you agree, and if you never agree, nothing you do in the app is shared at all.
What goes into that dataset is exactly what is public in the app already: what you wrote or reported, the day, the place it is about, and your trail name if you set one. It never contains your Apple Account, your email, the code iCloud identifies you by, or your phone’s location.
Deleting a comment or a report removes it from the app and from every later copy of the dataset. A copy somebody downloaded before you deleted it cannot be recalled — which is true of anything public, and the reason it is said here rather than left for you to work out.
If you never write a comment or send a report, nothing about you is stored in iCloud by this app at all. Reading what other people wrote sends nothing.
So I can tell which parts of the app are worth building on, it keeps a tally of how it is
used and sends it to PostHog, on servers in the European Union,
through e.corridor-trails.com — the same route this website’s counts take.
What is counted: when the app is opened and for how long; which trail is loaded; how that time splits between the map, its two modes, the trail pages and Settings; which kinds of place you open (a water source, a hut); which map tools you use; whether a map download finished or failed; that you posted a comment or a water report, but not what it said; which settings you switch. Alongside it: the app’s version, the iPhone model, the iOS version and language, and roughly which country the request came from, worked out from your IP address, which is not kept beside the result.
One thing is worked out from your location, and only one: whether you were within a kilometre of the trail at the time, as a yes or a no. It is what tells planning a trail at home apart from walking it. No coordinate, no distance and no route ever leaves the phone.
The counts are tied to a random code the app makes when it is first opened. It is not your name, your Apple Account, your device’s advertising identifier or anything else that could be traced back to you, and deleting the app deletes it. Nothing joins it to your comments or to this website.
Without a signal the counts wait on the phone and are sent the next time there is one. To stop them, turn off Share anonymous usage in the app’s Settings: nothing more is counted and anything still waiting is deleted from the phone. Nothing is used for advertising, nothing is sold, and nothing is shared with anybody else.
The app asks for your location so it can show where you are on the trail, measure how far you have walked, and warn you about water sources ahead. That location is read on the phone, used on the phone, and stored on the phone. It is never transmitted, never logged off the device, and never shared with anyone — including me. The one thing derived from it that does leave the phone is the yes-or-no described under Usage statistics.
You can refuse the permission or withdraw it at any time in iOS Settings. The app still works; it simply cannot draw where you are.
All of it lives inside the app's own storage and is deleted when you delete the app.
Three things cross the network.
Apple’s own handling of iCloud data is covered by Apple’s privacy policy, and Cloudflare’s by Cloudflare’s.
corridor-trails.com counts its visitors too. I write this on my own, for hikers, and the only way I can tell whether a page here is doing its job is to look at whether anybody reads it.
The site uses PostHog, on servers in the European Union, to record which pages are opened, how long they stay open, what is clicked, and roughly which country the request came from — worked out from your IP address, which is not kept beside the result. It also keeps a replay of a visit: a reconstruction of what moved on the page, rebuilt from the events your browser fired rather than from anything read off your screen. Anything typed into a field is masked before it leaves the browser, and there is no field on this site worth typing into anyway.
This needs a cookie, and the honest reason is that without one every page you open counts as a new stranger and how long did somebody stay cannot be answered at all. The cookie holds a random code and nothing else. It is not shared, not sold, and never used for advertising.
Those requests do not go straight to PostHog. They go to e.corridor-trails.com, a
subdomain of this site, and on to PostHog from there — because a browser extension that
blocks posthog.com by name otherwise deletes a fifth of the numbers without telling
anybody. That routing is done by Cloudflare,
who already hand out the map packs the app downloads.
If your browser sends Do Not Track, none of it runs. Blocking the script blocks all of it too, and the site works exactly the same either way.
One, in both the app and this website: PostHog, which receives the anonymous counts described above. There is no PostHog code in the app — the app sends its counts itself — and no advertising, no tracking across other apps or websites, and no crash reporting. The two libraries the app is built with draw the map and unpack the downloaded one.
Corridor is rated 4+. It lets hikers write notes other hikers can read, and nothing about you is collected unless you write a comment or send a water report.
If this policy ever changes, the date at the top of this page changes with it.
Questions about privacy, or something in a comment that should not be there: beiserjohannes@gmail.com
Licensing & attribution — every source the map is built from, and what each one asks to be called.