Privacy
Privacy Policy
Last updated: 12 October 2026
This policy covers two separate things: the SugarWalk app, and this website. They behave differently, so they are described separately rather than under one promise.
The app
The apps you block never leave your phone. That is Apple's rule, not only ours: the Family Controls entitlement SugarWalk is granted under forbids sharing that data with anyone, including us. It is the one guarantee here that cannot change.
Today, nothing else leaves either. Version 1 has no server, no account and makes no network requests of any kind — the build fails if networking is added. Where that could change one day is described under What could change, and this policy will say so before it does.
- The apps you choose. Picked through Apple's
FamilyActivityPicker. SugarWalk is handed an opaque token for each one and never learns which apps they are — we could not tell you what you selected if you asked. - Movement. SugarWalk uses Core Motion to tell whether you have been moving, so a block can end early when you have. It runs on your device. When a block ends, SugarWalk keeps when you were moving during it, so your record can show it. Its diagnostic log, which stays on your phone, also notes how many readings of each kind the sensor gave — walking, still, in a car — and is overwritten as it fills.
- Health data, read only, and only four kinds. With your permission, SugarWalk reads step count, workouts, wheelchair pushes and wheelchair distance from Apple Health — and nothing else. It reads them so that movement your iPhone did not see still counts: a walk you took with your phone left on a desk, or a workout recorded on an Apple Watch. The two wheelchair kinds are read for the same reason, but SugarWalk does not yet promise they end a block — that waits until it has been tested with a wheelchair. SugarWalk never writes to Apple Health, never stores the readings themselves — at most, the times they show you moving become part of that block's record, as above — never puts them in a log, and never sends it anywhere. If you refuse, the app works exactly as before — your iPhone's own motion still ends blocks early. Health data is never used for advertising or marketing; SugarWalk has no advertising and no third parties.
- No location, ever. There is no GPS, no geofence and no location permission anywhere in SugarWalk. It cannot tell a walk round the block from a walk round the hallway, and both count.
- Your meal times and block history. The meal times you set, and for each block how it ended and when you moved, are stored on your device. The history is kept for up to five years so the monthly record can show it, and it is part of your phone's backup like the rest of its data. Deleting the app deletes it.
- Two dates about your trial. When it began and the latest time the app has seen are kept in your iPhone's Keychain, so reinstalling does not restart the trial. Keychain items stay on your phone after the app is deleted. Like other app data, they are included in your phone's encrypted backup, so they move with it to a new iPhone; they never reach us.
- Notifications, where the app uses them, are local to your phone. There is no server to send a push from.
What the app does not do
- No account, no sign-in, no profile.
- No advertising SDKs, no analytics SDKs, no third-party trackers, no crash reporter.
- No camera or photo access.
- Nothing about you is sold or shared. There is nowhere for it to go.
This website
The website is not the app, and it is not silent in the way the app is.
- The waitlist. If you enter your email address, it is sent to Kit (kit.com), the email service that stores the list and sends the messages. That is a third party receiving your address, which is the point of a mailing list. Every email has an unsubscribe link and leaving removes you.
- Hosting. The site is served by Cloudflare Pages, which keeps ordinary server-side request logs.
- The one script that runs here, and it is not ours. Cloudflare adds its own Web Analytics to every page: a small script that reports the visit back to Cloudflare, so we can tell how many people a post actually sent. Cloudflare publishes what it collects. What we can tell you from checking the site ourselves is what it does not do: it sets no cookies, writes nothing to your browser's storage, and cannot follow you to any other site. That is why there is no cookie banner — there is no cookie. Cloudflare already sees every request as our host; this only turns those into a number we can read. Block it if you prefer; nothing on the site depends on it.
- No advertising pixel, and no advertiser. Nothing here is shared with one, and nothing on this site is used to target advertising anywhere.
Paying for it
SugarWalk is intended to be a paid app after a free trial. Any purchase is handled by Apple's In-App Purchase system — Apple processes the payment and SugarWalk never sees or stores your card details. If a future version ever uses a third-party service to manage purchases, this policy will be updated before that version ships.
Health-related framing
SugarWalk is not a medical device and does not diagnose, treat or monitor anything. It does not measure, estimate or display any physiological quantity — there is no blood-sugar reading in it, and no number about your body. It counts minutes of movement, and it has no sensor for anything else. What the app describes about walking after eating is general information drawn from published research, linked on the home page, and is not personal medical advice. Talk to a clinician about your own health.
Beta testing through TestFlight
Before the App Store release, SugarWalk is available to testers through Apple's TestFlight. If you install a beta build, Apple's TestFlight terms apply alongside this policy, and a few things are worth knowing that are specific to the beta:
- The app itself behaves exactly as described above. A beta build has no extra data collection, no analytics and no network code. It writes the same on-device log as every other build, and that log stays on your phone — there is no way for us to fetch it from you.
- What Apple sends us. TestFlight sends us crash reports automatically. If you choose to send feedback from inside TestFlight, Apple passes on what you wrote, the screenshot you attached if any, and basic device details (device model, iOS version, app version). Check the screenshot before you send it; we see whatever is in it. Apple describes exactly what it collects in its TestFlight terms, which you accept when you install.
- What you tell us directly. If you message, email or comment about the beta, we keep what you said for as long as the beta and the fixes that come from it, and use it only to improve the app. We will never quote you publicly without asking you first, and never with your name. If you want your messages deleted, say so at the address below and they will be.
- Who the beta is for. Testers must be 18 or over. SugarWalk is not medical advice and does not monitor anything about your body — see "Health-related framing" above. If you manage a health condition, talk to your clinician before changing when or how much you walk.
- Stopping. Delete the app, or leave the beta from the TestFlight app. The app itself leaves nothing behind on any system of ours, because it never sent anything there; the only record is whatever you chose to send us, and that is deleted on request, as above.
What could change
Features that let you share progress with family or friends — walk minutes, streaks, encouragement — are a direction we intend to build, and they would need accounts and a server. Two things are worth saying now rather than later:
- Which apps you block would still never leave your phone, because Apple's entitlement terms forbid it. That does not change with any feature.
- Anything shared would be a result you chose to share — minutes moved, a streak — with people you picked, and never raw health data. This policy and the App Store privacy label will both be updated before any such version ships.
Contact
Questions about this policy: support@sugarwalk.app
App operated by: Kiran Vallabh