Privacy Policy
Your training data deserves precise language.
This policy explains what the current version of 140.6 is designed to process, when information may leave your device, and the limits of those protections.
Live-release status: 140.6 is publicly distributed through Apple’s App Store. This policy must remain aligned with the exact signed release build, production analytics and retention configuration, App Store privacy disclosure, public support process, and qualified legal review.
At a glance
- The current app is designed to work without a separate 140.6 account. Apple, App Store, purchase, and service-provider systems may still hold their own records.
- Training plans, activity records, Fuel entries, race information, health context, settings, and Coach history are designed to be stored primarily on your device.
- Standard planning tries supported Apple Intelligence first. If needed, it may use a configured remote plan service. On-device-only planning avoids the plan server.
- Optional food-photo analysis can send one photo for remote analysis after disclosure and your action. Manual Fuel entry and photo-free barcode lookup remain alternatives.
- Strict zero-data-retention routing is currently disabled. Remote infrastructure and model providers may retain request data under their terms, settings, and legal obligations.
- Product analytics may operate when enabled in the signed release. Its behavior must match the signed build, this policy, and the App Store privacy disclosure.
Information stored on your device
You may provide race goals and dates, training availability and experience, planned sessions, completed activity information, Fuel entries, body and threshold inputs, Check-ins, Pain, Soreness, Sleep, Stress, Recovery context, coach preferences, notes, and privacy settings. The precise set depends on the features and permissions you use.
The current app is local-first: these records are designed to remain in app storage on your device unless a feature clearly requires a permitted system service or remote request. “Local-first” does not mean every operation is local, and it does not control device backups, Apple services, or information you choose to send elsewhere.
If you connect Apple Health, the app may request and process supported workout and health summaries. Apple controls Health authorization and does not expose every individual read-grant state to apps. Denied, unavailable, or missing information remains unknown rather than being treated as zero.
Location, Motion, Weather, and Apple Health
During an in-app workout, optional foreground Location can capture GPS coordinates, distance, elevation, and speed evidence. Optional background Location keeps that capture available when the screen is locked or the app is backgrounded. Motion & Fitness can help identify supported movement and moving-time evidence. These permissions are requested in context and remain separate; if they are denied or revoked, time-only recording remains available.
Captured route coordinates and derived workout evidence are designed to be stored with the local activity record. Temporary recovery checkpoints may also be stored on the device so an interrupted recording can be recovered, then cleared after the finalized activity is saved or the recording is explicitly discarded. Resetting or deleting local app data removes app-held copies, subject to device or platform backups.
If Apple Health workout export is enabled, a completed in-app workout summary, including supported distance and energy totals, may be written to Apple Health. The current app does not export its captured GPS route to Apple Health. Disconnecting Apple Health stops app synchronization and clears the app's pending Health work; records already held by Apple Health and native permissions remain managed in Apple's Health app and under Apple's policies.
Home may use Apple's WeatherKit only when foreground Location is already authorized. It uses recent coordinates to request current precipitation evidence and solar events for the decorative Home atmosphere; it does not request Location solely for weather, use background Location for weather, or send those coordinates through the plan or Coach model routes. Weather evidence is cached only for its bounded freshness period and otherwise falls back to a time-based atmosphere.
Planning, Coach, and remote models
In Standard mode, planning first tries supported Apple Intelligence. If it is unavailable or fails, the app may send minimized, structured context through the configured plan service to a remote model provider. This can include the plan and the limited profile, race, availability, performance, Recovery, Load, Fuel, Check-in, or goal summaries needed for that decision. It is not intended to include provider tokens, API secrets, precise routes or locations, raw Health samples, food images, or unrelated history.
AI can return a bounded plan proposal or user-facing wording. Deterministic code validates proposals, applies constraints, builds the concrete workout, and owns safety rules and calculations. You review proposed Plan changes before confirming them; Coach or Home guidance does not silently change the Plan.
In On-device-only mode, planning uses supported Apple Intelligence followed by deterministic local rules and does not call the plan server. Results may be less personalized or lower quality when supported Apple Intelligence is unavailable.
Remote-retention limit: strict zero-data-retention routing is currently disabled for the configured remote-model path. Serving providers may retain plan request data under their own terms, configuration, abuse-monitoring practices, and legal obligations. Do not enter emergency information, highly sensitive medical details, or information about another person into Coach or free-text fields.
The application service code is designed not to intentionally write full plan prompts, food photos, or model responses to its own application database. This is not a promise that no copies exist: hosting infrastructure, security logs, network services, and model providers may process or retain data under their policies and configuration.
Fuel photos, barcodes, and nutrition estimates
Fuel tracks carbohydrates, fluid, sodium, and calories. You can enter values manually. If you choose remote food-photo analysis, the app presents a disclosure and requests camera access in context; the selected photo is sent through the configured service to a remote model provider to produce an estimate. You review and can correct the estimate before saving.
In On-device-only mode, the image stays local unless you explicitly choose the one-photo “Analyze once” action. Choosing that action authorizes that photo to use the disclosed remote route; it does not change the processing mode for future requests.
For a packaged-food barcode lookup, the barcode digits—not the captured image—are sent to Open Food Facts. Its community-supplied product and nutrition data may be incomplete or inaccurate, so verify it against the packaging before saving.
Analytics and diagnostics
When enabled in the signed release, analytics may use a generated installation identifier and limited product-interaction, experiment, purchase, performance, or diagnostic events to understand reliability and product use. The exact event and property allowlist, consent or opt-out behavior, provider, and retention period must be verified for each production build and disclosed here and in the App Store privacy label.
Configured credentials or development instrumentation do not, by themselves, establish that analytics is active in a production build. The app is not currently making a verified promise of an exact analytics retention period or a universal analytics configuration.
Apple and the App Store may separately process purchase, subscription, crash, and device information under Apple's policies and your device settings.
How information may be used and shared
Information may be processed to provide plans and workouts, record activity and Fuel, calculate Stats and Recovery context, perform requested AI or barcode features, maintain security and reliability, respond to support requests, process purchases, and comply with law.
Depending on the feature and production configuration, information may be processed by Apple and App Store services, hosting and network infrastructure such as Vercel, remote-model routing and serving providers such as OpenRouter and the selected model provider, Open Food Facts for barcode lookups, and any analytics or diagnostics provider enabled in the signed build. Each provider processes data under its own terms, configuration, and legal obligations.
140.6 is not designed to sell personal information. Information may also be disclosed where required by law, to protect rights or safety, investigate misuse, or support a business transaction, subject to applicable law.
Retention, deletion, and access
App records stored locally remain until you delete or reset them, remove the app, or they are otherwise cleared by the device. Copies may remain in device or platform backups until those backups expire or are deleted under the relevant platform settings and policies.
A local deletion or app reset does not itself delete records held by Apple, hosting infrastructure, analytics or diagnostics services, remote-model providers, support systems, or other third parties. Their records follow their policies, configured retention, legal obligations, and applicable access or deletion request processes. We do not promise complete or immediate deletion from those providers.
Where applicable law grants access, correction, deletion, restriction, objection, or portability rights, requests need to use a verified public support channel and the applicable service-provider request processes. This page does not currently publish a verified privacy-contact address.
Children and teen athletes
140.6 is not intended for children under 13. Athletes aged 13 through 17 may be asked to attest that a parent or legal guardian has permitted their use. That checkbox is an unverified attestation; it is not identity verification or verified parental consent.
Age and guardian requirements vary by market and by race organizer. The 13+ rule, teen flow, under-13 reporting process, and guardian disclosures require ongoing qualified legal review for the markets where the app is offered. Athletes and guardians must also check the rules for their event.
Security and international processing
Reasonable technical and organizational safeguards are intended to protect information, but no device, transmission, or service can be guaranteed completely secure. Remote providers may process information in countries other than your own, where privacy laws may differ.
Changes and contact
This policy may change as the product and production configuration change. A revised policy will show a new last-updated date. Material changes should be presented as required by applicable law.
Apple’s App Store identifies RADIANT MANAGEMENT SYSTEMS PTE. LTD. as the app provider. This page does not currently publish a verified privacy-contact address; a public support and privacy-request process should be kept aligned across this page, the app, and the App Store listing.