Privacy policy

RIRVana is a lift coach. It tracks a set through your camera, counts reps, estimates how many you had left, and writes the next set from that. Almost everything it needs stays on your phone. This is the complete list of what reaches us.

• Account. You can use the app anonymously, in which case we hold only a random account id. If you sign in with Apple, Google, or an email link, we store the email address and display name the provider gives us, and the provider’s account id. Apple lets you hide your address; we then hold the relay address Apple creates. We never see a password.
• Sessions. A sign-in token, the IP address and the device’s user agent string at the time of sign-in, kept so a session can be revoked.
• Training data. Your programs, workouts, exercises, sets, loads, reps, and the numbers the camera derives from a set (rep count, tempo, range of motion, an effort estimate, and form flags). Body weight and body fat percentage when you log them, and body weight when you sync it from Apple Health. Training restrictions you declare. Equipment you say you have.
• Diagnostics. Short, anonymous failure reports, described below. Nothing else is collected automatically.

On this website, the waitlist form collects an email address and the training focus you pick. That is all the site collects. There is no analytics script on it.

To run the app: to keep your training history across devices, to generate and adapt your program, and to produce coaching feedback on a set. To sign you in and keep your account secure. To find and fix failures in the app.

We do not sell any of it. We do not use it for advertising. We do not track you across other apps or websites, and the app declares this to Apple in its privacy manifest. We do not build profiles of you for anyone else.

Pose tracking runs entirely on your phone. The camera frames are read by an on-device model, and only the geometry it derives (joint angles, timing, and a rep count) is used. No video and no camera frame is ever uploaded to us or to any third party.

When you record a set, the clip is saved in the app’s own storage on your phone and, if you allow it, exported to your Photos library. It stays there until you delete the set or the app. Deleting a workout from history deletes its clips.

Two optional, off-by-default settings send more detail about tracking, and only if you turn them on:

• Remote pose diagnostics sends a summary of a tracked set: frame counts, angle ranges, and how many rep attempts were rejected and why. No pixels, no coordinates.
• Upload calibration bundles sends, for a set you explicitly confirm, the per-frame joint positions the model found, as normalised coordinates, with the rep count you verified. This helps us tune the rep counter. It contains no images, but body geometry can be personal, so we treat every bundle as yours and delete it with your account.

If you connect Apple Health, the app reads steps, active energy, walking and running distance, resting heart rate, heart rate variability, sleep, and body mass, to show them alongside your training. These readings are displayed on your phone. Of them, only body weight is sent to our server, where it becomes a measurement in your history.

Health data is used only to provide the app’s features. It is never used for advertising or marketing, never sold, never shared with data brokers, and never disclosed to a third party except as this policy describes. The app does not write to Apple Health.

Two features call a large language model, and for both the model is run by OpenAI, acting as our processor. Each request contains only what the feature needs.

• Set feedback sends the numbers from one set: the exercise, reps, duration, tempo per rep, range of motion, any form flags, the load, and your recent sets of the same exercise for context.
• Program generation sends your training goal, days per week, session length, experience level, focus lifts, equipment, declared restrictions, and a summary of your recent training.

No name, email address, account id, video, or health reading other than what is listed above is included. OpenAI processes these requests under its API data policy, which does not use API inputs to train its models.

Your training data is kept for as long as you have an account, so your history is there when you come back.

You can delete your account from inside the app: Profile, then Delete Account. This permanently removes your account and every row we hold for it, including workouts, programs, measurements, calibration bundles, and settings. Data on your phone (recorded clips, the local database) is removed when you delete the app.

You can also write to support@rirvana.app to ask for deletion, a copy of your data, or a correction.

We use a small number of providers to run the service, each only for the purpose named:

• Railway hosts the API and the database, in the United States.
• OpenAI processes the AI requests described above.
• Resend delivers sign-in emails.
• Apple and Google handle sign-in if you choose them.

We do not share your data with anyone else, unless the law requires it.

When something in the app fails, it can send us a report. A report is one of six named events (for example, “set video save failed”), the platform, the app and build version, a named step of the operation that failed (for example, “saving to the phone’s index”), and short codes describing the error and, when one failure wrapped another, its underlying cause. It can also say which app build is installed, which runtime it uses, and whether the app is running its built-in code or an update it downloaded, so we can tell which version broke. Before any of those codes leave the phone, every file path, URL, and long identifier is stripped from them and each is cut to 64 characters. Reports carry no workout data, no video, and no personal information, and they are not tied to your account when we read them.

You can turn them off in Profile with the “Share error reports” switch.

RIRVana is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has created an account, write to us and we will delete it.

Data travels between the app and our server over TLS. Sign-in uses short-lived codes or the platform’s own identity service; we store no passwords. Access to the database is limited to the developer. No system is perfectly secure, and if we learn of a breach affecting your data we will tell you.

When the app starts collecting something new, or stops, this page changes and the date at the top moves. Material changes are announced in the app before they take effect.

RIRVana is made by Derek Rodriguez. Questions about this policy or your data go to support@rirvana.app.