Privacy Policy

Last updated: November 4, 2026

This Privacy Policy describes what information Velox collects, why we collect it, who we share it with, and how long we keep it. We have written it to describe what our software actually does rather than what a template says it might do. Where a practice is imperfect, we say so.

Scope

This policy covers both the Velox mobile application and the Velox website at velox-running.com, including the beta waitlist form. Where a practice applies to only one of them, we say which.

Interpretation and Definitions

Interpretation

The words whose initial letters are capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.

Definitions

For the purposes of this Privacy Policy:

• Account means a unique account created for You to access our Service or parts of our Service.

• Affiliate means an entity that controls, is controlled by, or is under common control with a party, where "control" means ownership of 50% or more of the shares, equity interest or other securities entitled to vote for election of directors or other managing authority.

• AI Assistant means a third-party app, such as Claude or ChatGPT, that You connect to Your Velox account so that it can read Your training plan and edit it. It is described under AI assistants below.

• Application refers to Velox, the mobile software program provided by the Company.

• Company (referred to as either "the Company", "We", "Us" or "Our" in this Privacy Policy) refers to Velox LLC, 6701 Corporate Dr Ste N, Johnston, IA 50131, United States.

• Device means any device that can access the Service such as a computer, a cell phone or a digital tablet.

• Health Data means information the Application reads from Apple Health (HealthKit) with Your permission, and anything We derive from it. It is described under Apple Health below.

• Linked Account Data means information We receive from a Garmin Connect or COROS account You link to Velox, and anything We derive from it. It is described under Garmin and COROS below.

• Personal Data (or "Personal Information") is any information that relates to an identified or identifiable individual. We use "Personal Data" and "Personal Information" interchangeably unless a law uses a specific term.

• Service refers to the Application and the Website together.

• Service Provider means any natural or legal person who processes data on behalf of the Company — third-party companies employed by the Company to host, operate or support the Service. The Service Providers we use are named individually below.

• Training Data means the running and fitness information You give Us or that We generate about Your training: survey answers, prescribed workouts, completed runs, distances, paces, and perceived-effort (RPE) reports.

• Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself.

• Website refers to velox-running.com.

• You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.

What We Collect

Account and identity

• Email address — from the account You create, or from Apple or Google if You sign in with one of those.
• Username — chosen by You, or suggested from the first part of Your email address.
• A user identifier — an anonymous identifier issued by our authentication provider that links Your data together.
• Your name — if You sign in with Apple or Google, they transmit Your display name to Us. We use it only to suggest a username and We do not store it as a separate field.

Training profile

Collected once during onboarding, and used to build and scale Your plan:

• Date of birth (also used to enforce our 16+ age requirement)
• Sex
• Self-reported running experience level
• Injury history — a count of major injuries and how recently the last one occurred
• Longest recent run
• Goal race date
• How many days per week You run, and which days You are available
• A recent 5k time

If You enter them in settings, We also store Your resting heart rate and a maximum heart rate You set yourself.

Training data

• The training plan We generate for You — months, weeks, days and individual workouts, with their prescribed distance, pace and intended effort.
• What You report after each run — perceived effort (RPE), distance, pace, and whether You completed the session. If the run was matched to a run from Apple Health, Garmin or COROS, its distance and pace come from that run.
• Adjustments We make to Your plan, and the reason recorded for each.
• Metrics We derive from the above, such as pace estimates and effort calibration.

Apple Health

Only if You connect Apple Health. The app asks iOS for permission, and You choose in iOS which categories to allow. Velox only reads from Apple Health; it never writes to it.

The app reads only data recorded by Apple Watch or iPhone. Runs and readings that other apps, such as Garmin Connect, COROS or Strava, write to Apple Health are not read. To bring in runs from a Garmin or COROS watch, link that account directly (see Garmin and COROS below). Earlier versions of the app also read data other apps had written to Apple Health.

What the app reads and sends to Us:

• Running workouts — start and end time, duration, distance, energy burned, and the heart rate, speed, distance, step count, running power, stride length, ground contact time and vertical oscillation samples recorded during the workout; pause and lap events; the workout's metadata; the name of the app that recorded it; and the recording device's name, manufacturer, model and software version. Only running workouts are read. New workouts are sent in the background as they appear, and past running workouts are sent the first time You connect.
• Where a workout started — if You allow route access, the app reads the first point of the workout's route, and only that point. It is sent at full precision and used only to look up the weather for that run (see Location below). The rest of the route is never read.
• Daily wellness — resting heart rate, heart rate variability (HRV), VO2 max, and sleep, including sleep stages. These are read for Your whole Apple Health history on first connection.

