Privacy Policy

Last updated: 2026-11-03

This policy explains what the Dappleway apps for iPhone and Android and this website collect, why, and how to switch it off or delete it. The short version: your Apple Health or Health Connect data stays on your phone, the only thing written back is a warm-up you do in the iPhone app, saved to Apple Health, and the camera records nothing.

What Dappleway is

Dappleway is an app for iPhone and Android with a small companion that grows from the days you already live. The two apps are the same game and follow this same policy; where they differ, this page says so. There is no account and no sign-up: the app never asks for your name, email address or phone number. Your companion, the name you give it, your history and your settings are stored only on your phone. On Android, Android's own backup can keep a copy in your Google account (see Android backup). Because there is no account, nothing moves between an iPhone and an Android phone.

This website uses no cookies, no analytics and no scripts. It is served by Cloudflare Pages, which handles each request the way any web host does.

Apple Health (iPhone)

We read your data, and write back only the warm-ups done here, as workouts. Nothing leaves your phone. With your permission, Dappleway reads these types from Apple Health:

Purpose. The app uses them to compute daily summaries — steps, distance, hours of sleep and workout minutes for each day — and to move your companion along the path. Nothing else is done with them: no advertising, no profiling, no selling and no sharing.

What is written. When you start the warm-up of the day with Start on iPhone and finish it, Dappleway saves it to Apple Health as one workout of the warm-up's kind (yoga or dance, for example), with its start, its end and any pauses. Nothing else is ever written: no heart rate, no energy, no steps, and nothing from camera sets. The permission to save workouts is asked the first time you tap Start on iPhone, never when you connect Health. Without it the warm-up runs the same, and nothing is saved.

Storage. The summaries are kept only on your iPhone, in the app's own container and in the app group it shares with the Dappleway home-screen widget. They are never uploaded to us or to anyone else. The only thing Dappleway writes to Apple Health is the warm-up workout described above.

Your choice. You pick which types Dappleway may read, and whether it may save workouts, in the system dialogs, and you can change that at any time: Health app → Sharing → Apps → Dappleway (or iOS Settings → Privacy & Security → Health → Dappleway).

Health Connect (Android)

On Android, Dappleway reads from Health Connect, the place where Android keeps the health and fitness data that your phone and your other apps record. We only read your data. Dappleway never writes anything to Health Connect, and what it reads goes to no server: not to us and not to anyone else. With your permission, it reads these four types:

Nothing is written. Unlike the iPhone app, the Android app doesn't save warm-ups: it has no Start on phone, and it never asks for permission to write. The warm-up of the day counts on Android when a workout of its kind, recorded by another app or a watch, arrives in Health Connect.

Purpose. The app uses them to compute one summary for each day — steps, distance, hours of sleep and workout minutes — which moves your companion along the path and shows you plain facts about your own days. On the first connection it reads your recent days, up to the last 90, so that your companion starts from your own walks. Nothing else is done with the data: no advertising, no profiling, no selling, no sharing, and nobody at Dappleway sees it, because it never reaches us.

Reading in the background. If you also allow Dappleway to read Health Connect in the background, a periodic job on your phone reads the day so far, so that the home-screen widget shows today's steps and the evening reminder can say how many steps are left to the day's goal. It reads only the four types above and sends nothing off the phone. Without this permission the app reads when you open it, and everything else works the same.

Storage and security. Only the daily summaries are kept, never the individual records Health Connect holds. They are stored in the app's private storage on your phone, which Android keeps closed to other apps, and they are never uploaded to us or to anyone else. They never appear in analytics or crash reports. The one copy that leaves the phone is the one in your own Android backup, if backup is on: Android keeps it in your Google account, end-to-end encrypted with your screen lock, where we cannot read it (see Android backup).

Retention and deletion. The summaries stay on your phone as part of your companion's history until you delete them. In the app, Settings → Delete everything removes them with everything else, and so does uninstalling the app.

Your choice. You pick which types Dappleway may read in Health Connect's own dialog, and you can change that at any time: Health Connect → App permissions → Dappleway. The data already summarised stays with your companion until you delete it.

Dappleway's use of information received from Health Connect adheres to the Health Connect Permissions policy, including its Limited Use requirements.

Camera

Camera sets are optional: your companion trains with you in front of your phone, and the app counts squats, push-ups and the seconds of a guided warm-up. Dappleway uses the front camera for this counting and for nothing else. It asks for the camera on the set-up screen of the first set, never before, and without the camera everything else in the app works the same.

On the phone. The counting happens on your phone. On iPhone, Apple's Vision framework looks at the frames from the front camera; on Android, Google's ML Kit pose detection does, with its model built into the app. Either way it runs on the device and finds the points of the body's pose — head, shoulders, elbows, hips, knees and ankles. It does not recognise who is in the picture. Only those points reach the counter, and each frame lives in memory for a moment and is gone; the live picture on the screen is shown, never kept. No photo, video or recording of you is made, stored or sent: not to us, not to anyone, and not even into the app's own storage on the phone. The camera is on only while the set-up or counting screen is open. It stops when the set ends, when you close the screen and when you leave the app, and iOS, like Android 12 and later, shows a green camera dot whenever it is on.

