You can use NourishNot without an account
NourishNot supports anonymous use. You do not have to protect your history with Google to use basic check-ins and tracking.
Anonymous history remains connected to the installation that created it. If that history was never protected, NourishNot may not be able to reconnect it after all local app state is lost through Clear Storage, uninstalling the app, resetting the device, or replacing the phone.
What Google protection does
Protecting your history with Google gives NourishNot a way to verify your connection to the same protected NourishNot history on another installation. Google verifies the account connection; your NourishNot history remains managed by NourishNot rather than being stored as Google app history.
Protection is optional. Basic NourishNot use does not require a Google connection.
Move to another device or clean installation
- Install and open NourishNot on the other device.
- Open Account and choose the Google history-protection option.
- Choose the same Google identity that protects your existing NourishNot history.
- Allow NourishNot to check for protected history and follow any restore confirmation shown.
- Keep a reliable network connection while synchronization and restoration finish.
If the account is connected without a merge prompt, supported protected history can still require a short period to synchronize and refresh across screens.
If the new installation already has activity
If the current installation has its own NourishNot activity and the Google identity is already connected to protected history, you may see “We found your NourishNot history.”
- Cancel leaves the current installation’s local history and account state unchanged.
- Restore my history reconnects the installation to the protected NourishNot history and adds appropriate current activity so the histories stay together.
- The existing protected history is retained rather than simply being replaced by the new installation.
After a successful restore, the installation adopts the protected history and future activity is recorded with it. Other already-connected devices can remain connected separately.
Restoration may take a little time
Larger histories may need synchronization and reconstruction before every screen is current. While restoration is in progress:
- Keep the app open if it asks you to wait.
- Maintain a network connection.
- Avoid repeated rapid sign-in attempts or repeatedly restarting the process.
What can be restored
Current restoration supports user-level history including Sleep, Daily Mood, hunger and craving activity, Water Break totals, activity context, Mindful Moment history or state, Awards, the history used to recalculate Mindful Days, and the beginning of the protected history period.
Existing legitimate information already on the installation is preserved where the restore process can safely combine it.
Some older details may not match exactly
Some older history may be rebuilt from daily summaries. This means useful totals can be restored even when the exact time or context of an older individual check-in is no longer available.
Original times, precise historical location attached to an individual event, and some legacy details may therefore differ from—or be less detailed than—the original device. This can affect older hourly, time-of-day, weekday, or location views without meaning that the overall restore failed.
If history does not appear
- Confirm that the device has a working network connection.
- Confirm that you selected the same Google identity used to protect the history.
- Check whether restoration is still in progress before trying again.
- If restoration completed but a screen has not refreshed, close and reopen NourishNot once.
- Confirm that history protection was enabled before access to the original installation was lost.
Signing out is not deletion
Signing out disconnects NourishNot from the protected account on that device. The account and protected history remain saved so you can sign in again. Data deletion is a separate action and should not be inferred from signing out.