Velox does not read Your date of birth, sex or any other personal characteristic from Apple Health.

What We keep, and what We discard. Each upload is held as received only until it has been processed, and is deleted within about an hour of that. From it We keep:

• A summary of each run: start time, distance, elapsed and moving time, average heart rate, energy burned, elevation gain, the app that recorded it, the model of the device that recorded it (for example "Apple Watch"), and the weather at its start (temperature, feels-like and conditions).
• The intervals We detect within the run, with the distance, time, pace and heart-rate figures for each.
• Heart-rate reference values We derive from Your runs, such as a threshold heart rate and a maximum heart rate, and Your resting heart rate as a 7-day median.
• An estimate of how hard a run was, calculated from its heart rate. We record it only to compare it with the effort You report; it is not shown to You or anyone else, and it does not change Your plan.
• Your daily resting heart rate, HRV, VO2 max and sleep stages.

We do not keep the second-by-second sample streams, the start coordinates, the other device details or the workout metadata once the upload is deleted.

How We use it. To match Your runs to the right day of Your plan and log them, to measure what You actually ran against what was prescribed, to derive the heart-rate reference values above, to add weather to a run, and to generate coaching text as described under Automated Processing below.

What We never do with Health Data. See What We never do with data from Your devices, below.

Stopping access. You can disconnect Apple Health in the app under Settings, Integrations, and turn off Velox's access at any time in iOS Settings under Health. Either stops new data reaching Us; neither deletes what We already hold. To have that removed, delete Your account or contact Us.

Garmin and COROS

Only if You link the account. You can link a Garmin Connect account, a COROS account, or both, from the app. Linking opens Garmin's or COROS's own sign-in and consent page, where You choose to give Velox access; We never see Your Garmin or COROS password. Naming Garmin and COROS here describes where data comes from; it does not mean either company endorses Velox. Velox only reads from these accounts; it never writes to them.

Linking Garmin includes Your consent to AI use. Before the Garmin sign-in opens, the app tells You that numbers from Your Garmin runs are used by AI models (Anthropic's Claude, running on Amazon Web Services' Bedrock service) to write Your coaching insights, and are never used to train AI. You cannot link Garmin without agreeing, and You withdraw that consent by disconnecting Garmin (see Disconnecting below). There is no separate setting for it.

Garmin. Garmin sends Us data for activities You record after You link the account; it does not send anything from before. We receive:

• Activities — for each activity, a notice naming it (its activity type, name, start time and the device that recorded it) and a one-time link to its original activity (FIT) file. We download the file once and read from it the summary, laps and second-by-second distance, speed, altitude and heart rate. We do not read the GPS route or location points the file contains.
• Activity summaries — Garmin also sends a summary of each activity, which can include its distance, heart rate and start location. We read from it only whether the activity was uploaded through Garmin Connect's website or is part of a multisport activity (We skip both), and discard the rest.
• Daily health summaries — Your resting heart rate for each day and Your overnight heart rate variability (HRV). Garmin's daily summaries also contain other figures, such as steps and stress; We read only resting heart rate and HRV, and discard the rest.
• Account notices — Your Garmin user identifier, which permissions You have shared with Velox, and notice when You withdraw them.

COROS. When You link COROS, and about every 15 minutes after that, Velox asks COROS for Your runs from the last 14 days, and up to four times a day for Your wellness figures from the last 7 days. We receive:

• Runs — for each run, its type, start time and start coordinates, and a link to its original activity (FIT) file. We download the file and read from it the summary, laps and second-by-second distance, speed, altitude and heart rate. We do not read the GPS route. The start coordinates are used only to look up the weather for that run, as for Apple Health.
• Wellness — Your daily resting heart rate, Your overnight HRV with COROS's normal range and baseline for You, and COROS's current VO2 max estimate.

What We keep, and what We discard. An activity file is read in memory and never stored. A notice or listing as received is held only until it has been processed, and is deleted within about an hour of that. From it We keep the same things as for Apple Health: a summary of each run (for Garmin, without weather), the intervals We detect, the heart-rate reference values and effort estimate We derive, the device model (for example "Forerunner 965"), and Your daily resting heart rate, HRV and, for COROS, VO2 max. We do not keep sample streams, routes or location.

Your tokens. Linking gives Us access tokens for Your Garmin or COROS account. We store them encrypted, use them only to fetch the data described here, and delete them when You disconnect.

