Privacy Policy

Last updated 21 October 2026

This policy explains how the Kondi service, operated by Brian Kyed, handles your personal data. Questions or privacy requests can be sent to privacy@getkondi.com.

What works today

Today, Kondi supports Sign in with Apple and Google sign-in, a first-party storage choice, iPhone activation and workbook sync. With the storage choice granted and an iPhone activated, the app uploads your plan, summary-only progress and minimal run summaries; the app itself is still in private testing and is not publicly distributed. Claude can connect in two ways. A connection-status connection reports training_data_access: false and cannot read or write training data. A separate approval, which names Claude and the exact categories, lets it read your plan and summary progress and replace your plan. ChatGPT support is still planned.

The current storage choice is called storage-v3. Its exact wording is: “Kondi keeps your training plan and workout instructions, goals, profile and coaching journal, summary progress, notes you write and account timezone in your private cloud workbook. It also keeps a summary of each run, and of any other workout your plan asks for: its identifier, date and time, duration, distance, timezone and UTC offset, deletion status, planned-session link and completion. Duration and distance reveal average pace; timezone is coarse location. Goals, profile and journal include anything you or your AI write. Earlier versions do not expire, and there is no history browser or restore action. This permission includes no GPS or Core Location data. Pace within a workout, heart rate, power, cadence, splits and interval results need a separate workout-history permission. After the app observes and syncs an Apple Health deletion, Kondi removes that workout's measurements and detail from active storage. Its deletion marker, plan assignment, completion and your written notes remain. Removed database values may remain in restricted recovery for up to 30 days. This permission does not share data with Claude or another AI.” An earlier storage choice does not carry over: you must choose again explicitly. You can withdraw the current storage choice in the app; older clients can still withdraw their recorded older choice, and the service continues to accept those withdrawals. Choosing an iPhone does not itself grant storage or AI sharing.

What we collect

Installing Kondi does not send every category below to us. What leaves your iPhone depends on which features are available and the separate permissions you choose. These are the current and planned categories:

• Account details from Sign in with Apple or Google sign-in, such as a provider identifier, name and email address when shared.
• Under the current base workbook storage choice, Kondi can store your training plan (including planned workout instructions), summary-only progress, notes you explicitly write and account timezone.
• A base run summary contains only the workout identifier, date and time, duration, distance, timezone identifier and UTC offset, deletion status, planned-session link and completion status. A run’s average pace follows from its duration and distance; the pace within a run, its route, heart rate, power, cadence, splits and interval results are not part of a base run summary. Kondi treats timezone values as coarse location; base sync does not use Core Location or include GPS coordinates.
• With the separate workout-history (Workout Cloud) storage permission, which creating your workbook asks for alongside base storage, and read-only Apple Health access, the active iPhone can synchronize approved fields for every Apple Health workout type from the rolling previous 365 days, then process new or changed workouts when iOS gives Kondi an execution opportunity. This may include the exact workout identifier and type, start and end time, elapsed and recorded-active duration, distance and speed, heart rate, step count and cadence derived from steps and recorded-active time, running power and dynamics, active energy, a bounded relative-time timeline, and HealthKit-observed workout events. Workout Cloud excludes GPS routes and coordinates, elevation, source, device and sample identifiers, absolute sample times inside the timeline, arbitrary HealthKit metadata, and any claim that observed events are planned intervals. Sync is not guaranteed to be immediate or continuously unattended.
• Technical information needed to keep the service secure and reliable, such as device identifiers, request metadata and error records.
• Your versioned consent decisions and connection records, so Kondi can enforce your choices and keep a record of changes.

Apple Health

Apple Health holds the original workout. You choose which Health categories the app may read on your iPhone and can change those permissions in device settings. Health permission is separate from permission to store data with Kondi and from permission to share it with an AI provider. Kondi does not use iCloud or CloudKit for your health or training data.

storage-v3 covers only the base workbook categories named above. Automatically recorded measurements outside that list stay on your iPhone unless you allow workout-history storage, the separate permission that creating your workbook asks for alongside it. Apple Health access never depends on it. Kondi never creates, changes or deletes an Apple Health workout. Planned workout targets and notes you write may themselves mention a distance, pace, heart rate or other measurement; storing that authored content does not remove those words.

We do not sell health data, use it for advertising, or share it with data brokers.

How we use data

We use personal data to:

• provide your account, consent controls and connection status, and support workout scheduling and history on your phone;
• when you opt in, store the categories you approve; and, only with separate provider-named approval, let that AI read approved workbook data or propose plans;
• protect accounts, prevent abuse, diagnose failures and maintain the service; and
• meet legal obligations and respond to valid legal requests.

AI services you connect

