Last updated: 2026-11-12
One Push is built around a simple idea: your reps should be provable without anyone having to watch you do them. This policy explains, in plain language, what we collect, why we collect it, and what you can do about it.
Account information. When you sign in, we store the email address you sign in with. If you sign in with Apple or Google where we offer it, we get that address from them. You then choose a username and a display name, and you can add an optional profile photo. That's the whole identity record.
Workout data. Every set you complete adds to your history: reps, sets, scores, streaks, XP, which exercise you did, when you did it, and whether the rep counter stamped the set as verified. This is the data that powers your stats, your streak, and your standing on the leaderboard.
Your body measure. The camera measures a few proportions of your body once, so the rep counter can judge your depth against your own build rather than a fixed number. We store those proportions with your account, along with the height and weight you enter yourself if you choose to. This is a handful of numbers, not a picture.
How the counter judged each set. For every set, we store a short record of what the counter saw: how many reps it counted, how many it refused and why, and the joint angles and ratios behind those calls. We use it to check the counter's decisions and to make it fairer. It is a table of numbers about your movement, never an image or a clip.
Social data. If you take part in rivalries, duels, friend races, crews or league play, we store the standings, scores, membership and history that come out of that — who you're rivals or friends with, which crews you're in and when you last logged a set for them, duel results, league placements, and any reports or blocks you or another player file.
We do not collect your location, your contacts, or any data unrelated to running the app's features.
One Push uses your camera to count and verify your reps. That processing — pose detection through MediaPipe BlazePose and Apple's Vision framework — happens entirely on your device, in real time, as you work out. Your video frames are never uploaded anywhere, never stored, and never retained after your set ends. We don't have a server that receives your camera feed, because there isn't one. What leaves your phone is the result — the counts, the score, your body measure and the numbers behind each rep decision described above — not the footage that produced it. The one exception is the closed beta program described below, which you join on a screen of its own and can leave at any time.
This section applies only to the closed beta. The test builds of One Push we hand out by invitation through TestFlight ask you, on a screen of their own, to join the beta program before you use them. If you join, and only then, the app sends us more than the numbers described above, so we can make the rep counter work on bodies and rooms that aren't ours.
What is sent. Whenever the camera is on — during a set, a battle, a coached run or the measuring step, including the ones you stop or that don't count — the app keeps the joint positions the pose detector found in each frame, and up to five small still frames a second. Before a frame is kept, it is shrunk to a small size and everything above your shoulders is blacked out, so pictures of your face never leave your phone. A frame where the app can't find your shoulders isn't kept at all. With them goes a short note about the session: what it was, the exercise, the counts, how it ended, how long it took, the app version, your phone model and iOS version, and whether you told us the count was wrong. Nothing is recorded while the camera is off.
Why. To check and improve how the counter judges reps: finding where it gets a rep wrong, building and testing the rules and models that do the judging, and measuring whether a change makes it better. That includes using these captures to train and evaluate those models. We don't use them to identify you, we don't sell them, and we don't share them for anyone else's purposes.
Where and how long. The captures go to a private storage area in our Supabase project that only we can read. No other player can see them, and there is no public link to them. We keep them while the beta runs. If you leave the beta (Settings → Beta program → Leave the beta), recording stops at once and what was already sent is deleted within a day. Deleting your account deletes them too.
The App Store version is different. In the version of One Push on the App Store, none of this happens unless you choose it: the app asks first, and the answer is off until you say yes. Without that yes, everything in "Camera processing stays on your device" holds exactly as written.
Your account and workout data are stored with Supabase, our backend provider, on servers we configure and control. That data exists for one reason: to run the features of the app you're using — your profile, your history, your streak, your standings, and the social features you opt into. We don't sell it, rent it, or hand it to data brokers.
Purchases. If you subscribe to One Push Pro, the purchase itself is handled by Apple through the App Store; we never see your card or payment details. RevenueCat, our subscription-processing provider, handles the receipt for us: it receives your One Push account id (not your name or email), the purchase and transaction records Apple issues, and basic app and device details such as the app version and iOS version. It never receives your name, your reps or anything from your camera. We store whether your account is Pro, and until when, with your account, so your subscription works on every device you sign in on. RevenueCat's own privacy policy is at revenuecat.com/privacy.
One Push has no advertising SDKs, no third-party analytics trackers, and no data-sale relationships of any kind. We don't build a profile of you to sell to advertisers, because we're not in that business.
You're in charge of your information:
One Push is not directed at children under 13, and we don't knowingly collect information from anyone under that age. If you believe a child has created an account, contact us and we'll remove it.
We may update this policy as the app changes. If we make a change that materially affects how we handle your data, we'll let you know inside the app before it takes effect. The "Last updated" date at the top always reflects the current version.
Questions about this policy or your data? Reach us at onepush.support@gmail.com. One Push is operated by DropWave Supply LLC, a Minnesota limited liability company, which is responsible for the data described here.