Support

Work through these in order:

• Open the Health app › Sharing › Apps › HabitStakes, or Settings › Privacy & Security › Health › HabitStakes, and confirm that Steps is turned on for reading.
• Check that Health actually has steps for the day: Health › Browse › Activity › Steps. If your iPhone was not with you, or steps come from a watch that has not synced, there may genuinely be nothing to read yet.
• In HabitStakes, open Settings and tap Refresh step count.
• Unlock the phone and open the Health app once; Health can withhold data while the device is locked or has not been unlocked since restart.
• Restart the device if Health data appears elsewhere but never reaches the app.

Apple intentionally does not tell an app whether read access was denied, so HabitStakes cannot say “you denied permission”. It says there is no step data available instead. That wording is deliberate honesty, not a bug.

Health totals settle over time as your iPhone and any paired watch sync and de-duplicate samples. HabitStakes keeps a finished day provisional past the end of that day so late samples can land, and a later successful refresh can still move a day from forfeited to protected. Give it time, then refresh.

Day totals already recorded locally stay in your ledger; revoking access stops future reads. To remove those records, use Delete all local data in Trust & data. Revoking access in Health never deletes anything from the Health app itself.

No. It only reads daily step totals, and only with your permission. It never adds, edits, or deletes anything in Health.

Unresolved means the app could not see data for that day, so it refuses to guess. It is not a failure and it is not a forfeit. Once data becomes visible and a refresh succeeds, the day resolves.

Commitment days are calendar days in the time zone recorded when the commitment started, not rolling 24-hour periods. If you travelled after starting, days still follow the original recorded time zone, so boundaries can feel shifted.

Terms can be edited only while the start date is still in the future. Once the commitment has started, terms lock so completed and missed days cannot be rewritten. You can end the commitment and start a new one with different terms.

Reading and hydration progress only changes when you confirm the check-in shown on screen. Focus records only the time the timer actually observed — leaving the screen does not award the remainder of the target. Start the session again and let it run.

Settings has a Load demo week action for trying the app without real Health data. Demo data is kept out of your real ledger, and export is disabled while it is loaded. Clear the demo from Trust & data to return to your saved records.

That message appears when stored records were written by a newer version than the one installed. HabitStakes deliberately preserves those bytes instead of overwriting them, and pauses ledger updates and export. Update to the latest version of the app. If that is not possible and you accept losing the records, deleting all local data clears the state.

• In the app, turn on Allow HabitStakes reminders and check that the specific reminder type is enabled.
• In Settings › Notifications › HabitStakes, confirm notifications are allowed and that the alert styles you expect are on.
• Check Focus modes, Scheduled Summary, and Do Not Disturb — any of them can hold or silence a delivery.
• Low Power Mode and background restrictions can delay notifications that depend on fresh progress.
• Reminders are scheduled for the remaining days of a commitment; if the commitment has ended, they are removed.

All reminders are scheduled locally on your device. HabitStakes uses no remote push service and has no device push token, so a reminder can never be re-sent from a server.

Goal-at-risk reminders use the most recent fresh step total. If Health data arrives after the reminder was scheduled, the timing can look off. Opening the app refreshes the state and cancels reminders that no longer apply.

iOS decides when widgets refresh, and it budgets those refreshes. HabitStakes pre-schedules updates and asks for a reload when its state changes, but a deferred reload can still leave a widget behind. Open the app to see the current state; when a widget’s daily data has expired it says so and asks you to open HabitStakes to refresh.

When a Health refresh is missing, partial, stale, failed, or for a different commitment context, the app clears those external surfaces rather than republishing old totals with a fresh-looking timestamp. That is intentional: a blank widget is more honest than a confidently wrong one.

A Live Activity starts only inside the final at-risk window of a day, and iOS limits how long one can run. Check Settings › HabitStakes › Live Activities is enabled, and note that ending or completing the challenge ends the activity.

Widgets deep-link to the dashboard. If the app was cold-launched, give it a moment to load; if it still lands somewhere unexpected, tell us the widget size and what you saw.

No. The app works fully without an account. Sign in with Apple is optional and only stores a device-local identity in the Keychain; it does not sync anything to a server. Because iOS keeps Keychain items outside the app’s container, sign out in the app if you want that identity removed — deleting the app is not guaranteed to remove it.

On the old device, create a recovery export and save the file somewhere you control. Write down or store the recovery key shown — it is displayed once. On the new device, import the file and enter the key. If a commitment already exists there, the import asks you to confirm replacement, and completed history is merged rather than duplicated.

The file cannot be opened without it. The key is generated on your device, shown once, and never stored by the app or by us, so there is no reset, no backup copy, and no way for us to help. This is the trade-off for having no server that holds your data.

Imports fail closed on purpose. Common causes: the key does not match the file, the file was edited or truncated, it is larger than the accepted limit, or it was written by a newer app version. Re-export from the source device with the current app version if you still can.

Your Apple identity, your Health authorization state, raw Apple Health samples, and Health-derived step totals are all excluded. Restored history rows show zero steps to mark that number as unavailable rather than measured.

Trust & data › Export my local data writes a JSON file to Files. It includes commitments, completed challenge history, and activity records, including the day-level totals recorded for verification. It does not copy raw Apple Health records. Export is unavailable while demo data is loaded.

Trust & data › Delete all local data removes the active commitment, completed-challenge history, activity ledger, demo state, and the local Keychain identity, and clears cached Health totals held by the app. It asks for confirmation and cannot be undone.

It does not delete anything in Apple Health, and it cannot reach JSON or recovery files you already exported, or copies you sent elsewhere. Those remain yours to delete.

Delete your data inside the app first. Removing the app removes the records in its container — commitment, ledger, history, and settings — but iOS stores Keychain items outside that container, so an optional Sign in with Apple identity can survive the uninstall. Use Trust & data › Delete all local data, or Sign out, before deleting the app.

Uninstalling also does not reach anything else: an existing device or iCloud backup may still hold a copy until that backup is replaced or deleted, JSON exports and recovery files you saved stay where you put them, and Apple Health data is untouched.

No charge is possible in this release, so there is nothing to refund. See the Refund Policy, which also explains how to check your Apple purchase history if you see a charge you cannot place.

Nowhere. It is a record of a missed day, not a transfer. No money is held, moved, donated, or collected by anyone. See the money boundary in the Terms.