How We use it. The same way as Health Data: to match Your runs to Your plan and log them, to measure what You ran against what was prescribed, to derive heart-rate reference values, to add weather to a run, to show the device that recorded each run, and to generate coaching text as described under Automated Processing below.

Disconnecting. You can disconnect Garmin or COROS at any time in the app under Settings, Integrations. For Garmin, We then tell Garmin to end Velox's registration for Your account, so Garmin stops sending Us data; if Garmin cannot be reached, We keep trying for up to 30 days. For COROS, We ask COROS to revoke Velox's access. Either way We delete Your tokens. Runs and daily figures We already hold are kept, so Your training history stays intact; to have them removed, delete Your account or contact Us. You can also withdraw Velox's access from within Garmin Connect, which stops new data reaching Us. Disconnecting Garmin withdraws Your consent to AI use: no new Garmin data reaches Us, and so none reaches the models. Garmin runs already stored stay part of Your training history, and coaching text about the days they cover can still draw on them.

What We never do with data from Your devices

This covers Health Data and Linked Account Data alike:

• We do not sell it.
• We do not use it for advertising, marketing or data mining, or share it with data brokers.
• We do not use it, or let anyone use it, for decisions about credit, insurance or employment.
• We do not use it to train, test or evaluate AI models. It can be used to generate coaching text, as described under Automated Processing below.
• We share it only as this policy describes: with the Service Providers named under Who We Share It With, and — for a run's distance, rounded as described under Leagues — with the members of a league You have chosen to join; and, except for anything from Garmin, with an AI Assistant You connect, as described under AI assistants below. League members never see a run's pace, duration, heart rate or the device that recorded it.

Leagues

Leagues are optional. Joining a league season requires Your explicit, versioned consent, given at the moment You join. A league has four to six members, so up to five opponents, and You face one opponent at a time.

What league members see about You throughout and after the season: Your username; Your age-graded grade, which We calculate from Your date of birth, sex and current 5k estimate and which therefore reflects them; and Your results — wins, losses, points and scores.

What an opponent sees about Your sessions. Only sessions You log while the season is running are shared — nothing from before it started or after it ends. For those, an opponent can see the session type, the day it was logged, Your total miles for that day (to a tenth of a mile), the effort Your plan prescribed, and summaries built from those sessions: the distance, rounded to whole miles, and reported effort of Your last two sessions of the same type; how widely Your reported effort has varied on that type over the last 14 days; and two scores of how heavy Your training load has been over the last three days and across the season. If a session was matched to a run from Apple Health, Garmin or COROS, its distance comes from that run. Opponents never see a session's pace or duration, Your heart rate, the device that recorded it, or any other Health Data or Linked Account Data.

Your reported effort (RPE). Your reported RPE is shared with Your league opponents in two ways. For the session an opponent is guessing, it is revealed only after they lock in their guess. For Your other sessions shared during the season, it can appear in the summaries of Your recent runs that an opponent can look at while guessing (in the app, "scout cards"), whether or not they ever guessed that session.

Notifications to opponents. When You log a run, Your opponent may receive a push notification that You have logged one. It does not include Your name or any of the run's details.

When session sharing stops. Sharing Your sessions requires three things to hold at once: Your profile visibility is set to public, Your consent for that league has not been revoked, and the season is running. Profile visibility is public by default; You can set it to private in settings. Doing so stops further sharing of Your sessions at the next read; what an opponent has already read stays read. Your username, grade and results remain visible to that league's members.

Simulated runners. A league may include simulated runners that We operate (see our Terms of Service). They are not real people. You are told when You join that some opponents may be simulated runners, but the app does not mark which ones are. A simulated runner's fitness level is set close to the grade of the real runners in the league, and its training log is generated from its own Velox plan, not copied from anyone. It takes part in reads the same way a member does, so it can lock a guess and see Your reported RPE; that information stays with Us.

Records We keep. Every read of Your data by an opponent is recorded — who read it, whose data, which league, which session, and when. We keep that record, and the league statistics We compute from reads, for 12 months after the league ends, and delete them if either account is deleted. The league's fixtures, guesses and results are kept as the league's history; if You delete Your account, Your identifier in them is replaced with a pseudonym and Your reported RPE is removed from them.

If We revise the consent text, its version number changes. A member who consented under an older version is asked again at their next enrolment, never mid-season.

AI assistants

Only if You connect one. An AI Assistant is an app such as Claude or ChatGPT that You connect to Your Velox account through the Model Context Protocol (MCP), so that You can ask it about Your training and have it change Your plan. We do not operate these apps, and they are separate from the coaching text Velox generates itself, described under Automated Processing below.

