Runcaster Privacy Policy

Overview

Runcaster is an AI-powered running coach that connects to Garmin Connect™ to generate personalized training plans, provide post-run feedback, and (optionally) create shareable run cards for Farcaster. This policy explains what data we collect, how we use it, and the choices you have. Your use of Runcaster is also governed by our Terms of Service, which include important health, safety, and liability terms.

Garmin Connect™ Data

When you connect your Garmin account via the Garmin Connect API, we access and store the following data:

• OAuth tokens: Access and refresh tokens to maintain your connection. Tokens are stored securely and never exposed to the browser.
• Garmin user ID: A stable identifier from Garmin used to link your activities.
• Activity summaries: Running activity metadata including start time, duration, distance, pace, heart rate (average and max), cadence, elevation gain/loss, calories, activity name, and device information.
• GPS route data: When available, GPS coordinates from your activities to render route maps and route previews.

We only collect running activities (including trail running and treadmill running). Other activity types are not stored.

How this data is used, processed, and stored: Garmin data is used solely to provide the coaching experience — displaying your runs, generating personalized training plans and post-run feedback, and (at your request) pushing workouts back to your watch. It is stored in our PostgreSQL database hosted by Supabase, with TLS in transit and access limited to authorized personnel, and retained until you disconnect Garmin or delete your account as described below.

Third-party processing of Garmin data: We never sell Garmin data and never share it with advertisers or data brokers. It is processed by third parties only as needed to provide the service: activity metrics and derived context are sent to OpenAI to generate AI coaching responses (OpenAI is contractually prohibited from training general-purpose models on this data); a run's approximate start coordinates and start time are sent to Open-Meteo to look up the weather conditions during that run; and our infrastructure providers Supabase (database) and Vercel (hosting) store and transmit data on our behalf. No other third parties receive Garmin data.

Apple Health (HealthKit) Data

On iPhone you can connect Apple Health instead of, or alongside, Garmin. When you allow it, the Runcaster app reads the following from the Health store on your device and uploads it to our servers:

• Workouts: running, walking and hiking workouts recorded by your Apple Watch or by any app that saves to Apple Health — start and end time, distance, duration, calories, elevation, cadence, and the name of the device or app that recorded them.
• Workout routes: the GPS track of each workout.
• Heart rate samples recorded during those workouts.

We read only workouts (and their routes and heart rate), not your wider Health record: no sleep, medical, reproductive or body measurements. On first connection we import the previous 90 days; after that, new workouts are read when you open the app or when iOS notifies the app of a new workout. We do not write to Apple Health.

Apple Health data is used only to provide the coaching experience — run analysis, training plans, briefs and the coach's context — and is processed and retained exactly as described for Garmin data above (the same AI processing, weather lookup and infrastructure providers; never sold, never shared with advertisers or data brokers, never used for advertising or marketing). We do not use HealthKit data for any purpose other than providing and improving the health and fitness features of the Service, and we do not disclose it to third parties except the processors named in this policy, acting on our behalf.

You can stop the import at any time from Profile → Devices (Disconnect, with the option to also delete the runs imported from Apple Health), or by revoking Runcaster's access in the iPhone Health app (Sharing → Apps → Runcaster).

Health Connect (Android) Data

On Android you can connect Health Connect instead of, or alongside, Garmin. Health Connect is the on-device health store that apps such as Google Health, Samsung Health, Garmin Connect, COROS and Strava can write to. When you allow it, the Runcaster app reads the following from Health Connect on your device and uploads it to our servers:

• Exercise sessions: running, walking and hiking sessions — start and end time, exercise type, title, laps, and the name of the app that recorded them.
• Distance, speed, step cadence and elevation gained recorded during those sessions, used to work out your pace and splits.
• Heart rate samples recorded during those sessions.
• Exercise routes: the GPS track of a session, read only when you tap "Add map" on that run and approve the Health Connect prompt for it. Routes are never read in the background.

We read only exercise sessions and the measurements recorded during them, not your wider health record: no sleep, nutrition, body measurements, medical, reproductive or respiratory data. On first connection we import the previous 30 days (the window Health Connect allows); after that, new sessions are read when you open the app and once a day in the background. Runcaster writes one thing to Health Connect: your planned workouts, as planned exercise sessions, so that watch apps which support them can show you the workout. We never modify or delete other apps' records.

