Privacy Policy

Overview

RepBite helps users plan workouts, run training sessions, set calorie and macro targets, log food, scan barcodes, estimate meals from photos, and generate AI-assisted fitness and nutrition plans.

This policy explains what information may be processed when you use RepBite, why it is used, and the choices you have. RepBite is not a medical service, and the information in the app is for general fitness and nutrition support only.

Information We Process

Depending on how you use the app, RepBite may process:

• Workout plans, exercise names, sets, reps, timers, training notes, and imported workout files or text.
• Nutrition targets, calories, macros, food log entries, meal names, barcode numbers, and meal preferences.
• Photos you choose to capture or select for meal estimation.
• Purchase status, entitlement identifiers, and pseudonymous app user identifiers used to unlock premium features.
• Pseudonymous analytics information such as app instance identifiers, app and device information, screen views, onboarding progress, paywall views, and feature milestones.
• Support requests you submit through the website, including your email address and message.
• Basic technical data such as device, app, request, and error information needed to keep the service reliable and secure.

RepBite stores workout and food log data primarily on your device unless you choose a feature that needs online processing, such as AI generation, barcode lookup, meal photo estimation, or purchase entitlement checks.

Analytics and Attribution

RepBite uses Firebase Analytics to understand whether onboarding, planning, workout, nutrition, and subscription flows are working. These events describe actions such as a plan being generated or a workout being completed. They do not include your workout prompt, exercise names, meal names, food photos, health measurements, calorie values, or other content you enter.

RevenueCat processes pseudonymous purchase and entitlement information to unlock premium features and measure subscription results. RepBite may provide RevenueCat with an pseudonymous Firebase app instance identifier. On iOS, Apple's AdServices attribution token may be used to measure results from Apple Ads. RepBite does not sell personal information and does not use the advertising identifier (IDFA) for this measurement.

Optional Advertising Measurement

App versions with Meta advertising measurement enabled ask for permission through Apple's App Tracking Transparency prompt before initializing Meta's SDK or collecting advertising identifiers. Refusing permission does not limit workout, nutrition, or subscription features.

If you allow tracking, RepBite may share advertising and device identifiers (including IDFA, IDFV, and Meta's anonymous app identifier), IP address and device information, and app usage events such as activation and session duration with Meta. RevenueCat may send subscription events, including trials, purchases, trial conversions, and renewals, together with product, subscription state, value, currency, and timestamps. This helps measure and improve RepBite advertising. We do not send Meta your workout plans, exercise or meal details, photos, prompts, health measurements, or food logs.

Subscription events can be sent by RevenueCat while the app is closed, based on the identifiers and consent information it has received. You can change tracking permission in iOS Settings. When RepBite next runs, it stops on-device advertising measurement if permission has been withdrawn and asks RevenueCat to clear advertising identifiers. That update needs a network connection and may be retried later; withdrawing permission does not instantly remove previously sent records or recall events already being processed.

In versions with this integration, the app's advertising privacy control explains the choice and opens the system prompt or iOS Settings. Firebase app analytics and subscription entitlement checks are separate from this optional Meta measurement.

Website Analytics and Purchase Measurement

Website analytics are optional and remain off unless you choose Allow analytics. When enabled, Google Analytics receives page views, App Store button clicks, general browser and device information, and recognized campaign labels. We do not send support messages, arbitrary URL parameters, or personal form content in these events. Advertising storage, advertising user data, and advertising personalization remain disabled.

Use Analytics preferences in the footer to withdraw or change your choice. We store that choice in your browser. Recognized campaign labels can stay in links as you browse and continue to the App Store, even if you decline website analytics. These links support aggregate campaign reporting, not a person-level link between your website visit and a purchase.

RevenueCat sends verified subscription lifecycle events to a private purchase ledger, including product, store, currency, amounts, subscription state, timestamps, and hashed customer and transaction identifiers. This lets us separate trials, paid purchases, renewals, and refunds. Test and sandbox events are excluded from production revenue. These records support subscription measurement and reconciliation; they do not include workout or nutrition content.

AI and Service Providers

Some RepBite features send the content you provide to backend services so the requested result can be generated. This can include workout requests, meal planning details, food photos, and imported plan text. RepBite may use service providers including Firebase and Google Cloud for hosting and backend infrastructure, OpenAI for AI-assisted generation and photo estimation, RevenueCat for subscription entitlement management, Apple for App Store purchases, Meta for the optional advertising measurement described above, and public food database providers for barcode lookup.

We do not receive your full payment card details. Purchases and billing are handled by Apple through your Apple ID and by RevenueCat for subscription status.

How Information Is Used

Information is used to:

• Provide workout, food logging, meal planning, barcode, and AI-assisted features.
• Verify premium access and restore purchases.
• Respond to support requests.
• Protect the service from abuse, troubleshoot problems, and improve reliability.
• Measure app and subscription performance and, when you allow tracking, advertising results.
• Comply with legal, App Store, and security obligations.

Permissions

RepBite may request camera access for barcode scanning and meal photos, photo library access when you choose an existing image, and notifications for workout or app reminders. You can change these permissions in iOS Settings.

Retention

Data stored locally remains on your device until you delete it in the app, remove the app, or reset your device. Backend request logs and support requests are retained only as long as needed for security, operations, support, legal, and App Store compliance.

Creator referrals

If you choose to enter a creator code, Firebase Authentication creates a pseudonymous app identity. We connect your code to verified subscription purchases, trials, renewals and refunds through Firebase and RevenueCat to attribute the referral and calculate agreed commissions. Creator codes do not change subscription prices. Creators receive aggregate counts and commission totals, not app identities, receipts, health or fitness information, meal photos or payment details.

Creator landing pages count page requests and App Store clicks in aggregate without referral cookies or device identifiers. These counts can include repeat visits and bots; they do not confirm downloads. A link click alone does not attribute a purchase. Creator codes must be applied in the app before a first trial or subscription.

Your Choices

• You can choose not to use camera, photo, barcode, AI generation, or support form features.
• You can delete local app data by removing the app from your device.
• You can manage or cancel subscriptions in your Apple ID subscription settings.
• You can change advertising tracking permission in iOS Settings. Open RepBite with a network connection afterward so it can update its advertising identifiers with RevenueCat.
• You can request access, deletion, or correction of records we hold through the support form. State that it is a privacy request and describe the records involved. We may ask for information needed to locate your records and verify the request. Do not include health details, passwords, or payment card information.

Removing the app deletes its local data but does not automatically delete records held by service providers or cancel an Apple subscription. We review deletion requests and coordinate with providers where applicable; some records may need to be retained for billing, security, or legal obligations.

Children

RepBite is not directed to children under 13. If you believe a child has provided personal information through RepBite, contact support and we will review the request.

Changes

We may update this policy as RepBite changes. The latest version will be posted on this page with a new updated date.

Contact

For privacy questions or support requests, use the support page: https://smartassistant-dfc25.web.app/support.