Privacy Policy

Account information

Creating an account is required to get your training plan — building it happens on our server and needs you to be signed in, with no offline mode. You can answer the setup questions before you create one. You can sign up with an email address and password, or with one-tap Google Sign-In. If you sign in with Google, Google processes that sign-in per its own privacy policy; we receive only your email address and Google account ID from it, the same as we'd receive from an email sign-up. Your password (for email sign-up) is handled by our authentication provider, Supabase — we never see or store it in plain text.

Profile and training data

Your running experience level, goals, weight, chosen race and goal time, training schedule preferences, and the training plan we generate for you, including past plans you've replaced. If you complete or reschedule a workout, we record that too.

Coach setup. If you set up your plan with the coach (this setup is being added and may not be in your version of the app yet), we keep the choices you make in it, all picked from fixed options: for example what you're working toward, how much you run now, whether you'd rather walk, and whether you chose to share your recent runs. We also keep which version of the questions you saw, how many you were asked and when you finished. There is no free-text box. If the coach suggested any of your settings from your runs (see Suggested settings from your runs below), we keep a record of each suggestion: which setting, the suggested value, whether it came from Health Connect or Garmin, how many days and runs it looked at, how sure it was, the value you ended with, and whether you confirmed it, changed it or it wasn't used. We use these records to build your plan and, looking at all runners together, to check how often suggestions are right so we can make them better (records based on Garmin runs are left out of that check; see Garmin Connect).

Health and fitness data — optional

Activity sync. If you choose to connect Apple Health or Health Connect, we read your exercise sessions and the distance, steps and calories burned recorded with them, including past activities, to match them against your planned workouts. For a matched run we keep only its distance, duration, pace and source app, stored with your plan so it syncs across your devices. A run that matches no planned workout (for example a run on a rest day) is kept on this device only, for 42 days, with the same fields, so Paceline can offer to count it against a nearby workout; it is not synced and is deleted when you sign out or delete your data.

Suggested settings from your runs. If you connect Health Connect while setting up your plan with the coach, the app reads your recent runs from it (by default, the last four weeks) and works out, on your phone, a suggested starting point: how often and on which days you run, your usual long-run day, your experience level and your easy pace. The runs it reads for this aren't uploaded. You see every suggestion and can confirm or change it before your plan is built. The settings you end with become part of your profile and plan, and the record of each suggestion is saved with your account (see Coach setup above). You can do this before you create an account; until you do, only the setup events described under App usage events are sent. Connecting Health Connect here also turns on Activity sync, described above.

Recovery insights. If you separately opt in, we also read your heart-rate variability (HRV), resting heart rate and sleep sessions (time in bed; sleep on Android only). These are used only to decide whether upcoming long runs in your plan should be trimmed back, or a harder session swapped for an easy one. They're processed and kept on your device only, as a small rolling 14-day summary, and are never uploaded to our servers.

All of these are optional and off by default; declining any of them doesn't affect the rest of the app. Health data is used only to provide these features — never for advertising, never sold, and never shared with anyone. We look at health and fitness records only in aggregate: nobody at Paceline reads an individual runner's records unless you ask us to (for example, in a support request), or where needed to keep the service secure or to comply with the law. Our use of data received from Health Connect follows the Health Connect Permissions policy, including its Limited Use requirements.

Garmin Connect — optional

If you choose to connect your Garmin account (this option is being added; it is off until you connect), Garmin asks you to approve the connection on its own sign-in page. We never see your Garmin password. We store the access token Garmin gives us, tied to your Paceline account, so we can send your planned workouts to your Garmin watch and, if you allow it, receive the activities, and later the heart-rate and sleep summaries, that Garmin sends us after you sync your device.

Before we send anything to Garmin for the first time, the app shows a notice, links to Garmin's own privacy policy (garmin.com/privacy/connect) and asks you to confirm. When you send workouts, we send only the planned run workouts for the period you chose: their name, date and target steps (distance or time, and pace). We keep a record of which workouts we sent (Garmin's identifiers for them, their dates and a fingerprint of their content) so that sending again updates your calendar instead of adding duplicates. That record is deleted when you disconnect Garmin or delete your account. Workouts already sent stay in your Garmin Connect account after you disconnect; you can delete them there.

