Privacy Policy

Summary

• RunToMax 1.0 is for adults aged 18 and older. Its age gate stores only the eligibility result, policy version, and confirmation time.
• No RunToMax account, email login, or password.
• Workouts, GPS routes, heart rate, and health history are stored in Apple Health and local app storage.
• Pro is one Apple subscription, offered monthly or annually. It includes both Cockpit and optional cloud coaching.
• Cloud coaching is off until you explicitly opt in. It sends a minimized summary through a RunToMax proxy to Google Gemini; the app does not contact Gemini directly in production.
• Optional product and coaching analytics are off until you opt in. RunToMax uses PostHog US Cloud with IP geolocation disabled and does not send exact workout or health values.
• The launch version has no public Strava integration, RevenueCat, Lifetime purchase, advertising, IDFA, or website analytics.

Who we are

"RunToMax," "we," "us," and "our" refer to Hidai Bar-Mor, an individual sole developer based in Israel, who develops and operates the RunToMax iPhone and Apple Watch application. Contact: hidai25@gmail.com.

Data the app processes

Health and fitness data (Apple HealthKit)

With your permission, RunToMax reads data needed for its training and recovery features, including workouts, workout routes, heart rate, active energy, distance, steps, running speed, body mass, resting heart rate, stride length, vertical oscillation, ground contact time, heart rate variability, sleep, VO₂ max, and running power. RunToMax writes workouts and related samples that it records back to Apple Health.

RunToMax does not use HealthKit data for advertising or sell it to data brokers. You can review or revoke Health access in iOS Settings → Privacy & Security → Health.

Location and routes (Core Location)

During an outdoor workout, RunToMax processes precise GPS coordinates, elevation, speed, and the resulting route. Location is used only while you are using the app or actively recording a workout. It is not used to track you outside an active workout. Completed routes are stored in Apple Health as part of the workout.

Profile and training settings

Details such as your first name, avatar, birth year, biological sex, body mass, heart-rate settings, race goals, plan answers, shoes, and unit preferences are stored locally in an Apple App Group shared by the iPhone app, Watch app, and widgets. RunToMax does not operate an account database containing this profile.

A profile birth year is optional physiology data for heart-rate-zone and calorie calculations. It is separate from the adult-eligibility check. The eligibility check does not ask for or retain a date of birth; it records only whether you confirmed you are 18 or older, the policy version, and the confirmation time.

Cloud coaching (optional, included with Pro)

Cockpit and cloud coaching are included in the same Pro subscription; cloud coaching is not a separate subscription. A Pro entitlement alone does not send data. You must also explicitly enable cloud coaching. If you do not enable it—or if the secured service is unavailable—the app uses its deterministic on-device coaching instead.

When enabled, RunToMax prepares a minimized coaching context from finalized, validated facts. It may include pace, heart-rate summaries, cadence, elevation gain, running-form averages, time in heart-rate zones, splits, training load and readiness, sleep and recovery summaries, recent comparable-run summaries, plan context, and weather. The language model is asked to explain those supplied facts; it is not the source of record for distance, pace, splits, recovery, or plan calculations.

The app sends that context over HTTPS to a RunToMax coaching proxy, which checks that the request is well-formed and forwards it to a billing-enabled Google Gemini service. The production app does not contain a Gemini API secret and does not call Gemini directly, so the key cannot be extracted from the app. The proxy does not log or store the prompt or the response; it records status codes and timings only, and it does not keep coaching content in any RunToMax database.

We do not include your name, email address, raw GPS coordinates, route polyline, contacts, photos, or individual heart-rate samples in the coaching request. Google may process the request and limited technical or abuse-monitoring logs under its Gemini API Additional Terms and Privacy Policy. RunToMax uses a paid Gemini service so Google states that prompts and responses are not used to improve its products. Google states that it retains prompts, their context, and responses for 55 days for abuse detection, security, and required legal disclosures. If content is flagged, authorized Google employees may review it.

Google's current Gemini API terms require users of API clients to be at least 18. RunToMax 1.0 is therefore an adult-only product, not merely an app with an adult-only coaching toggle. You can withdraw cloud-coaching consent at any time in Settings → Privacy → AI coaching; future cloud requests stop immediately.

Weather and map services (Apple)

RunToMax may send the coordinate or map region needed to Apple Maps or WeatherKit to render a map, obtain elevation context, or request temperature, humidity, and wind for heat-aware guidance. It does not send your training history or RunToMax identity with that query. See Apple's Weather privacy notice.

Subscriptions

RunToMax offers Pro as a monthly or annual auto-renewing subscription through Apple StoreKit. Pro includes Cockpit and cloud coaching. Apple processes payment and provides the app with purchase and entitlement status. RunToMax never receives your full card number, billing address, or Apple ID. The launch build does not use RevenueCat and does not offer a Lifetime purchase.

Bluetooth heart-rate monitors