You approve each app. Connecting starts in the AI Assistant, which sends You to velox-running.com/oauth/consent. There You sign in to Velox and are shown the app's name, what it will be able to do, and the site that approving returns You to. Nothing is shared unless You choose Allow, and You approve each app separately. Anyone can give an app any name, so approve only an app You started connecting yourself. Approving gives the app an access token for Your Velox account; it never receives Your password.

What a connected app can read:

• Your training plan — its phases, and for each day the prescribed workout type, sessions, distance and effort, and, for a day not yet run, a pace and duration.
• Your past days — each day's prescription, whether You completed or skipped it, and a summary of the run: its type, distance, duration, pace and Your reported effort (RPE). For a run from Apple Health or COROS, the distance, duration and pace come from that run.
• What it needs to edit a co-coached plan — if Your plan is co-coached, meaning You set sessions yourself and Velox suggests the rest, each upcoming day's sessions, which of their details You have set, any workout You wrote in the workout builder, and the warnings Velox's planning rules raise about the plan.

What a connected app can do. On a co-coached plan, it can change Your days after today, Your weeks and Your race goal. Every change goes through the same checks as an edit in the app, and the app must first try the change and receive Velox's result, including any warnings, before it can save it. It cannot change today or past days, switch Your plan between co-coached and generated, or change a plan Velox generated. Velox cannot tell whether You asked for a particular change, so check what an AI Assistant proposes before You let it save. Its access token works only for these tools; it is refused by the rest of the Velox app's features, such as Your settings, leagues and account deletion.

What is never shared with an AI Assistant:

• Data from Garmin. For a day that holds a run recorded by Garmin — whether it reached Us from Garmin directly or from a Garmin app through Apple Health — the app sees only what Your plan prescribed and that the day was completed: no distance, duration, pace, effort or other figure from the run. If We cannot check where a day's runs came from, the request fails rather than risk sending Garmin data.
• Health metrics — heart rate, HRV, VO2 max, sleep or any other daily wellness figure, from any source.
• Raw device data — activity files, laps, sample streams, location, and the device or source that recorded a run.
• Your account details — our tools do not return Your email address, name, username, date of birth, sex or other onboarding answers.
• Everything else — coaching insight text, coach-chat messages, league data, and the tokens for accounts You have linked.

Once data reaches the app. What a connected app receives is held by the company that provides it, and that company's own privacy policy and terms govern what it does with it, including whether it keeps Your conversations or uses them to train its models. Velox does not control this and is not responsible for it. Read the app's privacy policy before You connect it.

Disconnecting. You can see the apps You have connected, and disconnect any of them, in the app under Settings, Integrations, AI assistants. Disconnecting cuts off that app's access immediately; to connect it again You must approve it again. Disconnecting does not delete what the app has already received; ask its provider to remove that.

Records We keep. Our authentication provider records each app You approve, with its name, the site it returns to and when You approved it; this is the list You see in the app. When You disconnect an app, We record which app and when, so that its access tokens are refused from then on. Requests from a connected app are logged like any other request, as described under Diagnostics, logs and crash reports below.

Location

Your current location. The app asks iOS for permission to use Your location while You are using it, the first time You open the home screen. Nothing is collected unless You allow it, and You can turn it off in the app or in iOS settings at any time. When allowed, the app asks iOS for Your location to within about a hundred metres, and Your device rounds the coordinates to two decimal places — roughly one kilometre of precision — before sending them to Us. We use them to fetch local weather, to show the name of Your nearest city (looked up on our own servers, not by a third party), and to work out Your local date so the right day of Your plan is shown. We do not store Your coordinates in our database, and We blank them out of our request logs. Our servers keep them in memory for up to a day to avoid repeat lookups. Request logs written before October 9, 2026 can still contain them, and are kept as described under How Long We Keep It.

Where a run started. If You have connected Apple Health and allowed route access, the start point of each running workout reaches Us at full precision, as described under Apple Health. If You have linked COROS, COROS gives Us the start point of each run. We use it only to look up the weather for that run, then keep only the weather. The coordinate is deleted with the upload, within about an hour of processing. We do not use location from Garmin.

Time zone. Your device time zone is sent with most requests whether or not location is enabled, so that Your plan follows Your local calendar. We store Your current time zone with Your preferences, so that league days and Your weekly analytics follow Your local calendar too. It also appears in request logs.

Push notifications

Only if You allow notifications. The first time You open the home screen, the app asks iOS to ask You; nothing is sent unless You allow it there. When You do, We store the push token Apple issues for Your device, and whether it is a development or production token, against Your account. We use it only to send notifications through Apple's push service. We send two kinds:

