What leaves the device, and what doesn't.
Settings is also where Ovels's data philosophy shows up in practice: local-first storage, an opt-in-only analytics path, and a full backup you control.
Dashboard's step, sleep, and calorie-burn numbers come from the platform's own health store:
| Platform | Source |
|---|---|
| Android | Health Connect — Google's current health data platform, replacing the deprecated Google Fit APIs |
| iOS | Apple HealthKit |
Recent workouts logged in a different app can also be imported from health data rather than re-entered by hand.
A full backup captures every piece of durable user data — profile, meals, workouts, goals, streaks, photos, everything meant to persist. It deliberately leaves out purely transient state, like an in-progress rest timer or a one-time "have you seen this" prompt, since restoring those would just be confusing rather than useful.
By default, usage numbers live only on-device and are only ever read back by the app's own local "Usage Insights" screen — nothing is sent anywhere. If anonymous, aggregate analytics are enabled, only install and usage counters are sent, tied to an install ID rather than any personal identifier.
On-device AI means meal photos and coaching conversations can be processed entirely on the phone, without a network round trip, whenever the on-device model tier is active. See AI Models for the full roster.