Legal review required
Privacy Policy
Testing policy for the current PWA. Review with counsel before public launch.
Local-first storage
Jompa stores your profile, program, workout and body logs, measurements, nutrition, achievements, and pending sync changes in this browser. Workouts remain usable offline.
Optional Google account
Google sign-in and cloud sync are not enabled in the current public PWA, so your current use stays on this device. If account sync is introduced later, Jompa will explain what leaves the device and ask before moving any local data.
Cloud backup and isolation
The codebase includes an optional account-sync foundation, but it is disabled in the live public PWA. Jompa will not enable it for users until the storage, encryption, recovery, and consent model is finalized.
Device-only workout check-ins
End-of-workout feeling, note, and photo check-ins stay in this browser and are excluded from cloud snapshots. A local JSON export can include them so you can make your own backup.
Health data
The native wrapper can read steps, active calories, and weight from Apple Health or Health Connect only after permission. The PWA does not request those native permissions.
Optional reminders
Jompa asks for notification permission only after you choose reminder types and times. To deliver Web Push, the server stores the browser push endpoint and delivery keys, locale, time zone, reminder schedule, and a short-lived weekly-eligibility expiry. It does not receive the workout, exercise, body, meal, calorie, injury, or health details behind a reminder. Browser push providers such as Apple, Google, or Mozilla transport the notification. You can edit or turn reminders off in Settings.
Export and deletion
Settings can export local JSON, remove local device data, log out without deleting the preserved account database, or permanently delete the signed-in cloud account and its server snapshot.