• Run complete — when a run from Apple Health, Garmin or COROS reaches Us soon after You finish it, We ask how hard it felt. The message carries a short line about the run, such as its distance, its pace against Your plan, or Your total for the week. Like any notification, it can show on Your lock screen.
• League read — telling You that Your opponent has logged a run. It names no one.

The token is removed when You turn notifications off in the app, sign out, or delete Your account, or when Apple tells Us it is no longer valid.

Preferences

Theme, language, unit system, profile visibility, time zone, whether You have enabled location and notifications, whether runs from Your devices are logged to Your plan automatically, and whether Your effort comes from Your watch, Your own rating, or manual entry.

Coach chat

We store the messages You send to the in-app coach for 12 months, then delete them automatically. We keep them to understand what runners ask so we can improve the coach's answers. We store only the text You type, never the training data or device data sent to the coach with it. They are stored under a one-way cryptographic reference rather than Your account identifier, so they are not directly linked back to You in that store. We do not store the coach's replies to You.

Insight text the coach generates about Your month, a specific workout, a completed run, or Your effort and training load is cached against Your account so it does not have to be regenerated.

Planning and workout assistants

The workout builder and the planning screen each have an assistant. You type what You want, and it writes or changes a workout, or the days of Your plan, for You to keep or discard. It uses the same model as the coach, as described under Automated Processing below.

We keep a record of each request for 90 days, then delete it automatically. A record holds what You typed, what We sent the model with it, the assistant's reply, whether You kept the result, whether and how the request failed, and how long it took. What We send the model can include numbers from Your devices, such as Your weekly mileage. If You import a workout from a photo, PDF or text file, We record only the file's type and size, never the file. Records are stored against Your account and deleted with it.

How We use these records. To find where the assistants go wrong and fix them. Our team reads them only through internal reporting, in which accounts are identified by a pseudonym. A record that contains any Health Data or Linked Account Data is never used to test or evaluate the assistants; only a record with none can become a test case.

Diagnostics, logs and crash reports

• Server logs. Our servers log requests and errors. These log lines include Your user identifier, and request log lines include the request address, which can contain Your time zone; coordinates and push tokens are blanked out of it. They may also include the network address a request came from and the version of the app that made it. For a Garmin delivery We log how many items it contained, never its contents. On rare occasions, when data You send Us fails validation, a fragment of it can appear in an error log line. Logs are stored in our hosting provider's logging service.
• App logs. When the app hits a warning or an error, it sends that log line to Us automatically, without any action from You. Before sending, the app removes access tokens and email addresses from the text and restricts what metadata may be attached. These lines go to our server logs only.
• Error reports. Unhandled server errors, and a sample of requests for performance measurement, are sent to our error-tracking provider. These include the stack trace, the route, the response status, timings, recent server log lines from the same request, and Your user identifier. They deliberately exclude request bodies, local variables and query strings — the last of these specifically so that location coordinates are not captured. The app itself contains no crash-reporting library; its product analytics are described below.
• Device information. App version, operating system version, and Your device's hardware model (for example, a string like iPhone15,2). We also store against Your account the app version and build You last used, and the day We last saw it, so that We know which versions are still in use.

Product analytics

Unless You turn it off, the app sends usage events to our product-analytics provider so that We can see which parts of Velox runners use and where new runners get stuck. Each event records a screen You opened or an action You took — signing up or signing in, reaching each step of the onboarding survey and finishing it, logging a run, connecting a device, joining a league, sending a message to the coach, or starting a new plan — together with Your user identifier, the app version, and Your device model and operating system version. A few events carry a category: whether a logged run came from Your watch or was entered by hand and whether it was planned, which device You connected, which onboarding step You reached, and whether a coach message was about a month or a workout.

Events never contain Your run data or anything from Apple Health, Garmin or COROS — no pace, distance, duration, heart rate or other values — and never the text of coach messages. The app does not record Your screen or Your taps, and our provider is configured not to locate You from Your network address or keep it. Analytics are on by default, and You can turn them off at any time in the app under Settings; while they are off, the app sends no analytics events.

Bug reports

If You submit a bug report from within the app, We collect the title, Your description, any steps to reproduce, Your app and OS version, Your device model, and up to 4,000 characters of recent app logs. If You tick the box asking for updates, We also include Your email address.

Bug reports are filed as issues in our source-code repository so that our engineers can act on them. Please see "What survives deletion" below.

Website and beta waitlist