Storage and AI sharing are separate choices. A connection that can reach your training requires its own agreement naming the AI provider, and the page you agree on names each category the connection asks for above one Agree; base storage, workout-history storage and a connection-status approval do not permit that sharing. Plan and progress: Claude can read and change your queue of upcoming sessions, including personal information written in it, your session notes and skip reasons; see which sessions you completed or skipped; read up to twelve recent weeks of summaries of your runs and of other workouts your plan asks for (identifier, date, duration and distance), deletion markers linked to sessions still in the queue, and the period your iPhone last read from Apple Health and whether it held any workout; and see which queue version your iPhone last applied and when it last synced. That category includes no pace within a workout, heart rate, power, cadence, splits, interval results, routes, location or timezone records, the time of day you ran, or your email address. Context: Claude can read and change your goals and training profile, and read and add to your coaching journal, as written. Recorded workouts: while your workout-history storage stays on, Claude can list summaries of workouts already synchronized to Kondi and read one stored workout per call, including heart rate, power and the other measurements that storage keeps; it reads the cloud copy, so its calls do not wake the iPhone, start an Apple Health read or show a Health permission prompt. No category includes GPS routes or coordinates, elevation, source, device or sample identifiers, absolute sample times, arbitrary HealthKit metadata, or a claim that observed events are planned intervals.

Shared data is also governed by that provider's privacy terms. Disconnecting ends future access through Kondi, but does not erase information already in a conversation or retained by the provider. Deleting a workout in Apple Health cannot recall those copies either. You can disconnect without deleting your Kondi account.

Legal bases

Where the GDPR applies, we process ordinary account and service data to perform our contract with you. We process health data only with your explicit consent. We may use legitimate interests for proportionate security and reliability work, and process data where necessary to meet legal obligations. You may withdraw consent at any time; this does not affect processing that was lawful before withdrawal.

Service providers and international transfers

Kondi uses Cloudflare for its website, API and cloud infrastructure. Cloudflare D1 is the service's existing private EU database for account, consent, connection, base workbook and workout-history data. Under the workout-history (Workout Cloud) storage permission, Kondi stores one bounded deterministic-gzip body for each current workout generation, up to 4,096 current workout rows per account. The earlier exact-request Workout Detail feature, now retired, stored one such body per requested activity. Both designs keep their authority and deletion records in D1. These are copies held by the Kondi service, not storage in your own Apple account. Workout Detail and Workout Cloud are not stored in Cloudflare R2.

Apple and Google each provide sign-in. An AI provider receives only data covered by your separate approval for that provider. Providers may process data in countries outside your own. Where required, we rely on recognized transfer safeguards.

Retention and deletion

We keep your account and training data while your account is active and as needed to provide the service. Security records are kept only as long as reasonably necessary. You can request an export or deletion of your account and associated server data by contacting us. Some limited records may be retained where required by law or necessary to establish or defend legal claims.

Deleting a workout in Apple Health removes its automatically recorded observations and Detail or Workout Cloud body from your active Kondi workbook after the app observes and syncs the deletion. A minimal marker containing only the workout identifier and deletion status prevents an older phone or retry from restoring that workout's observations. For Workout Detail, Kondi blocks active cloud reads and writes and retries active D1 deletion until the exact body row is absent. Workout Cloud blocks active reads and writes and transactionally removes the exact active D1 body row. Deletion from active D1 does not mean physical removal from Cloudflare's restricted recovery history.

Historical plan assignments, completion decisions, planned workout instructions and notes you explicitly wrote will remain after a workout deletion. A retained note or plan may still mention a measurement. Deleting a workout does not erase every mention of it or delete your account; you can contact us about deletion of account data or retained authored content.

Active cloud Workout Detail becomes unavailable at the earlier of 30 days after upload and 180 days after the activity started. Kondi starts active deletion 15 minutes before that deadline. Its protected, backup-excluded phone cache has a fixed 180-day cutoff. Withdrawing Claude Workout Detail sharing stops future Claude Detail requests and reads but does not delete a first-party copy still permitted by your separate Workout Detail storage choice. Withdrawing Workout Detail storage starts active cloud deletion. An active Workout Cloud body expires 365 days after the workout ended. Kondi stops reads 15 minutes before expiry, so availability can end at that early fence, and then transactionally removes the active D1 body. Withdrawing Claude Workout Cloud sharing stops future Claude lists and reads but does not delete a first-party copy still permitted by your separate Workout Cloud storage choice. Withdrawing Workout Cloud storage immediately closes new phone processing and cloud reads when the server records it and transactionally removes active Workout Cloud bodies. The iPhone keeps an account-, device-, activation- and consent-bound, backup-excluded Health cursor and crash checkpoint, not a second cloud-body cache. Cloudflare's restricted D1 recovery history, called Time Travel, may retain removed database values for up to 30 days. Those recovery values are not active data and are not available to the app, Claude or another connected AI provider. Kondi does not restore deleted Workout Cloud data or any other D1-resident cloud state from that history. Deletion from active D1 must not be understood as physical removal from recovery history. A database incident may permanently lose all D1-resident state; data still on an iPhone or in Apple Health does not guarantee recovery.

Your rights

Depending on where you live, you may have rights to access, correct, export, restrict, object to or delete your personal data, and to withdraw consent. You may also complain to your local data protection authority. Contact us to exercise these rights.

Security

We use technical and organizational safeguards intended to protect personal data. No online service can guarantee absolute security, so please contact us if you believe your account or data may be at risk.

Children

Kondi is not directed to children under 16, and we do not knowingly collect their personal data. Contact us if you believe a child has provided data to the service.

Changes

We may update this policy as the product develops. We will publish the revised policy here and change the date above. We will provide additional notice when a change materially affects how personal data is used.