Health Connect data is used only to provide the coaching experience — run analysis, training plans, briefs and the coach's context — and is processed and retained exactly as described for Garmin data above. That includes sending the run metrics to our AI provider to generate your coaching, which you consent to when you connect; it never includes selling the data, sharing it with advertisers or data brokers, or using it for advertising, marketing, credit or insurance decisions. We do not use Health Connect data for any purpose other than providing and improving the health and fitness features of the Service, and we do not disclose it to third parties except the processors named in this policy, acting on our behalf.

You can stop the import at any time from Profile → Devices (Disconnect, with the option to also delete the runs imported from Health Connect), or by removing Runcaster's permissions in the Health Connect settings on your phone (Settings → Health Connect → App permissions → Runcaster). Deleting your Runcaster account deletes the imported sessions with it.

AI Coaching and Stored Memories

Runcaster includes a chat-based AI running coach that uses your activity data and conversation history to provide personalized guidance. To do this, we:

• Send activity context to our AI provider: Your recent activity summaries (the metrics listed above) and chat history are sent to OpenAI's API to generate coach responses, training plans, and post-run feedback. OpenAI is contractually prohibited from training their general models on this data.
• Store coach memories: Facts you share with the coach (training goals, schedule constraints, injury history and any health conditions you choose to mention, preferences) are extracted by the AI and stored on your account so the coach can remember them across conversations. Sharing health information is optional; the coach works without it. You can view, edit, and delete these memories at any time from the Coach screen, and they are deleted with your account.
• Store training plans and targets:AI-generated 2-week training plans, structured workout steps, and any pace/distance/race goals you set are stored on your account so the coach can track progress and adjust plans over time.
• Compute embeddings: OpenAI's embedding model is used to detect duplicate memories so the coach doesn't accumulate redundant entries. Embedding vectors are stored alongside the memory text.

AI Transparency

Runcaster's coaching features are powered by artificial intelligence. To generate training plans, post-run feedback, and chat responses, we send your running activity data (the metrics listed above), your stored coach memories, and your chat messages to our AI provider (OpenAI) for processing. This processing is used to provide coaching to you and to maintain the quality and safety of the service (see “Quality, Safety, and Support Monitoring” below) — never for advertising or profiling. We do not use your data to train general-purpose AI models, and OpenAI is contractually prohibited from doing so.

By connecting Garmin and using the coach, you consent to this AI processing. You can withdraw consent at any time by disconnecting Garmin, deleting your coach memories, or deleting your account, after which we stop sending your data for AI processing. AI-generated guidance can be inaccurate — see our Terms of Service for important health and safety limitations.

Quality, Safety, and Support Monitoring

To find and fix problems before they affect more runners, we review how the coach is behaving:

• Automated conversation review: Coach conversations are periodically reviewed by automated systems (software rules and AI models) that look for app bugs, coaching errors, safety issues, and abuse or misuse of the Service. Findings — which may include short excerpts of a conversation — are compiled into internal reports that authorized personnel may read to diagnose and fix problems.
• Feedback you share: If you give the coach feedback about the app (something you like, something broken, a feature request), we log it — including your words — so we can act on it.
• Technical error logs: When something in the Service fails, we record technical details of the failure, which may include your account identifier, so we can diagnose and fix it.

Monitoring data is used only to operate, debug, and improve the Service. It is never used for advertising, never sold, and the same AI-provider terms apply: OpenAI is contractually prohibited from training general-purpose models on this data.

Pushing Workouts to Your Garmin Watch

When you have a training plan generated by the AI coach, you can push the plan's individual workouts to your Garmin Connect calendar so they appear on your watch on the day they are scheduled. This push:

• Happens only after you explicitly tap a "Push to Garmin watch" button on the Plan screen. Plans are never sent to your watch automatically.
• Includes only the structured workout details (warmup, intervals, cooldown, with pace or heart rate targets) — no chat history, memories, or other data.
• Can be undone by disconnecting Garmin or by removing the pushed workouts from the Plan screen, which deletes the corresponding entries from your Garmin Connect™ calendar.

