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
If you choose Google sign-in, Google provides a stable account identifier, verified email, display name, and optional profile image. Jompa verifies the sign-in on its server and never stores the Google credential in browser storage.
Cloud backup and isolation
Signed-in testers can sync an encrypted-transport account snapshot to Jompa's Postgres database. Every snapshot is owned by the authenticated server account; one tester cannot request another tester's data. On first sign-in, existing guest data moves into that account and the guest workspace is cleared after the server confirms the backup.
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.
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.