If You join the beta waitlist on our Website, We collect the email address You submit, and We send that address to our team in a notification email through Resend. Our Website host records standard web request logs.

If You accept analytics cookies in the banner on our Website, We use Google Analytics to see how visitors use the Website. Google Analytics sets cookies and receives information such as the pages You view, how You reached them, Your general location, and details of Your browser and device. If You decline, or do not answer, these cookies are not set and Google Analytics does not load. You can change Your choice at any time using Cookie Settings in the Website footer. The Website does not use advertising cookies, and We have turned off the advertising features of Google Analytics. This choice applies to the Website only, not the app.

What We do not collect

We do not track You across other companies' apps or websites. We do not use advertising identifiers. We do not sell Your Personal Data. Beyond the product analytics and the optional Website analytics described above, We use no behavioural-tracking service, and those analytics are never used for advertising. We do not read Your full workout routes from Apple Health, Garmin or COROS, and We do not write anything to Apple Health, Garmin or COROS.

How We Use Your Information

• To build and adapt Your training plan. This is the core purpose. Your survey answers, reported runs, perceived effort and, if You connect them, Health Data and Linked Account Data drive what We prescribe next.

• To operate Your account — registration, sign-in, and account management.

• To show You Your own data, including derived analytics such as how closely Your reported effort matches what was prescribed.

• To run leagues You join, as described under Leagues above.

• To answer AI Assistants You connect, and make the plan changes they ask for, as described under AI assistants above.

• To generate coaching text, as described under Automated Processing below.

• To fetch weather for Your planned run and for runs imported from Apple Health or COROS.

• To send notifications You have turned on.

• To contact You about Your account, security matters, or a bug report You asked to be updated on.

• To find and fix defects, using the diagnostics and bug reports described above.

• To understand how the app is used, using the product analytics described above, so that We can fix confusing steps and decide what to build next.

• To improve the Service. This includes using stored coach-chat messages to improve how the coach retrieves and answers questions, and internal reporting over Training Data, Health Data and Linked Account Data — in which accounts are identified only by a pseudonym — to find problems and improve how our plans adapt. This reporting is used only by our own team. It is never used to train AI models, and it is used to test the assistants only through records that contain no Health Data or Linked Account Data, as described under Planning and workout assistants. Data from Garmin, and anything derived from it, is never used to train, test, evaluate or improve any AI model.

• For business transfers — if We are involved in a merger, acquisition or asset sale, Your Personal Data may be among the assets transferred.

• To comply with law, enforce our terms, or protect the rights and safety of Velox, our users, or the public.

Automated Processing and AI

Velox uses large language models to generate written coaching insight, to answer questions You ask the in-app coach, and to run the planning and workout assistants. This matters enough to spell out. Numbers from Your devices — Apple Health, Garmin and COROS — can be part of what the model receives.

What is sent. When We generate insight or answer a chat message, We send a structured summary of the relevant part of Your training to the model: the workout, run or month in question, its distances, paces, intended effort and phase, along with Your experience level, goal race date, how many days a week You run, and Your injury count and how long ago it was. Insight about a completed run, and insight or chat about a workout You have already run, also include, for a run from Apple Health, Garmin or COROS, its local start time, duration, average heart rate, and the intervals We detected in it with their distance, pace and heart rate. Insight about Your effort and training load includes summaries of how Your reported effort compares with what was prescribed. For chat, We also send the conversation transcript and the passages retrieved from our coaching reference material. Your chat message text is additionally sent to a separate embedding model in order to find relevant reference passages.

What the assistants send. When You ask the planning assistant, We send Your request, the days of Your plan it may change with their sessions and the details You set, and a summary of You as a runner: Your goal race and date, the weekly targets You set, Your weekly mileage over the last six weeks, how Your reported effort compared with what was prescribed over the last 14 days, Your pace for each training zone, and any races in the weeks it is editing. When You ask the workout assistant, We send Your request, the workout as it stands and Your pace zones. Importing a workout sends the photo, PDF or text file itself.

What is not sent. We deliberately exclude Your age and sex from these prompts. We do not send Your email address, name, username, location, league data, the device that recorded a run, or any daily wellness figures — no resting heart rate, HRV, VO2 max or sleep.

Consent and withdrawing it. For Garmin, linking the account is Your consent to this use, and disconnecting Garmin in the app withdraws it, as described under Garmin and COROS above. For Apple Health and COROS there is currently no setting that turns this off while keeping the connection. Disconnecting stops new data from that source reaching Us, and so reaching the models. For every source, runs already stored stay part of Your training history, and coaching text can still draw on them until You delete Your account.

