Repp
ES/ENDownload

Privacy Policy

Last updated: October 4, 2026

At Repp ("we", "us", "our" or "the app") we respect your privacy and are committed to protecting it. This Privacy Policy describes what information we collect when you use the Repp mobile application and related services (collectively, the "Service"), how we use it, who we share it with, and the rights you have over it.

By creating an account or using the Service you accept the practices described in this Policy. If you do not agree, please do not use the app.

What changed on October 4, 2026: we now run ads for Repp on Facebook and Instagram, and we use AppsFlyer and Meta to measure which ads bring people to the app, improve who they are shown to and build audiences. The previous version of this Policy said we did not use your data for targeted advertising; that is no longer the case. The details, and how to limit that use, are in section 8.

1. Information we collect

1.1 Account information

When you create an account we may collect your name, email address, password (stored encrypted) and, optionally, a profile picture and date of birth.

1.2 Profile and preferences information

To personalize your experience, we store the data you provide, such as your goal (lose fat, build muscle, maintain), experience level, available equipment, training days per week, body weight, height and other optional metrics. Weight, height and other body metrics may be considered health-related data: we use them to personalize your experience and to understand internally how the app is used, and we do not share them for advertising.

1.3 Training data

We collect the information you generate by using the Service, including:

  • Created routines, templates and selected exercises.
  • Sets, reps, weight lifted and duration of each workout.
  • Session history, streak, weekly check-ins and personal notes.
  • Configured rest times and timer usage.

1.4 Technical and usage information

We automatically collect information about your device (model, operating system, language), unique install identifiers, device and advertising identifiers, IP address, crash logs and usage events (screens visited, features used) to maintain and improve the Service. The device and advertising identifiers are: on iOS, the IDFV (a code Apple assigns to Repp on your iPhone, different for each company) and, only if you allow it in Apple's prompt asking whether Repp may track your activity (App Tracking Transparency), the IDFA (your iPhone's advertising identifier); on Android, Google's advertising ID. Those identifiers, your IP address and some app events (not crash logs or the screens you visit) are also used to measure and improve our ads, as explained in section 8.

2. How we use your information

We use the collected information to:

  • Provide, operate and maintain the Service.
  • Personalize your routines, recommendations and statistics.
  • Sync your data across devices when you sign in.
  • Manage your subscription.
  • Measure and improve our ads on other platforms, such as Facebook and Instagram: know which ad or link brought each install, measure campaign results, improve who they are shown to and build audiences (for example, to avoid showing them to people who already installed Repp) (see section 8).
  • Know which creator's link brought you to Repp so we can pay them their commission.
  • Diagnose technical issues, prevent fraud and improve stability.
  • Communicate with you about changes, updates or support.
  • Comply with applicable legal obligations.

3. Legal basis for processing

We process your personal data based on (a) the performance of the contract you accept when using the Service; (b) your consent or authorization: by creating an account or using the Service you accept this Policy, including the use of your device identifiers and certain app events to measure and improve our ads with AppsFlyer and Meta (section 8); on iOS, access to the IDFA additionally requires the permission you give in the App Tracking Transparency prompt. You can withdraw your consent or limit that use at any time (see sections 7 and 8.4); (c) our legitimate interest in maintaining and improving the app; and (d) compliance with legal obligations that apply to us. We process your data in accordance with Colombia's personal data protection law (Law 1581 of 2012) and other applicable rules. Who the data controller is can be found in section 12.

4. How we share your information

We do not sell your personal data: no one pays us for it. We do share it in the following cases, including the advertising partners described below:

  • Service providers that help us operate the app (cloud hosting, authentication and database, file storage, product analytics and error monitoring), under confidentiality and data processing agreements.
  • Subscriptions and payments: RevenueCat manages the subscriptions you buy in the app through Apple or Google. Your card details are processed by Apple and Google; Repp does not receive them.
  • Advertising and measurement partners: AppsFlyer, which measures which ads and links bring people to Repp, and Meta (Facebook and Instagram), where we run ads for Repp and which receives data only through AppsFlyer. They receive identifiers of your device and certain app and subscription events; AppsFlyer also receives your IP address and your Repp user identifier. They use them to measure our ads, decide who they are shown to and build audiences, and Meta also for its own purposes. They do not receive your email or your phone number. The details are in section 8.
  • Legal compliance: when required by law, court order or to protect our rights, yours or public safety.
  • Corporate transfers: in case of merger, acquisition or sale of assets, your data may be transferred to the successor, maintaining the protections of this Policy.
  • With your explicit consent, in any other case.

