Privacy Policy

Effective: September 10, 2026 · Version 2026-09-10

Deutsch · Terms of Use

This policy explains how Repsset processes personal data. Repsset is a workout log, not a medical application.

1. Controller and contact

The controller for Repsset is:

Fabian Waller
Email: repsset@fabianwaller.de

2. Data we process

Depending on how you use Repsset, we process:

• Account and sign-in data: internal user ID, email address, display name, authentication provider, and technical session data. Sign in with Apple may provide a relay email address. Google Sign-In may provide your name, email address, profile picture, and provider identifier.
• Anonymous accounts: Repsset initially creates a pseudonymous Supabase account with a random ID. “Anonymous” means you do not initially provide an email or social login; the service can still distinguish the account and the data you enter. Servers may also process IP addresses and security logs.
• Fitness profile: age bracket, training experience, sleep category, self-reported stress, goals, focus muscles, equipment, available days, and session duration.
• Workout data: programs, exercises, weights, repetitions, sets, timestamps, duration, personal records, progress, and volume metrics.
• Subscription data: App User ID, product, purchase state, term, receipt, and transaction information. The App Store processes payment credentials; Repsset does not receive complete payment details.
• Agent Access data: if a user enables Agent Access, we process OAuth client details, authorization status, and limited security logs (user/client identifiers, requested tool, outcome, and timing) to provide and protect the connection. We do not log tool arguments or returned workout data.
• Technical usage data: Expo Insights records an app-launch event with a persistent EAS client ID, project ID, app version, platform, and operating-system version. We use this for aggregate product and technical measurement. We do not use advertising SDKs or cross-app tracking.
• On-device data: local settings, authentication tokens, cached server data, and an active workout. If you select a photo or video for an Instagram Story, Repsset passes it locally to the system share flow and does not upload it to Repsset.

3. Purposes and legal bases

We process data:

• to provide accounts, synchronization, offline use, workout logging, programs, and subscription features (GDPR Article 6(1)(b));
• to secure, troubleshoot, prevent abuse of, and reliably operate the service (Article 6(1)(f), our legitimate interest in a secure and stable service);
• to meet mandatory legal obligations, including accounting and tax duties (Article 6(1)(c)); and
• conservatively, for fitness-profile and workout data, on your explicit consent (Articles 6(1)(a) and, if the information qualifies as health data, 9(2)(a)).

You give this consent when you select Agree & Continue during onboarding. You may withdraw it prospectively by deleting your account in Settings → Delete Account or contacting us. Processing the fitness and workout data you enter is necessary for Repsset’s core features, so those features cannot continue after withdrawal. Withdrawal does not affect processing that was lawful before it.

4. Recipients and service providers

We do not sell personal data or use it for personalized advertising.

Providers process data under their contracts and privacy notices. We may also disclose data when legally required or necessary to establish, exercise, or defend legal claims.

User-selected AI agents

Agent Access is optional and read-only. After you approve a connection, the MCP-compatible agent and AI provider you selected can retrieve your Repsset profile, programs, workout templates, completed workouts and sets, notes, personal records, and referenced exercise details. The agent cannot create, edit, or delete Repsset data. The selected provider processes the retrieved data under its own privacy terms; review those terms before connecting. You can revoke all Agent Access immediately in Repsset settings.

5. Apple Health / HealthKit

Apple Health export is optional and requires system permission. Repsset does not read HealthKit data. When enabled, the app writes a completed strength-training workout locally to HealthKit, including start and end times, duration, workout ID and name, and exercise and set counts. Repsset does not send this HealthKit data to Supabase, RevenueCat, Expo, or Google and does not use it for advertising.

You can change access in iOS under Settings → Privacy & Security → Health and delete entries in the Health app. Apple processes HealthKit data under Apple’s terms.

6. Local storage and iCloud backup

• Authentication tokens are stored in the iOS Keychain.
• MMKV and AsyncStorage hold the query cache, preferences, sync state, and active workout for offline use.
• The TanStack Query cache has a maximum persisted age of 30 days. An active workout remains until completion, cancellation, sign-out, or account deletion.
• iOS may include MMKV and AsyncStorage data in the user’s encrypted iCloud or device backup. This can help restore guest data and unfinished workouts when the user restores their device. Apple controls the backup and restoration process; Repsset does not directly access the user’s iCloud account.

User-scoped local data is cleared on sign-out or deletion. Existing device backups are controlled separately by Apple and may retain an earlier copy until Apple replaces or deletes that backup. Operating-system, Keychain, or backup operations can complete asynchronously.

7. Retention and deletion

• Account, fitness, and workout data is generally retained while your account exists.
• Agent authorization handoffs expire after 10 minutes and are deleted after use. Agent client records remain while the account exists or as needed for revocation and security.
• Local query cache is retained for no more than 30 days; other local preferences remain until sign-out, deletion, or removal of the app.
• Repsset does not upload or retain the media you select for sharing.
• Expo Insights and security logs are retained only as needed for aggregate measurement, security, and operations under the relevant provider’s retention practices.
• Apple and RevenueCat may retain purchase and subscription records longer where needed to maintain entitlements, prevent fraud, process billing, or meet legal obligations.

Using Settings → Delete Account deletes your Supabase account and directly associated server data and clears user-scoped local storage. For Apple-linked accounts, Repsset also revokes Apple authorization. Account deletion does not cancel an App Store subscription; cancel it in Apple’s subscription settings. Email us to request deletion of your RevenueCat customer record or exercise another privacy right. Data may remain temporarily in access-restricted technical backups or where mandatory law requires retention, after which it is deleted or blocked.

8. International processing

Supabase, RevenueCat, and Expo are US-based providers and may use subprocessors in other countries. Apple and Google also process data internationally. When personal data from the EU/EEA or Switzerland is transferred to a country without an adequacy decision, we rely on safeguards offered by the provider, especially EU Standard Contractual Clauses and, where appropriate, supplementary measures. A project’s primary database region is distinct from possible support, security, or subprocessor access.

9. Your rights

Depending on applicable law, you may have rights to access, correct, erase, restrict, or port your data; object to certain processing; and withdraw consent. You may also complain to a competent data-protection authority. Contact repsset@fabianwaller.de.

10. Security and policy changes

We use TLS, Supabase Row Level Security, and secure token storage. No system is completely secure. We will update this policy for material changes and request a new consent version where required.