If you pair a compatible Bluetooth heart-rate monitor, its name and peripheral identifier are stored locally for reconnection. Samples are used during the workout and may be written to Apple Health. They are not sent to RunToMax.

Apple Watch, iPhone, and widgets

WatchConnectivity and the shared App Group transfer workout data and settings between your Apple devices. Widgets read local Apple Health and App Group data. These features do not send your training history to a RunToMax account server.

App-local workout-detail archives, derived fingerprints, generated coaching caches, imported-run files, RPE ratings, plan execution feedback, and manually entered sleep use iOS data protection and are excluded from device backups. After reinstalling or restoring a device, reconstructable data may be rebuilt from Apple Health or recovered from the Watch where available. Imported runs that were not written to Apple Health may need to be imported again. Apple Health backup and synchronization are controlled separately by Apple and your device settings.

Consent-based product analytics

RunToMax uses PostHog US Cloud only after you explicitly opt in. Analytics may include a random installation identifier, app, build and device information, categorical feature events, and categorical or broad-bucket fitness and coaching events. Examples include workout type, broad completion ranges, training-plan feedback, and whether you confirmed or corrected an interpretation. RunToMax configures PostHog not to use the request IP for geolocation. Autocapture is off, and session replay is disabled in production.

We do not send your name, email, exact pace, distance, heart-rate or sleep values, location, route, workout identifier or workout time, or coaching text to PostHog. You can turn analytics off at any time in Settings → Privacy → Optional analytics. See PostHog's Privacy Policy.

Website and waitlist

The RunToMax website does not use Google Analytics, advertising trackers, or non-essential analytics cookies. If you join the waitlist, the email address you submit is processed by Web3Forms to deliver the signup to RunToMax. We use it only for TestFlight, launch, and closely related RunToMax updates. You can ask us to remove it at any time by emailing hidai25@gmail.com. See Web3Forms' Privacy Policy.

What RunToMax does not use at launch

• No advertising, IDFA, or third-party advertising trackers.
• No public Strava integration in the launch build.
• No RevenueCat subscription processing.
• No Lifetime purchase or separate AI Coaching subscription.
• No Google Analytics on the website.
• No RunToMax email/password account or cloud training-history sync.
• No contacts or calendar access.

Service providers

• Apple — HealthKit, Core Location, Maps, WeatherKit, StoreKit, WatchConnectivity, and App Store services ( privacy).
• Google — paid Gemini processing, only after an eligible Pro user explicitly enables cloud coaching ( privacy).
• PostHog US Cloud — minimized product analytics, only after opt-in ( privacy).
• Web3Forms — website waitlist form delivery, only if you submit your email ( privacy).

Retention and deletion

• Deleting RunToMax removes its local settings and cached app data. Workouts in Apple Health remain until you delete them in the Health app.
• The coaching proxy does not maintain a RunToMax training-history account or intentionally persist prompt and response content. Google may keep limited paid-service logs as described above.
• Turning analytics off stops future PostHog events. To request deletion of analytics associated with your random install identifier, contact us.
• Waitlist email addresses are kept until you unsubscribe, request deletion, or they are no longer needed for the launch communications described above.

Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of personal data. Most training data is already under your control on your device. For analytics, waitlist, or cloud-coaching questions, email hidai25@gmail.com.

Age eligibility

RunToMax 1.0 is intended only for adults aged 18 and older. We do not knowingly provide the app to or process personal information from anyone under 18, and parental consent does not make an under-18 person eligible for this release. The iPhone app fails closed until an adult eligibility result is established. On iOS 26 or later, you may use Apple's Declared Age Range service, which shares a coarse range rather than a birth date. RunToMax immediately reduces the response to an eligibility result and does not retain the range or its declaration source. If Apple's service is unavailable or declined, the app offers an explicit adult confirmation. The Apple Watch app requires the phone's current eligibility result before a workout can start, and complications hide cached run statistics until that result is current.

If we learn that an under-18 person has used RunToMax or provided data, we will disable access and take appropriate steps to delete data under our control. Contact hidai25@gmail.com for an age-eligibility or deletion concern.

International processing

Apple, Google, PostHog, and Web3Forms may process data outside your country, including in the United States. Their safeguards and transfer practices are described in the policies linked above. RunToMax minimizes what is sent and requires opt-in for cloud coaching and product analytics.

Security

Apple Health protects health and route data on your devices. Network requests use HTTPS. Cloud coaching uses a server-side credential rather than embedding a Gemini secret in the app. The proxy validates request shape, applies a strict body-size ceiling, and uses a capped credential. No system is perfectly secure; if we learn of an incident that requires notice, we will notify affected users as required by law.

Changes to this policy

We may update this Privacy Policy as the product changes. The effective date above identifies the current version. Material changes will be announced in the app or by email when we have an appropriate address.

Contact

Questions, requests, or concerns: hidai25@gmail.com.