← Back to Rapsy

Rapsy Privacy Policy

App: Rapsy
Developer: Adarsh Kumar Verma
Privacy contact: avwithai.port@gmail.com
Last updated: May 2, 2026

1. Overview

This Privacy Policy explains how Rapsy accesses, collects, uses, shares, retains, and deletes user data. Rapsy is an AI-powered fitness tracking app that uses on-device camera pose detection, Firebase account services, saved workout history, and Google Play subscriptions.

Rapsy does not sell personal or sensitive user data. Rapsy does not show ads, use advertising tracking, use analytics SDKs, use Crashlytics, collect location, collect contacts, use health-record APIs, or upload camera images or videos to Rapsy servers.

2. Data We Access or Collect

Account and profile data

Data: Name, email address, Firebase user ID, sign-in provider, and profile photo URL when provided through Google Sign-In or Firebase Authentication.

Use: Create and secure your Rapsy account, keep you signed in, and sync your workout history across devices.

Retention: Kept while your account is active. Deleted from active Rapsy systems within 7 to 14 days after a verified account deletion request.

Workout and fitness activity data

Data: Workout dates, selected exercises, reps, sets, duration, estimated calories, weight entries, and progress history that you choose to save in the app.

Use: Show your workout history, progress, and app features that depend on saved training data.

Retention: Kept while your account is active. Deleted within 7 to 14 days after account deletion or a verified request to delete workout history.

Camera permission and pose data

Data: Rapsy accesses your device camera during workout tracking so on-device ML Kit pose detection can identify body points in real time.

Use: Count reps, analyze exercise form, and provide real-time workout feedback.

Retention: Camera frames, images, videos, and raw camera feeds are not uploaded, saved, or retained by Rapsy.

Subscription and purchase status

Data: Subscription tier, entitlement status, purchase identifiers, and related transaction metadata from Google Play and RevenueCat. Rapsy does not collect or store credit card numbers.

Use: Provide paid features, restore purchases, prevent abuse, and handle subscription support.

Retention: Kept while needed to provide subscriptions and support. Google Play and RevenueCat may retain transaction records as required for tax, accounting, fraud prevention, and legal compliance.

Support and deletion request emails

Data: Email address, request details, and messages you send to the developer.

Use: Respond to support requests, verify deletion requests, and keep a record of completed requests.

Retention: Normally kept for up to 90 days after the request is resolved unless a longer period is required for legal, security, or dispute reasons.

3. How We Use Data

  • To provide account sign-in, authentication, and account security.
  • To save and display workout history, progress, subscription access, and app settings.
  • To run on-device pose detection during workouts and provide rep counting or form feedback.
  • To respond to support, account deletion, and data deletion requests.
  • To comply with legal obligations, enforce terms, prevent fraud, and protect users and the app.

4. Third-Party Services and Sharing

Rapsy shares user data only with service providers needed to operate the app, process subscriptions, support sign-in, or comply with legal obligations. These providers process data under their own security and privacy terms.

Firebase Authentication and Firebase services

Authentication, account security, and storage or sync of account and workout data.

Google Sign-In

Optional sign-in provider for creating and accessing your Rapsy account.

Google Play Billing

Subscription purchase processing, renewal status, cancellation handling, and payment compliance.

RevenueCat

Subscription entitlement management and purchase restoration.

Google ML Kit

On-device pose detection. Camera frames are processed locally on your device and are not sent to Rapsy servers.

5. Camera and On-Device Processing

Rapsy requests camera access only when you use workout tracking features that need pose detection. Camera frames are processed locally on your device using ML Kit. Rapsy does not transmit, save, upload, or share your camera feed, photos, or videos.

6. Security

Rapsy uses Firebase and Google Play services that transmit data over secure connections. Access to account and workout data is limited to app functionality, user support, security, and compliance needs. No method of transmission or storage is perfect, but Rapsy uses reasonable safeguards for the type of data handled by the app.

7. Data Retention and Deletion

Rapsy keeps account and workout data while your account is active so the app can provide its core features. When you delete your account in the app or send a verified deletion request, Rapsy deletes your Firebase Authentication profile and saved Rapsy workout data from active systems within 7 to 14 days.

Some limited records may be retained longer when required for legitimate reasons such as security, fraud prevention, billing disputes, tax, accounting, legal compliance, or proof that a deletion request was completed. Google Play, RevenueCat, Firebase, and email providers may also retain data under their own required retention schedules.

To request deletion from outside the app, visit the Rapsy Account and Data Deletion page or email avwithai.port@gmail.com with the subject line Rapsy Data Deletion Request.

8. Your Choices

  • You can delete your Rapsy account in the app from the Profile or Settings area.
  • You can request account or workout data deletion by email if you no longer have access to the app.
  • You can cancel or manage subscriptions through your Google Play account settings.
  • You can deny camera permission, but workout tracking features that require pose detection will not work without it.

9. Children

Rapsy is not directed to children under 13. If you believe a child has provided personal data to Rapsy, contact the developer so the data can be reviewed and deleted where appropriate.

10. Changes and Contact

This Privacy Policy may be updated from time to time. Updates will be posted on this page with a revised last updated date.

For privacy questions, support, or deletion requests, contact:
Adarsh Kumar Verma
Email: avwithai.port@gmail.com

a² + b² = c²Pythagoras