Walking to the Moon Support

Last updated: 2026-08-06

Walking to the Moon is a step-motivation app for iPhone. This page covers the most common setup, Apple Health, Social, account-recovery, and privacy questions.

Steps are zero or have not updated

Walking to the Moon reads Steps and Walking + Running Distance from Apple Health only after you grant read access. You can review access in the Health app or in iPhone Settings under Health.

Apple does not tell an app whether read access was denied, so a zero can mean either that no steps are available or that access is unavailable. Open Apple Health to confirm that recent steps exist, then return to Walking to the Moon and pull down on Today to refresh.

Apple Watch activity can take time to reach Apple Health on the iPhone. Keep the Watch and iPhone nearby, let Apple Health finish updating, then refresh Today. Walking to the Moon cannot show whether Watch synchronization itself has finished.

Today can also request separate Motion & Fitness access so the number rises from this iPhone’s motion coprocessor between Apple Health refreshes. Denying that permission does not stop Apple Health-backed journey progress; it only removes the temporary live update. You can change Motion & Fitness access in iPhone Settings.

Why does Atlas use the network in solo mode?

The journey itself remains account-free and works offline. When a network is available, the app can send an empty, App-Check-protected request for anonymous worldwide counts showing how many opted-in Social profiles reached each Atlas stage. The request contains no steps, Health data, local profile, or journey position. If it fails or the phone is offline, Atlas uses its local fallback copy.

What does Bring available Apple Health history do?

It previews one aggregate snapshot of the walking history Apple Health makes available before the journey activation boundary. It is not described as an entire-life record. You can skip it, review it before saving, refresh it later, or remove it.

The complete Today count is display-only. On the activation day, it can include steps from earlier that day, but those earlier steps never enter journey progress, Atlas, recaps, or Social.

Moving to a new iPhone

The local movement store is not synced through CloudKit and is excluded from ordinary device backups. Provider-linked Social recovery does not restore daily charts, recaps, private recorded distance, observed activity dates, the Today cache, distance-unit choice, or notification preferences. A separate Apple device-migration process may handle ordinary preferences differently, but it is not the app’s Social recovery path.

If you turned on Social, linked Apple or Google, and your aggregate progress is still shared, signing in on the new iPhone can restore the Social username, voyager, friends, consent state, and server-held aggregate step position used for the Atlas. Imported steps return only while the separate imported-history sharing option is on. If sharing was paused, the remote step aggregates were deleted and cannot be restored from Social.

Only one installation is allowed to publish for a protected Social profile at a time. Completing recovery on a new iPhone makes it the active publisher and pauses publication from the old iPhone. To switch back, open the old iPhone while signed into the same protected account and use its restore-publication action; the most recent successful claim becomes authoritative.

Adding or managing friends

Turn on Social, open the Social tab, and choose Add a friend. One person creates a private invitation code and the other enters it. Codes expire and can be used only as shown in the app.

Open a walker’s profile from the board to remove, block, or report that account. Blocking immediately removes both people from each other’s boards. A report does not automatically block the person, so use both controls when appropriate.

Deleting Social versus resetting the journey

Delete social account removes the authentication account, public profile, username claim, shared aggregates, connections, report relationships, and leaderboard projections. Before a Google-linked deletion is dispatched, the app asks Google again and confirms that the fresh credential belongs to the same Firebase account. After server deletion succeeds, it revokes Apple access where applicable and disconnects the confirmed Google grant. If Google cleanup cannot finish, the app keeps Social closed on an account-cleanup screen, lets the person retry, and provides Support. The person may also remove Walking to the Moon access from their Google Account. Restricted moderation case, audit, removal-approval, and linked-identity hold and block records may remain under the Privacy Policy’s separate retention rule. A temporary identity hold is released after valid independent rejection or cancellation; if the profile still exists, its projections can be restored, but already deleted data is not recreated. Deletion does not erase the local solo journey.

Reset journey deletes the local journey on this iPhone and starts onboarding again. These are intentionally separate actions.

Contact and moderation

For support, a moderation appeal, or an account-deletion problem, email doldorijw@gmail.com. Include the app version, iOS version, the screen where the problem happened, and the exact error message. Do not email raw Apple Health exports, provider passwords, sign-in tokens, or screenshots containing private health details. Reports and the support inbox are not monitored in real time, there is no fixed response deadline, and Walking to the Moon is not an emergency service. If someone may be in immediate danger, contact local emergency services or a trusted local authority.

Related: Privacy Policy (https://joonwoopark.me/walking-to-the-moon/privacy) · Terms of Use (https://joonwoopark.me/walking-to-the-moon/terms)