What is kept. A set keeps only which exercise it was, how many reps or seconds it counted (or the number you fixed it to), when it started and ended, and whether you fixed the number. Sets are kept on your phone with the rest of your companion's history, and Dappleway sends them to no server: there is no account, no iCloud sync and no server of ours that receives them. On Android they are part of the game your own Android backup keeps. They are never written to Apple Health or Health Connect. In the app, Settings → Delete everything removes them with everything else.

Your choice. You can switch the camera off for Dappleway at any time: on iPhone, iOS Settings → Privacy & Security → Camera → Dappleway; on Android, Settings → Apps → Dappleway → Permissions → Camera. The sets already done stay with your companion.

Android backup

On Android, the system's Auto Backup keeps a copy of your game in your own Google account, so that your companion comes back on a new Android phone or after you install Dappleway again. The copy holds what the app stores: your companion and its name, its history with the daily summaries and camera sets, and your settings. Downloaded map pictures and item art are left out to keep the backup small; the app downloads them again when they are needed.

Android makes the backup itself, about once a day when the phone is idle and on Wi-Fi, and keeps only the latest one. On Android 9 and later it is end-to-end encrypted with your phone's screen lock (PIN, pattern or password) when one is set. It goes to Google, never to us: there is no server of ours that receives it, and we cannot read it. When you set up a new phone with the same Google account, or install Dappleway again, Android restores the game before the app first opens.

Backup is Android's setting, not Dappleway's: switch it off in Android Settings → System → Backup (the name can differ by phone maker). On iPhone, Dappleway has no backup of its own.

Analytics (TelemetryDeck)

To learn which parts of the app are used, Dappleway sends anonymous usage signals to TelemetryDeck, a privacy-focused analytics service. A signal contains:

Signals never contain step counts, distances, hours of sleep, workout details or any other value from Apple Health or Health Connect, nor the reps or seconds of a camera set or your companion's name, and they are not used for advertising or to follow you across apps. TelemetryDeck does not store IP addresses. To switch analytics off: in the app, Settings → Share anonymous usage. More in TelemetryDeck's privacy policy.

Crash reports (Sentry)

When the app crashes, or runs into a problem it cannot recover from, it sends a report to Sentry so that we can fix the cause. A report contains the stack trace (the place in the code where it happened), the platform, the app version, the iOS or Android version, the device model and a random installation identifier created on your phone. Reports from the iPhone app and the Android app go to separate Sentry projects.

No IP address is stored — Sentry only notes the country a report came from — and a report never carries Apple Health or Health Connect values, anything from the camera, your companion's name or a screenshot: the app removes anything that looks like a health value before a report leaves the phone. The same switch stops crash reports: Settings → Share anonymous usage. More in Sentry's privacy policy.

Feedback form

If you write to us with Send feedback in the app's Settings, we keep:

Feedback is stored in a Cloudflare D1 database created in Cloudflare's Western Europe region, and is read only by the people who build Dappleway. It is used for nothing but answering you and improving the app. To have your feedback deleted, write to hello@dappleway.app.

Purchases

Your companion's coats, and Mango the bearded dragon with his Red and White coats, are optional one-time purchases: in the App Store on iPhone, and in Google Play on Android. The store handles the payment: we never see your card, your bank, your Apple ID or your Google account, and we receive no payment details at all. The app sends nothing about what you bought — not to us, not to TelemetryDeck and not to Sentry. On your phone it keeps only which companions and coats you have chosen.

On iPhone, which purchases you own is known to your Apple ID, so they come back on a new iPhone with Settings → Restore purchases, and refunds are requested from Apple, at reportaproblem.apple.com. On Android, which purchases you own is known to your Google account, so they come back when you install Dappleway with that account, or with Settings → Restore purchases, and refunds are requested from Google Play. A purchase made in one store stays in that store: it doesn't carry over between iPhone and Android. After a refund a coat simply gives way to the companion's free coat again, and Mango gives way to the companion you raised before him.

Notifications

Reminders are local notifications: your phone schedules them itself from what the app already knows. No server is involved in creating them, and nothing leaves the phone. Switch them off in the app's Settings → Reminders, in iOS Settings → Notifications → Dappleway, or in Android Settings → Apps → Dappleway → Notifications.

Data deletion

In the app, Settings → Delete everything removes your companion, the history with its daily summaries and camera sets, the settings and the downloaded game config and map pictures from your phone and cancels scheduled reminders. Coats you bought stay with your Apple ID or Google account. It sends one last anonymous data_deleted signal and then resets the analytics identifier. Deleting the app removes its data from the phone as well.

On iPhone, iOS doesn't let an app withdraw its own Apple Health access, so to stop sharing, turn Dappleway off in the Health app → Sharing → Apps → Dappleway. On Android, turn Dappleway's access off in Health Connect → App permissions → Dappleway; the next backup then replaces the copy in your Google account with the game as it is then, and Android's backup settings let you remove backups altogether. Feedback kept on the server is deleted on request — write to hello@dappleway.app.

Children

Dappleway is not directed to children under 13, and we do not knowingly collect information from them.

Changes

When this policy changes, the new version appears on this page with a new “Last updated” date.

Contact

Questions or requests about your data: hello@dappleway.app.