Effective Date: August 24, 2026 Last Updated: October 23, 2026 — applies to version 6.4.0 and later Application: Push Up Pro (com.jverse.pushup) Developer / Controller: J VERSE (Chaitanya Ajay Vora) — jaiminadac@gmail.com
Push Up Pro is a camera-based push-up counter. This policy states exactly what the app collects, what stays on your phone, what reaches our servers, who else can see it, and how to have it removed.
1. Camera Usage & On-Device Vision (Zero Image Upload)
Push Up Pro uses the device camera — the front camera by default, with a switch to the rear camera on the workout screen — solely to perform real-time push-up rep counting, depth analysis and form feedback using Google ML Kit Pose Detection, which runs entirely on your device.
Important: all computer-vision processing happens 100% locally. We never record, stream, capture, store, or transmit your camera video feed or still images to any server or third party. The app writes no video file, holds no image in storage, and uploads only numeric results you generate (rep count, duration, mode, form score).
The app does not request the microphone, contacts, call log, SMS, calendar, photos or audio files, and it holds no location permission at all — neither precise nor approximate, in foreground or background.
2. What We Collect
a) Stored on your device only (used by everyone, including Guest mode):
Workout records — reps, duration, exercise mode, form score and timestamps, in a local Room (SQLite) database.
Preferences and progress — sound and haptics switch, sensitivity preset, chosen program, streak counter, XP and level, badges, and a display copy of your coin balance, in app-private DataStore. The coin balance you see is only a mirror: the real number is kept on our servers (see below).
Purchase entitlements — flags recording that you bought "Remove Ads" or subscribe to Pro, kept in EncryptedSharedPreferences.
In Guest mode nothing from this list is uploaded; it stays on the phone until you delete it, clear app data, or sign in.
b) Sent to our backend — only when you sign in with Google:
Account identifier — the Firebase Authentication user id for your Google sign-in, plus your chosen display name and, if you set one, a profile photo URL or avatar colour. We do not store your email address or any password in our database; your Google account is held by Firebase Authentication and is used only to sign you in and to let you verify a deletion request.
Fitness aggregates — total reps, best single set, streak length, per-day totals, and one summary row per submitted session, so leaderboards and challenges are computed on the server instead of trusting the phone.
Competition records — clan membership, challenge contributions, race (duel) rows with your participant id, scores, result and rating, and races won or lost.
Activity marker — a last-active timestamp used to detect stale sessions and to protect matchmaking.
Coin ledger — your balance and one row per coin earned or spent (a completed rewarded ad, a logged workout, a race entry, founding or joining a squad), with your user id and a timestamp. Coins are earned only, never bought, and the ledger exists so the server — not the phone — decides what you can spend.
Reward session records — when you choose to watch a rewarded ad, our server issues a one-time code for that single view and stores when it was issued and whether it was redeemed, so coins are paid only for ads actually finished and the daily limit stays honest. It holds no advertising identifier and no ad content.
c) Diagnostics, analytics and advertising:
Firebase Crashlytics — crash reports containing the stack trace, device model, OS version, app version and the Firebase Installation identifier, so we can fix faults.
Firebase Analytics — app lifecycle and feature-usage events with the same device and app identifiers. No camera content, no workout values.
Google AdMob with UMP consent — when you consent, the Google Advertising ID is used to serve and measure ads, together with coarse device info and the ad request's IP address. Declining consent switches the app to non-personalised ads; an ad-free purchase removes ads. Consent can be withdrawn at any time through the app's privacy dialog or Google's "My Ad Center".
Server logs — Supabase and Google infrastructure record request metadata (IP address, user agent, timestamp) needed to run, secure and rate-limit the service.
3. Permissions We Request and Why
Camera — rep counting and form analysis, on-device only.
Internet & network state — sign-in, leaderboards, races, ads, sync.
Post notifications — the two reminders you turn on yourself: the daily streak nudge and a new personal record. Both are raised locally; the app has no push-notification service.
Vibrate — haptic feedback on completed reps.
Google Play Billing — purchases and subscription restore.
Run at startup — restores the streak reminder you scheduled.
Advertising ID — ads only, and only under your UMP consent.
4. Who Else Can See Your Data
Signed-in athletes are published, and that is the point of the app: your display name, avatar, rep totals, rank, streak and clan membership appear on the daily, weekly and all-time leaderboards, on your public profile, on clan boards, and in the 1 Million Pushup Challenge contributor list. During a live 1v1 race your name and running rep count are streamed to your opponent's device over an encrypted realtime channel for the length of the race. Do not choose a display name or clan details you would not want other athletes to read.
5. Third-Party Services
Google ML Kit (Google LLC) — on-device pose model. Pose analysis sends nothing to Google; the model binary is delivered through Google Play.
Firebase Authentication, Analytics, Crashlytics (Google LLC) — sign-in and diagnostics, under Google's Privacy Policy.
Google Play Billing (Google LLC) — payments; card details are handled by Google Play and never reach us.
Supabase — hosts the database rows listed in §2(b) and relays live race messages.
Coil and ZXing — image loading and QR joining, both on-device, with no network calls of their own.
We do not sell, rent or trade your personal data, and we do not share it with advertisers or data brokers.
6. Where Your Data Is Stored and How It Is Protected
Your cloud rows live in a Supabase-hosted PostgreSQL database in the ap-south-1 (Mumbai, India) region; Firebase and AdMob data are processed on Google's infrastructure under Google's own terms.
Every network call leaves the app over HTTPS/TLS; the app forbids cleartext traffic and checks its own signing fingerprint against tampered installs.
Android cloud backup and device-to-device transfer are disabled for this app, so your workout history is not copied into a Google One backup.
The app cannot read or write any database table directly. It may call six public read functions anonymously, and every write goes through our gateway function, which verifies your Firebase ID token before talking to the database with a service-only role.
Database functions recompute totals, streaks and race results server-side and reject implausible submissions (rep caps, minimum cadence, cooldowns, duplicate and backdated sessions, identity mismatch).
Access to production data is limited to the developer and the service roles the app requires.
7. Retention
On the phone: until you delete a session, uninstall, or clear app data — and the app's own maintenance job prunes synced history older than 180 days.
In the cloud: until you delete your account. Deletion purges your profile, aggregates, session rows, clan membership, challenge contributions and notification records immediately. A completed race that involved another athlete is kept with your participant id anonymised, so your opponent's match history stays coherent; no fitness numbers of yours remain attached to it.
Crash and analytics data: retained by Google under its own defaults (Crashlytics reports roughly 90 days) and deletable on request.
Purchase records: kept by Google Play; we retain only what tax and platform rules require.
8. Your Privacy Rights (GDPR, India DPDP Act 2023, CCPA)
Access & portability — use Settings → Export My Data in the app for a shareable summary of your sessions, totals and streaks, or email us for the raw synced rows in machine-readable form.
Rectification — change your display name, avatar and preferences any time in the app.
Erasure — delete your account and data in-app, through the web portal, or by email (see §9).
Withdraw consent — turn off personalised ads in the app's privacy dialog or in Google's "My Ad Center"; stop analytics by removing the app.
Object, complain, or request a copy — write to us first; you may also complain to your local supervisory authority (in India, the Data Protection Board constituted under the DPDP Act).
No sale of personal data — we have never sold or shared personal information for commercial consideration, so there is nothing to opt out of under CCPA/CPRA.
We act on requests within 30 days and never charge for them.
9. Account & Data Deletion (Google Play Compliance)
There is always an accessible path to permanently delete your account and data:
In-app (instant): open Push Up Pro → Settings → "Delete Account & Data" → confirm. Your cloud profile, workout history, leaderboard and challenge records, clan membership and open races are purged, the local database is wiped, and you are signed out.
Guest mode needs no request: your data was never uploaded. Uninstalling, or clearing app data in Android Settings, removes it from the phone.
10. Children
Push Up Pro is built for a general audience and is not directed at children under 13 (under 16 in some European jurisdictions). We do not knowingly collect personal information from children and do not use age-inappropriate ad targeting. The app has no age-verification step, so a parent or school using it with a child should manage the Google Play account, ad personalisation and camera permission on that device. If you believe a child has given us personal data, tell us and we will delete it.
11. Changes to This Policy
When this policy changes materially we update the "Last Updated" date above and republish it at https://pushup-pro-oath.web.app/privacy and in the Play Store listing. Using the app after that date means you accept the updated policy.