Last updated: 2026-09-22
Run More One is a running app: you run, and the real distance you cover becomes turns you spend exploring a dungeon inside the app. This page states, in plain language, what the app reads, what it sends anywhere, and what it does not.
When you grant Health access, Run More One reads exactly two things: your running workouts and your walking/running distance. That is the complete list — the app requests no other Health data type of any kind. Specifically:
This data is read on your device and used on your device to compute how many turns you have earned. It is not transmitted anywhere as part of that computation.
This is not a promise we are asking you to take on faith — it follows from how the app is built. The one file in the app permitted to send anything to our analytics service (TelemetryDeck) accepts only a fixed, closed set of non-numeric signal names as input. There is no code path anywhere in that file that can accept a distance, a duration, a date, or a turn count and forward it — those types simply do not appear among the values that file's functions can take. A number describing your run cannot reach a network request through this seam, by construction, not by omission.
The complete list of what that service can be told, in plain terms, is:
Every one of those eight signals is a fixed name, never a number you generated by running. No distance, no duration, no date, and no turn count is ever attached to any of them.
One honest limit on that guarantee: the analytics SDK itself (TelemetryDeck) is a piece of software we did not write, and like most such services it may attach its own anonymous device or install identifier and standard technical metadata (such as coarse device/OS information) to every signal it sends, independent of anything the app tells it to send. That identifier and metadata are the SDK vendor's own baseline behavior, not something this app's code controls or can inspect from inside this repository — we are not able to verify their exact contents the same way we verified the eight signals above, and we say so here rather than asserting more than we have checked. It is never linked to your Health data, because nothing in the file that talks to this service ever receives a Health-derived value to attach in the first place.
If you buy access to a past week's dungeon, that purchase is processed by RevenueCat, our in-app-purchase service. RevenueCat receives your purchase, transaction, and entitlement information — but under an anonymous identifier it generates itself, not your name, email, or any account of ours, because Run More One does not create or require an account. Your purchase record is not linked to anything read from Health, and it is not linked to you as a person by us or, to the best of our understanding of the service we use, by RevenueCat.
Run More One has no login, no sign-up, and no user profile. Your wallet of turns, your dungeon progress, your journal, and your run history all live only on your device. If you delete the app, that data is gone — we don't have a copy anywhere, because we were never sent one. The single exception is the anonymous purchase identifier described above, which exists only if you made a purchase, and which is not linked to your identity.
The pages at run.thunk.tech send one anonymous page view per page load to the same analytics service the app uses (TelemetryDeck), so we can see roughly how many people read them. The site sets no cookies and does no fingerprinting. The service tells visitors apart with a hash of the IP address, browser user agent, and a salt that changes every day, which means it can count a return visit on the same day but cannot recognise you across days or across other websites. The site has no forms and no login, so there is nothing else it could send.
Run More One does not collect, request, or transmit:
If you have a question about how Run More One handles your data, write to [email protected].