Last updated: 16-07-2026
Runney (“the app”) is designed to keep your data on your device. This policy explains what data the app accesses, how it’s used, and — just as importantly — what we don’t do with it.
Runney reads the following from Apple Health (HealthKit), with your explicit permission, granted through Apple’s standard Health access prompt:
Runney does not request permission to write or modify any data in Apple Health.
Runney offers an optional “Runney Pro” subscription (monthly or yearly, with a free trial on the yearly plan) that unlocks additional features. All payment processing is handled entirely by Apple through the App Store — Runney has no payment system, server, or database of its own, and never sees or stores your payment details.
To check whether you have an active subscription, Runney reads your purchase status directly from Apple’s on-device StoreKit framework. This check happens locally and isn’t sent to any server we operate. Apple’s own systems retain a record of your purchase (as they do for any App Store purchase) under your Apple ID — see Apple’s own Privacy Policy for how they handle that.
You can view, manage, or cancel your subscription at any time via your Apple ID Account Settings, on your device or at reportaproblem.apple.com.
UserDefaults storage.If you choose to enable the optional weekly recap notification, Runney schedules a local notification directly on your device using Apple’s notification system. No data leaves your device to make this happen.
Because Runney doesn’t store your data anywhere except your own device, deleting the app removes all app-specific data (preferences, goals, cached calculations) immediately. Deleting Runney does not affect your underlying data in Apple Health — that remains managed by Apple’s Health app, under your control there.
Runney is not directed at children and does not knowingly collect data from children. Since the app does not collect any data beyond what stays on-device, no data is collected from any user, regardless of age.
If Runney’s data practices change in a future update (for example, if a feature is added that requires a server we operate), this policy will be updated accordingly, and the “Last updated” date above will reflect that.
If you have questions about this policy or how Runney handles data, contact:
remcoudb@gmail.com