Not used to train models. We never use Health Data or Linked Account Data to train, test or evaluate AI models, and We do not put it into any dataset for doing so. Under AWS's terms for Bedrock, the prompts We send and the text that comes back are not used to train AWS's or the model providers' models.

Which providers. Both models run inside Amazon Web Services' Bedrock service: a Claude model provided by Anthropic for the written text, and an Amazon Titan embedding model for retrieval. Your data is processed under our agreement with AWS.

No automated decisions with legal effects. These models produce training suggestions and explanatory text. They do not make decisions about You that produce legal or similarly significant effects.

Who We Share It With

We do not sell Your Personal Data, and We do not share it for advertising. We use the following Service Providers, and We name them rather than describing them in the abstract:

• Amazon Web Services — hosting, database storage, logging, and the AI models described above. Substantially all of Your data, including Health Data, is stored here.

• Supabase — authentication. Holds Your email address and sign-in credentials or linked provider identity, and sends the verification codes for sign-up and email changes. Also stores the beta-waitlist email addresses collected on our Website.

• Anthropic (via AWS Bedrock) — generates coaching text from the training summary described above, which can include numbers from Your devices.

• Apple — Sign in with Apple, if You use it; Apple Health, from which the app reads with Your permission; Apple's push notification service, which receives Your push token and the notification; and Apple WeatherKit, which receives coordinates in order to return a forecast — Your rounded current location, and the full-precision start point of runs imported from Apple Health or COROS. No identifier of You is sent to WeatherKit, and the request comes from our servers rather than Your device.

• Google — Sign in with Google, if You use it; and Google Analytics on our Website, if You accept analytics cookies.

• Sentry — error and performance monitoring, as described under Diagnostics above.

• PostHog — product analytics, as described under Product analytics above, on servers in the United States.

• GitHub — receives bug reports You submit, as issues in our repository.

• Resend — delivers the notification email our team receives when someone joins the beta waitlist on our Website. It handles the email address submitted. Resend is not used to email You.

Garmin and COROS are sources, not recipients: if You link one, it sends Your data to Us, and We send it only the requests needed to fetch that data and to end Velox's access when You disconnect. We do not send them Your training plan or anything else about You.

If You join a league, the data described under Leagues above is shared with the other members of that league.

If You connect an AI Assistant, the data described under AI assistants above is shared with that app. You choose it, and its provider is not our Service Provider: its own privacy policy and terms govern what it does with that data.

We may also disclose Personal Data where required by law, in response to valid legal process, to enforce our terms, to investigate fraud or a security incident, or to protect the rights, property or safety of Velox, our users, or the public.

How Long We Keep It

We describe our actual practice. We are deliberately not publishing a retention schedule we do not enforce.

• Your account, training data and Health Data are kept for as long as Your account exists. There is no automatic expiry. If You want it gone, delete Your account — see below.

• Apple Health uploads, and Garmin and COROS notices, as received, including workout start coordinates and sample streams, are deleted within about an hour of being processed. Garmin and COROS activity files are never stored.

• Garmin and COROS tokens are kept until You disconnect or delete Your account.

• Coach chat messages are automatically deleted after 12 months.

• Planning and workout assistant records are automatically deleted after 90 days.

• League read records and league statistics are automatically deleted 12 months after the league ends. League fixtures, guesses and results are kept as the league's history.

• Push tokens are kept until You turn notifications off, sign out or delete Your account, or until Apple reports them invalid.

• Server logs, error reports, product-analytics events and bug-report issues do not currently have an enforced retention period. We are working on this. We would rather tell You than publish a period we do not keep to.

• Google Analytics event data for our Website is kept for 2 months. Aggregated reports that do not identify You may be kept longer.

• Beta-waitlist email addresses are kept until We remove them on request or the waitlist is retired. This includes the notification emails in our team's inboxes. Resend may also keep delivery records under its own retention practices.

We may retain information for longer where We are required to by law, or where it is needed to resolve a dispute or enforce our agreements.

Deleting Your Data

You can delete Your account from within the app. If You have linked Garmin, We first tell Garmin to end Velox's registration for Your account. Deleting then permanently removes, from our database and our authentication provider:

• Your account, email address and username
• Your training profile — date of birth, sex, experience, injuries, goals, availability and heart-rate settings
• Your entire training plan and history, including every reported run
• Everything We hold from Apple Health, Garmin and COROS — run summaries, detected intervals, heart-rate reference values, effort estimates and daily wellness — and Your Garmin and COROS tokens
• Your preferences and push tokens
• Your stored coach-chat messages and generated insight text
• Your league consents, league statistics, and every record of reads of or by You
• Any plan adjustments and coach-review records

