Privacy Policy and Data Protection Notice

1. Controller and scope

Alper BİÇER, Avcular mah 4174. sokak no 17/7 Edremit/Balıkesir is the data controller for the Motion Arc Fit web, PWA, iOS and Android services. Contact: [email protected]. Notice version: 2026-08-12. Consent choices are presented separately from this notice.

2. Data we process

• Account and identity data: email, account ID, sign-in provider, display name, Arc ID, approved profile image and legal-version records.
• Activity and profile data: workout type, duration, sets, repetitions, weight, distance, pace, progress, badges, preferences and optional notes.
• On-device drafts and sync records: unfinished workout drafts, notification/reminder preferences, and the last Apple Health sync time plus imported/exported record counts. These remain in user-and-device-specific local storage; Apple Health sync metadata does not contain raw health data.
• Apple Health: only in the iOS app, after HealthKit permission and the user taps Sync Now, workout type, start time, duration, distance and active-energy summaries may be read or written. Heart rate, routes, location and raw sensor samples are not read.
• Optional sensitive data: body measurements, birth year, heart-rate information and health information entered by the user, processed only after a separate consent where required.
• Pelvic floor program: after a separate device-storage choice, the acceptance time and completed sessions stay only on the user’s device. They are not sent to the server, activity history, community, badges or leaderboard.
• Location: saved venue coordinates and foreground location used to calculate outdoor distance/pace only after permission and a separate choice. Raw route points are not stored on the server and there is no background tracking.
• Community data: posts, comments, follows, reactions, notifications, reports and blocks.
• Paddleboard meetups: event title, approximate region, exact meeting instructions, time, level, capacity, participation/approval/waitlist and check-in status. Exact meeting instructions are shown only to the organiser and accepted participants.
• Coach assignments: an explicitly accepted coach-athlete connection, assignment targets, the athlete’s separate coach note, and the submitted activity duration and effort.
• Technical and security data: IP address, user agent, session/device information, error and security logs. If the user separately opts in under Settings, Sentry may receive a scrubbed error/crash stack, app version and device/operating-system type; PostHog may receive a general screen category, platform, operating system, app version and non-persistent random session identifier. User identity, health data, form text, full URLs, click capture and session recording are excluded from these flows.

3. Purposes and legal bases

• Providing accounts, workouts, progress, community and support: performance of the user contract.
• Security, abuse prevention and service reliability: legitimate interests that do not override user rights, and legal obligations where applicable.
• Regulatory, consumer and legal claims records: legal obligation and the establishment, exercise or defence of legal claims.
• Optional health data, precise saved-location features, public leaderboard participation and marketing: separate consent or permission, where required.
• Optional Sentry error/crash reporting and PostHog anonymous usage analytics: a separate opt-in for each provider before processing starts. Declining does not affect core features.

4. Visibility and automated calculations

Personal workout records are not community posts unless the user chooses to share them. Public leaderboard participation is off by default. Level, points and badges may be calculated automatically, but these calculations do not make legal or similarly significant decisions.

The coach role alone does not grant access to activity records. The athlete separately accepts the coach connection and each assignment. A coach sees only the assignment target, submitted duration and effort, and the athlete’s separate coach note. Private activity notes, body measurements, photos and precise location are not shared. Coach access ends when the connection is ended.

A Paddleboard meetup may show its approximate region to the selected audience. Exact launch instructions are visible only to the organiser and accepted participants; a request or waitlist position does not grant access. Weather is resolved server-side from the approximate region without sending a route or device coordinates to the forecast provider.

5. Processors and international transfers

Data may be processed, only as necessary, by Supabase (authentication, database and storage), Cloudflare (asset storage/delivery and security), hosting and email providers, Apple or Google for the selected sign-in method, professional advisers and lawful authorities.

When a Paddleboard weather forecast is requested, only the entered approximate region is sent to Open-Meteo location search. Device location, exact meeting instructions, user identity and routes are not sent. Returned coordinates are used transiently to obtain the forecast and are not stored in the Motion Arc Fit database.

Replicate is used by administrators to generate public editorial artwork; user accounts, private community content, health data and location data are not sent to it. International transfers are made only where a lawful transfer mechanism and required safeguards are in place.

Apple Health sync runs through Apple HealthKit and device permissions. Motion Arc Fit processes only the workout summaries in a sync explicitly started by the user; Apple Health data is not used for advertising, profiling or third-party targeting.

Sentry processes scrubbed technical error records only when the user enables error and crash reports. PostHog processes allowlisted general usage events only when the user enables anonymous analytics. The choices are independent, the SDKs do not send data before opt-in, and neither provider is used for advertising, cross-app tracking, user profiles or session recording.

6. Retention, deletion and security

Account and activity data is kept while the account is active or until earlier deletion. Community content, Paddleboard meetups, participation and clubs remain until deletion, departure, account closure or moderation. Device-only pelvic floor progress remains until the user resets it or clears browser/app data and does not enter server backups. On-device workout drafts, reminder choices, Apple Health sync metadata and telemetry choices remain until sign-out, account deletion, local-data clearing or they are no longer needed. Disabling a telemetry choice stops new sends; prior provider records are deleted or anonymised after the shortest retention period verified and documented before release. Limited legal, consent and security records may be retained for the applicable limitation or statutory period. Deleted server data leaves backups within the configured backup cycle.

Security measures include HTTPS, access controls, row-level policies, server-only privileged credentials, protected session storage, rate limits and incident records.

Use the account deletion page to delete an account.

7. Your rights and choices

Depending on applicable law, you may request access, correction, deletion, restriction, portability, information about recipients, objection and withdrawal of consent. Sentry and PostHog choices can be disabled independently under Settings > Privacy, which stops new sends. Submit a verifiable privacy request to [email protected]. You may also complain to the competent data-protection authority. Withdrawing consent does not affect earlier lawful processing.

8. Changes

Material changes to purposes, categories, recipients or legal bases are notified through an appropriate channel. A new consent is requested where the change cannot be covered by the existing choice.