Privacy Policy

Effective date: 11 October 2026
Last updated: 11 October 2026

1. Who we are

RedPlate is operated by WIKTOR BARON LABS, represented by Wiktor Baron, at ul. Jana Heweliusza 11/811, 80-890 Gdańsk, Poland ("RedPlate," "we," "us," or "our"). We are the controller of the personal information described in this policy.

For privacy questions and requests, email contact@redplate.app. For app support, you can also use support@redplate.app.

This policy covers the RedPlate mobile app and its account services. RedPlate stores information locally and synchronizes saved account data with our cloud service when you sign in. Some profile information is visible to other signed-in users.

2. Information we process

Account and identity information

When you sign in with Google or Apple, we process your RedPlate account ID, provider identity, email address where supplied, authentication/session information, and basic profile information supplied by the provider. Apple may provide a private relay email address. Your RedPlate display name is the name you enter in the app. We do not receive your Google or Apple password.

Native Sign in with Apple also sends an authorization code to our backend. We exchange it with Apple and retain encrypted authorization credentials so that saved Apple authorization can be revoked during account deletion.

Profile, training and progress information

We process the information you enter and results calculated from it, including:

• Your display name, bodyweight, selected gender, goals, measurement units, lift preferences, starting lift estimates and selected tracked/ranked exercises.
• Workouts, dates and times, exercise names, sets, weights, repetitions, effort ratings, completion status, routines, personal records and estimated strength values.
• Trophies, rank, workout/rest dates, streaks, rewards, virtual inventory, banners and preferences associated with these features.

Discontinued inputs and older local records

The current build skips pre- and post-workout check-ins and does not offer new training-program generation. The ordinary workout flow therefore does not ask for sleep, calorie-intake, energy, soreness, pain, injury or check-in notes. Height entry has also been removed from onboarding and Settings.

Earlier released versions stored information locally without RedPlate account creation. When you create an account in the current version, saved ordinary workout/routine history can be imported and synchronized. Discontinued height and pre/post check-in fields are excluded from cloud uploads, including older queued changes and imported history, and are not restored from cloud records on another device. Their existing values may remain in the originating installation's local account cache. We do not receive those local-only values through the current synchronization flow.

Any previously saved program records can still be retained and synchronized, including their saved questionnaires and prescriptions, even though new program generation is disabled. Changes to the current sync flow do not themselves erase information already uploaded by an earlier account-enabled build. Applicable deletion requests and account deletion cover information held in your account; device-only information also depends on the device's local storage and backup arrangements.

Social information

We process friendships, friend requests and responses, blocks, invite identifiers, and in-app notification history/read status. Other participants receive information about your interactions with them, such as a friend request, acceptance, rejection or removal. People search uses RedPlate display names; it does not read your phone's address book.

Notification and technical information

For enabled iOS push reminders, we process the device push token, installation identifier and verification secret, account/session association, timezone, delivery environment, and reminder/delivery records. Android reminders are scheduled locally using saved activity and reward information; the current Android implementation does not use Firebase Cloud Messaging or register an Android token with our push backend.

Our infrastructure and subscription/update providers process technical information needed to authenticate requests, verify purchases, deliver updates, maintain security and operate their services. This may include IP addresses, request timestamps, app/SDK version, operating-system platform, locale and service-usage information, depending on the provider.

Communications

If you contact us, we receive your email address, message, attachments and any other information you supply. Please avoid sending unnecessary medical records or sensitive information.

3. Why we use information

We use information to provide accounts, cloud synchronization and offline caching; save and restore workouts and routines; calculate strength estimates, progress and ranks; maintain rewards and streaks; provide search, profiles, friendships, invites and blocking; verify Pro access and purchases; deliver enabled reminders and software updates; respond to requests; protect the service; and comply with applicable law.

Training calculations use saved profile and workout information to provide fitness estimates and progress displays. They are not medical diagnoses. The disabled program generator is implemented within the app; we do not send its questionnaire or workout history to an external generative-AI service to generate a program.

Account identity is needed for cloud and social features. Information used by a particular fitness feature is needed to calculate that feature's results. Notification permission can be declined; declining it does not prevent workout logging.

4. Local storage and cloud synchronization

Onboarding information is initially saved locally. When you sign in, local information is imported into your account as appropriate and saved account data is synchronized through Supabase, our authentication and cloud-database provider. Existing accounts restore their saved cloud profile. Account data is cached on the device for offline use, and queued changes upload when synchronization reconnects.