5. Storage and security

Your data is stored on servers managed by recognized industry providers. We apply reasonable technical and organizational measures to protect it against unauthorized access, loss or alteration, including encryption in transit (TLS) and at rest when possible.

No system is 100% secure. We recommend using a strong password and keeping your device up to date.

6. Data retention

We keep your information while your account is active or for as long as necessary to fulfill the purposes described in this Policy. When you delete your account, we will delete or anonymize the personal data we hold within a reasonable time, unless the law requires us to keep it. Data already received by AppsFlyer, Meta and RevenueCat is not deleted automatically when you delete your account: it is kept under their own policies. If you want us to ask them to delete the data associated with your device or your account, write to us at support@repp.community.

7. Your rights

Depending on your jurisdiction, you can exercise the following rights:

  • Access: request a copy of your personal data.
  • Rectification: correct inaccurate or outdated information.
  • Deletion: request the deletion of your account and associated data.
  • Portability: receive your data in a structured format.
  • Objection or restriction of processing in certain cases, including the use of your data for advertising.
  • Withdraw consent at any time.
  • Proof of authorization: request proof of the authorization you gave us.
  • File a complaint: if you are in Colombia, with the Superintendence of Industry and Commerce (SIC), after first submitting your claim to us.

To exercise these rights write to us at support@repp.community. We will respond within the applicable legal timeframes.

8. Third-party services and advertising

The app uses, among others, third-party services for authentication and database (Supabase), file storage, product analytics (PostHog), error monitoring (Sentry), push notifications (Expo, Apple and Google), sign-in with Google or Apple, the Strava integration if you choose to connect it, subscriptions (RevenueCat) and attribution, measurement and advertising (AppsFlyer and, through AppsFlyer, Meta). Providers process your data on our behalf, only receive what they need to perform their function and are subject to their own privacy policies. Meta, on the other hand, also uses the data it receives for its own purposes, as explained in section 8.2. The app does not include the Facebook SDK or the SDKs of other ad networks.

8.1 Ad attribution and measurement (AppsFlyer)

We use AppsFlyer to know which ad or link brought you to Repp. With that we measure and improve our ads and, when you install Repp from a link shared by a creator, we know which link brought you in so we can pay that person their commission. AppsFlyer receives:

  • The app install and each time you open it.
  • Identifiers of your device: the AppsFlyer ID; on iOS, the IDFV and, only if you accept it in the App Tracking Transparency prompt, the IDFA; on Android, Google's advertising ID.
  • Your IP address and technical data about the device and the app, such as model, operating system, language, network type and app version; on Android, also the Google Play install referrer (where the download came from).
  • Your Repp user identifier (an internal code, not your name or email), once you sign in.
  • One app event: sign-up completed, with the method you used (email, Google or Apple). We send nothing about your workouts.
  • Your subscription events (purchases, renewals, cancellations and refunds, with their amount), sent by RevenueCat (see section 8.3).
  • If you open a creator's link on your phone and don't have the app yet, your browser goes from link.repp.community to an AppsFlyer link, which receives your IP address, your browser data and the creator's code.

If on iOS you accept the App Tracking Transparency prompt, the IDFA is used to measure which ads and links bring people to Repp (with AppsFlyer and Meta) and to improve who we show Repp's ads to. We do not build device fingerprints (fingerprinting). For creator links, AppsFlyer may match the click with the install statistically, using data such as the IP address and device type. The click on a creator's link first happens on our own domain and is recorded on our own servers. We do not share your workouts, weight, height or other body metrics with AppsFlyer, Meta or RevenueCat. You can read AppsFlyer's privacy policy at appsflyer.com.

8.2 Advertising on Meta (Facebook and Instagram)

