resetReset does not require a Reset account. You do not create a profile, choose a password or provide an email address to use its timer. The record is stored in the app’s local data on your Android device.
That can make setup simpler, but it changes how recovery works.
A store account is a separate thing
Google Play handles the purchase and installation. Using Google Play is not the same as creating an account inside Reset.
The store can keep a record of your purchase while Reset keeps fasting sessions locally. Access to one does not establish that the other has been backed up. Reinstalling the app and recovering its history are separate tasks.
No password means no password recovery
There is no Reset login to reset and no developer dashboard containing your fasting sessions. Support cannot look up your history by email or synchronise it onto a new phone.
Android’s backup system may restore app data depending on the device and settings. That possibility should not be mistaken for a guaranteed Reset cloud service.
Consider the tradeoff before switching devices
A local approach may suit a person who wants a record on one phone. Someone who requires automatic access across several devices needs to check whether a different product supports that requirement.
Before replacing or resetting your phone, read moving your fasting history. Keep the old device intact until you have checked what actually restored.
What support can still do
Support can explain controls, investigate reproducible problems and clarify app behaviour. Include the app version and device model in a report, but avoid unnecessary medical information or payment details.
The absence of an account reduces what the developer holds; it also limits what the developer can retrieve. Our privacy policy and offline storage guide explain that boundary in more detail.