Garmin data is used only to deliver and adjust your own training plan inside Paceline. That includes suggesting your starting settings from your recent Garmin runs when you set up a plan with the coach; those suggestion records are marked as coming from Garmin and are used only for your own plan, never in the check across all runners described under Coach setup. We don't sell it, we don't share it with advertisers or data brokers, and we don't use it, or anything derived from it, to train, evaluate or improve AI models. No Garmin data is sent to Anthropic or to any other AI service. The only other party that handles it is our backend provider, Supabase, which stores it for us. You can disconnect Garmin at any time in the app or in your Garmin Connect account settings; disconnecting deletes the access token and stops all new data. Deleting your Paceline account deletes the token and any Garmin data we hold for you. To see, correct or export the Garmin data we hold, write to us at the address under Contact us.

Location — optional

If you use the race-week readiness brief (a Paceline Pro feature) and tap its weather-forecast prompt, the app requests your device's approximate location — rounded to about 1.1 km before it ever leaves your device — and sends it to our weather-data provider, Open-Meteo, to fetch a forecast for race day. We don't store this location, use it for any other purpose, or request it anywhere else in the app. If you decline or never tap that prompt, no location data is ever read or sent.

In the same brief you can instead type your race's city to get a heat-adjusted race goal. What you type is sent to Open-Meteo's place search, and the chosen city's coordinates to its forecast service. The chosen city (its name, coordinates and time zone) and your race start time are saved with your plan.

Subscription and purchase status

If you subscribe to Paceline Pro, we verify your purchase with Google Play's Developer API and store whether you have an active subscription. We don't receive or store your payment card details — those are handled entirely by Google Play Billing. We may also grant Pro for free, for example to beta testers; that's recorded the same way, with no purchase involved.

Notifications

A reminder for a missed long run is scheduled and delivered entirely on your device. Other reminders (a long run tomorrow, the start of your taper week, a missed workout) are sent by our server through Firebase Cloud Messaging. For these we store your device's push token, platform (Android or iOS), time zone (so reminders arrive at a sensible local hour), your per-reminder on/off settings, and a log of which reminders were sent (so you never get the same one twice). Signing out deletes your push token and settings. You can turn each reminder off in Profile → Notifications, or turn off notifications for Paceline in your device settings.

AI-tailored plans — optional, Paceline Pro

If you choose the AI-tailored plan option, our server sends Anthropic (the provider of the Claude model) your chosen race type, experience level, goal finish time (if any) and weekly schedule preferences, and nothing else: no name, email, account ID, location, health data or free text. The model returns planning numbers that our server turns into your plan. Anthropic acts as our data processor. The standard plan option makes no such call. Settings the coach suggested from your Health Connect or Garmin runs are never sent to Anthropic, even after you confirm or change them.

App usage events

We record a small, fixed set of in-app events — for example which setup step you reached and what you picked, whether plan generation succeeded, workouts completed, and paywall views and purchases — with the app version, platform, your device's language setting (for example, "he-IL"), a random per-launch session ID and, if you installed Paceline from a link that carries a campaign label, that label. Setup events hold only options and ranges, never free text or exact values from your runs: for example, how many runs were found, which days you run, or a pace range.

Before you have an account. Events recorded while you're signed out can be sent to us before you have an account. They're tagged with a random install ID that the app creates and keeps on your phone. It isn't your advertising ID or a hardware identifier, and these events carry no name, email, account ID or location. When you sign in or create an account on that install, we link its earlier events to your account, so we can see which setup steps lead to a plan; from then on they're kept and deleted like the rest of your usage events. Events from an install that never signs in are deleted after 90 days.

Usage events are stored in our own database, not sent to any analytics company, and used only to understand where the app works and where people get stuck.

Crash reports

When the app crashes or hits an unexpected error, a report is sent to Sentry. It contains the error and stack trace, your device model and OS version, the app version, and your account ID (a random identifier, not your email) so we can tell whether one person or many are affected. It doesn't include your training plan, health data or location.

Website (pacelinerun.com)

The site sets no cookies. It records one anonymous row per page view and per "Join the beta" click (which link, an optional campaign label from the address you arrived by, and the time), with no identifier of any kind; it is skipped if your browser sends Do Not Track. If you can't get into the beta and use the "leave your email" form, we store the email address you type, the optional note, that campaign label and the time, only so we can add you and reply. It isn't tied to an app account, isn't used for marketing, and you can ask us to delete it at any time by emailing privacy@pacelinerun.com.

Sign-in protection

Sign-up, sign-in and password reset are protected by Cloudflare Turnstile, which checks that the request comes from a real person. Cloudflare processes technical signals from your device (such as IP address and browser characteristics) for this check, under its own privacy policy.