Logging out does not delete your account, cloud data or that account's local cache. Unsynchronized changes remain in the account's cache for the next sign-in to that account. Different accounts have separate caches.

Uninstalling the app does not delete your cloud account. Removing local app data can lose information that has not synchronized. Operating-system backups and device transfers are controlled separately by your device and backup provider.

5. Information visible to other users

After your account has a completed profile, other eligible signed-in RedPlate users can find it by searching your display name or opening an invite. Visibility extends beyond accepted friends. The current app does not offer a private-profile switch.

Shared information includes your display name, banner, trophies/rank, current streak and whether it is at risk, workout/rest dates in the displayed current-month calendar, selected ranked exercise, its best estimated one-repetition maximum, displayed weight unit and Pro badge when applicable. Account IDs are used to identify profiles and connections.

Other users' profile views do not expose your email, bodyweight, height, selected gender, detailed workout sets, check-in answers, pain/injury notes, routines, programs or full inventories. RedPlate and authorized providers process private account records to deliver the service; "private" does not mean inaccessible to the service operator.

Blocking restricts the accounts' access to each other's profiles through the app and removes associated connections and related notifications. An invite identifies a discoverable profile and does not grant access to private account data. Information already seen or copied by another person cannot necessarily be withdrawn from that person's possession.

6. Providers and disclosures

We use:

• Supabase for authentication, cloud storage/synchronization, social records, service controls and iOS notification infrastructure.
• Google and Apple for sign-in and identity verification. Their own services are also governed by their privacy policies.
• Apple and RevenueCat for current iOS purchases, restoration and subscription entitlement verification. RevenueCat starts with an anonymous identifier and receives your RedPlate account ID after sign-in to associate access with the account. It processes relevant purchase/transaction information, entitlement status, timestamps and technical information. We do not send RevenueCat your display name, email, body measurements, workouts, check-ins or injury notes. Our backend checks entitlement status for Pro badges and does not expose transaction details to other users. Apple processes payment; we do not receive your payment-card details. Purchasing and restoring subscriptions is currently supported on iOS only.
• Apple Push Notification service (APNs) for enabled iOS loot-ready and streak reminders. Apple receives the push token and notification payload needed for delivery. Friend-event notifications currently appear inside the app.
• Shorebird for software patches in builds distributed with Shorebird. Update checks send the app identifier, release/patch version, platform, architecture, applicable channel and a random identifier for the installation. The identifier supports active-installation counts. Shorebird's infrastructure may also process network information. We do not send it workout records, body measurements or check-in content.

Android reminders use the phone's notification/alarm services and local scheduling information. The related saved workout/reward records still use ordinary account synchronization.

Relevant provider information is available from Supabase, RevenueCat, Shorebird, Apple and Google.

We may disclose information when required by law or when necessary and lawful to address fraud, security incidents or legal claims.

7. Notifications, widgets and workout displays

You can decline notification permission or change it in device settings. Reminder timing uses saved reward deadlines, activity/rest dates and timezone information. iOS sends remote reminders through APNs; Android schedules reminders locally. Notification delivery is subject to device settings and operating-system limits.

Home-screen widgets use locally stored summaries such as rank, estimated strength and streak history. Running workouts can appear in iOS Live Activities or Android ongoing notifications. Notification previews and system displays may reveal information to someone who can see your screen; visibility depends on the platform and your device settings. Android reminder data is excluded from the app's Android cloud-backup/device-transfer configuration.

8. Advertising and analytics

The current app does not include advertising SDKs or a general-purpose behavioral analytics SDK. We do not sell your personal information or use your workout, bodyweight or other profile information for advertising or cross-app advertising tracking.

Subscription operations, infrastructure/security logs, service quotas and Shorebird installation counts still involve limited technical information. Exercise analytics and progress charts are fitness features calculated from your saved records.

9. Legal bases

Where the GDPR applies, we use the following legal bases:

• Providing the service — Article 6(1)(b). We process account identity, saved workouts and routines, bodyweight and relevant profile preferences, progress calculations, requested cloud/social features and subscription access where necessary to provide the RedPlate services you use. Bodyweight and training records support fitness logging, strength estimates, comparisons and progress displays.
• Legitimate interests — Article 6(1)(f). We process proportionate technical and support information to secure and maintain RedPlate, prevent abuse, deliver updates, respond to support and handle legal claims. We consider your rights and reasonable expectations when relying on these interests.
• Legal obligations — Article 6(1)(c). We process or retain information where required to comply with applicable law.
• Consent — Article 6(1)(a), where applicable. If a particular activity relies on consent, we explain that activity and request consent separately. You may withdraw it without affecting prior lawful processing.