What survives deletion

We would rather be exact about this than imply deletion is total:

• League history. Fixtures, guesses and results You took part in remain, with Your identifier replaced by a pseudonym and Your reported RPE removed, so that other members' league records stay intact.

• A recent Apple Health upload, or Garmin or COROS notice, that had not yet been deleted remains for up to about an hour.

• Your link at Garmin or COROS. If Garmin cannot be reached when You delete Your account, We still delete Your tokens, and Garmin may go on listing Velox as connected until You remove it in Garmin Connect; it can no longer deliver to Your Velox account. Deleting Your account does not notify COROS: disconnect COROS in the app first if You want Velox's access revoked there too.

• Bug reports You filed remain as issues in our source-code repository, including their description, device details, attached logs, and Your email address if You asked for updates. Contact Us if You want one removed.

• Server log lines, error reports and product-analytics events containing Your user identifier remain with our hosting, error-monitoring and analytics providers until they age out of those systems. Contact Us to have Your analytics events removed sooner.

• Database backups retain a copy of Your data until the backup itself expires.

• A beta-waitlist email address is stored separately from Your app account and is not removed by deleting Your account. Contact Us to have it removed, including from the notification emails in our team's inboxes.

• Data an AI Assistant has already received stays with that app's provider. Ask it to remove that data.

• Your data in Apple Health, Garmin Connect and COROS is Yours and stays there; deleting Your Velox account does not touch it.

Your rights to access, correct, delete and export

You can ask Us for access to Your Personal Data, for a copy of it to take elsewhere, to correct it, or to delete it. This includes Health Data and Linked Account Data. There is no in-app export yet: email Us at the address below from the address on Your account, say what You want, and We will do it and reply. You can also delete Your account in the app at any time, as described above.

Your Choices

• Apple Health access is off until You connect it. You can disconnect it in the app, and turn it off, in whole or by category, at any time in iOS Settings under Health.

• Garmin and COROS are off until You link them, and can be disconnected at any time in the app.

• AI Assistants are off until You approve one, and each can be disconnected at any time in the app under Settings, Integrations, AI assistants.

• Location is only used if You allow it when iOS asks, and can be turned on or off at any time in the app or in Your device settings.

• Notifications are sent only if You allow them when iOS asks, and can be turned off in the app or in Your device settings.

• Product analytics are on by default and can be turned off at any time in the app under Settings → Share usage analytics.

• Website analytics are off until You accept them, and You can change Your choice at any time using Cookie Settings in the Website footer.

• Profile visibility is public by default and can be set to private in the app. It controls whether league members can see Your sessions.

• Leagues are optional; nothing is shared with other runners unless You join one.

• Bug-report emails. Your email address is only attached to a bug report if You tick the box asking for updates.

• Correcting Your information. You can currently change Your username, Your email address (for email sign-in accounts), how many days per week You run, and Your resting and maximum heart rate from within the app. Other onboarding answers — date of birth, sex, experience, injury history, longest run, goal date and available days — are not yet editable in the app. Contact Us and We will correct them for You.

Security

We use commercially reasonable measures to protect Your Personal Data, including encrypted connections between the app and our servers, encrypted connections to our database, encrypting the Garmin and COROS tokens We hold, and restricting access to production systems. No method of transmission over the Internet or method of electronic storage is completely secure, and We cannot guarantee absolute security.

International Transfers

Velox is operated from the United States and Your information is processed and stored there. If You access the Service from outside the United States, You understand that Your information will be transferred to, stored and processed in the United States, where data-protection laws may differ from those in Your jurisdiction.

Children's Privacy

Our Service is not directed to anyone under the age of 16, and We do not knowingly collect Personal Data from anyone under 16. If You are a parent or guardian and believe Your child has provided Us with Personal Data, please contact Us and We will remove it. If We become aware that We have collected Personal Data from anyone under 16 without verified parental consent, We take steps to delete it.

Links to Other Websites

Our Service may contain links to sites We do not operate. We have no control over, and assume no responsibility for, the content or privacy practices of those sites. We advise You to review the privacy policy of every site You visit.

Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When We do, We will post the updated policy on this page and change the "Last updated" date at the top. If We make a material change to how We use Your Personal Data, We will also notify You in the app or by email before it takes effect. Changes are effective when posted, and continuing to use the Service after that means You accept them.

Contact Us

If you have any questions about this Privacy Policy, or want to exercise any of the choices described above, You can contact us:

• By email: support@velox-running.com