When you push a workout to your watch, that workout data is transferred to Garmin and stored in your Garmin Connect account, where it is governed by Garmin's privacy notice. Do not connect Garmin or push workouts if you are restricted from uploading data to a Garmin Connect™ account.

Apple Watch: when Apple Health is your connected device and "Watch sync" is on, the app schedules the coming week's planned workouts into the Workout app on your Apple Watch using Apple's WorkoutKit, from your iPhone. Only the workout structure (steps with time or distance goals and pace or heart-rate alerts) is scheduled; it stays on your own devices and is not sent to Apple's servers by us. You can turn Watch sync off in Profile → Devices, and scheduled workouts are removed when you disconnect.

Purpose limitation

We use Garmin data only to provide the coaching experience — displaying your runs in the app, generating personalized training plans, providing post-run feedback, tracking goals, optionally pushing workouts to your watch, and (if you choose) generating shareable run cards for Farcaster. We do not use the data for advertising, profiling, or unrelated analytics.

User Control and Disconnection

You have full control over your Garmin connection:

• Disconnect anytime: Use the "Disconnect" button in the app to revoke Runcaster's access to your Garmin account. New activities will stop syncing immediately.
• Manage coach memories: Open the Coach screen and tap the memory icon to view, edit, or delete any fact the coach has stored about you.
• Remove pushed workouts: Workouts pushed to your Garmin Connect™ calendar can be removed from the Plan screen, which deletes them from Garmin as well.
• Data deletion: When you disconnect, we delete your OAuth tokens and Garmin registration. Activity data, training plans, and coach memories remain stored but will no longer update.
• Full deletion: Delete your account in the app (Profile → Delete account) or request deletion at runcaster.app/delete-account. This removes all your data including stored activities, generated share cards, training plans, and coach memories.
• Garmin side: You can also revoke access from within your Garmin Connect™ account settings under connected apps.
• Apple Health: Disconnect from Profile → Devices (optionally deleting the imported runs), or revoke Runcaster's read access in the iPhone Health app. New workouts stop importing immediately.
• Health Connect: Disconnect from Profile → Devices (optionally deleting the imported runs), or remove Runcaster's permissions in your phone's Health Connect settings. New sessions stop importing immediately, and any planned workouts we wrote to Health Connect are removed.

Data sharing

We do not sell your data and we do not share it with advertisers or analytics providers. Activity data is sent to our AI provider (OpenAI) only to power the coach features and the quality and safety monitoring described above. Data is shared externally only when you explicitly post a run card to Farcaster.

Storage and retention

We keep data only as long as needed to provide the service. You control deletion and may remove your data by disconnecting Garmin or contacting support. We do not retain data longer than necessary for coaching and (optional) sharing.

Security practices

We use TLS for data in transit and access controls for stored data. We limit access to production systems to authorized personnel only.

Third-party Infrastructure and Sub-processors

• Vercel: Hosting, deployment, and blob storage for share card images.
• Supabase: PostgreSQL database for storing user connections, activity data, training plans, and coach memories.
• OpenAI: AI inference for the coach (chat, plan generation, post-run feedback) and embedding computation for memory dedup. Activity data and chat content are sent to OpenAI's API to generate responses; OpenAI is contractually prohibited from training their general models on this data.
• Open-Meteo: Weather lookup for your runs. A run's approximate start coordinates and start time are sent to Open-Meteo to retrieve ambient conditions (temperature, humidity, wind) for display and coaching context. No account identifiers are included.
• Garmin Connect API: Activity data is received from Garmin via secure webhooks. When you push workouts to your watch, structured workout payloads are sent to Garmin via the Garmin Training API.
• Apple HealthKit and WorkoutKit: On iPhone, the app reads workouts, routes and heart rate from the Health store on your device with your permission and uploads them to our servers over an encrypted connection; planned workouts are scheduled onto your Apple Watch on-device. Apple does not receive data from us.
• Health Connect: On Android, the app reads exercise sessions, their measurements and (on request) routes from Health Connect on your device with your permission and uploads them to our servers over an encrypted connection; planned workouts are written to Health Connect on-device. Google does not receive data from us.

Jurisdiction

This service is operated from the United States.

Contact

For privacy questions or data requests, contact support@runcaster.app.