Understand the boundary of local erasure

Know the data boundary

The in-app erase action targets local sessions, journal, and settings. It does not know every location where you may have saved or shared an exported copy.

Use the supported file workflow

If you want to remove those copies, review the folders, devices, or services you chose during export. Manage each through its own controls and access rules.

The importer expects a version-1 Fastly JSON object and rejects files larger than 10 MB. Record validation checks dates, goal values, note length, optional weight, and the distinction between running and completed records.

Check the copy you actually have

A backup stored elsewhere can still restore the old ledger after the app's local data is erased. That is useful for recovery but also explains why erase does not mean every copy disappeared.

Manage each retained copy

Keep the goal of the action clear: resetting this device and removing all retained copies are different scopes of work.

There is no account or automatic custom-server backup in this release. The privacy text also states that the app's private local storage is excluded from automatic cloud device backups; exported files are your separately chosen copies.

A worked walkthrough

Imagine exporting a backup to a chosen folder and later using Erase local data in Fastly. The local ledger and supported preferences are removed from the app, but the folder still has the older JSON file. Importing that file could bring the earlier data back. If your purpose was resetting the app while retaining a recovery path, that separation is helpful. If your purpose was removing every copy you control, the in-app action is only part of the work. Locate the exported file and manage it through the destination's controls, along with any other deliberate copies. A previously shared recipient may have its own retained version too. Do not interpret an empty History screen as proof that all exported information disappeared. Always match the removal action's scope to the location where the relevant data actually exists.