We run ads for Repp on Meta (Facebook and Instagram). The app does not include the Facebook SDK: Meta receives data from Repp only through AppsFlyer, via its Meta Ads integration, and it receives it for every install, including people who did not come from an ad (for example, from the store or from a creator's link). It receives the install, the completed sign-up and your purchases, together with identifiers of your device. It receives nothing about your workouts or your body. To attribute installs and build audiences, Meta matches those identifiers with your Facebook or Instagram account, if you have one. This data is used to:

  • Attribute which ad brought each install.
  • Measure the results of our campaigns.
  • Optimize who sees Repp's ads.
  • Build audiences; for example, to avoid showing Repp ads to people who already installed the app or to find people similar to those who already use it.

Meta does not act only on our behalf: it processes this data as an independent controller, under its own terms and privacy policy, and may also use it for its own purposes, such as providing measurement services and targeting and delivering ads. On iOS, if you did not accept the App Tracking Transparency prompt, AppsFlyer does not send Meta your events with identifiers of your device; Meta only receives the aggregated, anonymous campaign results reported by Apple (SKAdNetwork). We do not share your email or your phone number with Meta or with AppsFlyer, not even converted into an unreadable code (hashed). You can read Meta's privacy policy at facebook.com.

8.3 Subscriptions and payments (RevenueCat)

Repp subscriptions are bought inside the app through Apple (App Store) or Google (Google Play), and are managed by RevenueCat. Payment data, such as your card, is processed by Apple and Google; Repp does not receive it. RevenueCat knows your Repp user identifier and your purchase history, and also receives your device's AppsFlyer ID. With that it sends AppsFlyer the purchases, renewals, cancellations and refunds of your subscription, with their amount, and AppsFlyer forwards to Meta the purchase events we configure, which Meta uses as explained in section 8.2. You can read RevenueCat's privacy policy at revenuecat.com.

8.4 How to control the use of your data for advertising

These are your options:

  • On iOS: the app asks for your permission through Apple's prompt asking whether Repp may track your activity (App Tracking Transparency), and you can change your decision at any time in Settings > Privacy & Security > Tracking. If you decline, the IDFA is not accessed, Meta does not receive your events with identifiers of your device and the app works the same. AppsFlyer still receives the other data listed in section 8.1, and Apple may report aggregated, anonymous campaign results (SKAdNetwork).
  • On Android: the app does not show a separate permission prompt. You can delete or reset your advertising ID in the system Settings (Google > Ads or Privacy > Ads, depending on your device). If you delete it, it is no longer sent, but AppsFlyer still receives the other data listed in section 8.1.
  • On Facebook and Instagram: in Meta's Accounts Center (accountscenter.facebook.com), in your ad preferences, you can review and limit how Meta uses the information it receives from advertising partners like Repp to show you ads, and disconnect your activity off Meta technologies.
  • By email: the app does not yet have its own setting to stop sending this data; while it is installed, the only way to stop it completely is to uninstall it. If you want to object to this use, or want us to ask AppsFlyer and RevenueCat to delete the data associated with your device or your account, write to us at support@repp.community.

If you accepted the App Tracking Transparency prompt in a version of Repp released before October 4, 2026, that prompt said the permission was only used to know which link brought you in and not to show you ads. Starting with this version, the IDFA is also used to measure and improve Repp's ads with AppsFlyer and Meta. If you don't agree, you can withdraw the permission in Settings > Privacy & Security > Tracking > Repp; from then on we no longer access the IDFA.

9. Children's privacy

The Service is not directed to children under 13 (or the minimum age in your jurisdiction) and we do not knowingly collect their data. If you are between 13 and 17, you need the authorization of your parent or legal guardian to use Repp, and we process your data respecting your best interests, under Colombia's Law 1581 of 2012. If you believe a minor gave us information without that authorization, contact us to delete it.

10. International transfers

Your data may be processed in countries other than your own, where our providers operate (including Supabase, PostHog, Sentry, RevenueCat, AppsFlyer and Meta). When this happens, we apply appropriate safeguards, such as each provider's data processing agreements, to protect your information in accordance with applicable law.

11. Changes to this Policy

We may update this Policy to reflect changes in the Service or the law. We will publish the updated version on this page and, if the changes are material, we will notify within the app or by email. The "Last updated" date at the top indicates when the current version came into effect.

12. Contact

The data controller for your personal data is Edison Bedoya, in Colombia. If you have questions about this Privacy Policy, want to make an inquiry or a claim about your data, or exercise your rights, write to us at support@repp.community.