Where Does Lose It Store Nutrition Data?
Lose It keeps nutrition server-side with web ZIP exports of CSVs. No meaningful local files exist on either mobile OS.
Last updated
Lose It centralizes nutrition server-side with web exports as the exit. ZIP bundles carry CSVs per data type with week and goal narrowings. Imports never return.
Packages verify on both stores while local storage stays cache. Barcode databases live remotely with API integrations beside. Quote IDs and flows while marking local files absent.
Where Lose It! stores this, by platform
/data/data/com.fitnow.loseit
Private sandbox for the verified package with cache-only contents. Web ZIP exports carry CSVs per type. No local database to quote.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container for the verified store ID with identical cloud model. Per-week exports narrow scope without imports. Same no-local-files story.
Frequently asked questions
How do I export Lose It data?
Use the website export data flow for the ZIP of CSVs covering foods, exercise, weight and steps. Per-week and per-goal exports narrow the scope. Imports never return, so treat exports as analysis copies.
What are the Lose It app IDs?
Through verified packages and store IDs on both platforms with cache-only contents. Barcode databases live server-side with tens of millions of items. Integrations sync devices through APIs instead.
Does Lose It work without an account?
Account-based throughout with anonymous limits and deletion flows. Privacy policies place servers centrally with device data syncing up. Quote IDs and export flows, never local databases.
Notice an outdated path? Let us know.