Acknowledging this Privacy Policy provides notice of our processing; it does not itself create consent for a separate activity that requires it.

10. Retention and deletion

Saved account records are retained to provide your account/history until you delete the relevant records, request applicable erasure or delete your account. Deleting a training record propagates through synchronization. Its content is replaced with a deletion marker; record identifiers, revisions/timestamps and accepted-change receipts can remain until account deletion so other devices apply deletions and retries do not duplicate changes.

Social history is retained with the account, subject to deletion of related records through blocking or account deletion. iOS push registrations are removed on unregistration, session/account deletion or detection of an invalid token. Loot-reminder jobs and delivery records are cleaned up when the reward is claimed or its deadline is more than a day old; streak-reminder history is cleaned up seven days after its delivery window expires. Android scheduling records are held locally and pending reminders are cleared when the account is logged out or switched.

Support correspondence is retained while needed to handle the request, related follow-up, disputes or applicable legal obligations. Necessary legal/claim records are retained for the applicable obligation or claim period and removed when no longer needed. Provider backups and internal operational records have their own applicable retention arrangements; deleting a record from the active database does not immediately rewrite existing backups. Supabase's current Free plan normally makes one day of API/database logs available; that is not a promise that every provider log or backup is erased within one day.

You can delete your account in Profile → Settings → Delete account. Successful deletion removes the authentication account and related records from the active RedPlate backend, including saved training data, shared-profile information, social records, invites, push records and saved Apple credentials. The requesting app also clears its account and onboarding data on that device.

Deletion attempts to revoke captured Apple authorization before removing an Apple-linked account. Where no revocable credential was captured, such as certain older/browser sign-ins, the account can still be deleted and the app shows Apple's manual disconnect instructions. Stopping Sign in with Apple authorization by itself does not delete your RedPlate cloud account.

Cached copies on other devices and operating-system backups may remain. The deletion flow does not remotely wipe other installations or independently managed backups. Clearing RedPlate's local app data removes that installation's cached data, subject to the device's backup arrangements.

Account deletion, logout and uninstalling do not cancel an App Store subscription. Cancel renewal separately through Apple. RedPlate account deletion also does not automatically erase Apple's transaction records or RevenueCat customer/purchase records. Contact us about applicable provider-data erasure; lawful retention exceptions may apply.

For deletion help or a request without access to the app, email contact@redplate.app. We may request proportionate information to verify account ownership.

11. International processing

Our main Supabase database is hosted in the United States (us-east-1). Providers and their subprocessors may process information in other countries. A database's hosting region does not determine the location of every provider operation.

Supabase and RevenueCat's standard agreements incorporate data-processing terms and applicable Standard Contractual Clauses for restricted international transfers. Their safeguards are described in the Supabase DPA and RevenueCat DPA. Contact contact@redplate.app for information or available copies of safeguards relevant to your information, subject to lawful redactions.

12. Your rights

Depending on applicable law, you may have rights to access, correction, erasure, restriction, objection and portability. You may object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting prior lawful processing.

Email contact@redplate.app to exercise these rights. The current app has no self-service export feature; applicable access/export requests can be made by email. We may seek proportionate identity verification and will handle requests within the periods required by law, subject to applicable exceptions.

You may complain to your competent data-protection authority. In Poland, this is the President of the Personal Data Protection Office (UODO).

13. Age, security and changes

RedPlate is intended for people 18 or older. The sign-up notice asks users to confirm that eligibility; it is a self-declaration and does not verify age through identity documents. If you believe an under-18 user has provided information, contact us so the account and processing can be reviewed and appropriate action taken.

We use encrypted connections for cloud requests, account-based access restrictions and encrypted storage for saved Apple revocation credentials. Private training records are not end-to-end encrypted; RedPlate and authorized providers process them to deliver the service. Local data is subject to the app's account separation and device security. No system can guarantee complete security.

We will update this policy when the app, processing or applicable requirements change, revise the dates and provide additional notice of material changes where required.

Contact: WIKTOR BARON LABS / Wiktor Baron, ul. Jana Heweliusza 11/811, 80-890 Gdańsk, Poland; contact@redplate.app.