The short version: RipFir Train has no servers of its own. Your training data lives on your device. We do not collect, sell, or share your personal data, and we do not use analytics, advertising, or tracking SDKs.
RipFir Train ("the App"), developed by Gregory Stevenson ("we," "us," or "our"), is a strength-and-conditioning training app for action sports riders. This Privacy Policy explains what information the App handles and how.
1. Information stored on your device
All of your training information is stored locally on your device and is not transmitted to us. This includes:
- Profile details you enter (height, weight, experience level, chosen sport, training availability)
- Workouts, exercises, sets, reps, and weights
- Training plans, phases, and scheduled sessions
- Personal records, achievements, and progress statistics
- Race events and reminders
We do not have access to this data. It never leaves your device except through the optional integrations described below.
2. Apple Health (HealthKit)
If you grant permission, RipFir Train writes your completed workouts to Apple Health so they count toward your activity and exercise rings. The App does not request read access to your Health data. This exchange happens directly between the App and Apple Health on your device — health data is never sent to us or any third party, and you can revoke access at any time in Settings → Health → Data Access & Devices.
3. Training plan generation
RipFir Train builds your training plan using a language model, which can run in one of two ways:
- On-device (default where supported): On devices that support Apple Intelligence, plan generation uses Apple's on-device language model. Your profile and training context are processed locally and are not sent over the network.
- Bring-your-own Claude API key (optional): If you choose to enter your own Anthropic Claude API key, your training context (sport, experience level, current phase, weeks into your plan, weekly gym/ride frequency, and a summary of your recent workouts) is sent directly from your device to Anthropic's API under your own key, subject to Anthropic's Privacy Policy. RipFir does not receive, store, or proxy this traffic. Your API key is stored only on your device, in the iOS Keychain.
You are never required to provide an API key. You can remove a stored key at any time in the App's AI Engine settings.
4. Subscriptions and purchases
RipFir Train offers optional subscriptions processed entirely by Apple's App Store / StoreKit. We never see or store your payment-card details. Purchases are handled by Apple under Apple's Privacy Policy.
5. Notifications
RipFir Train uses local notifications (workout reminders, race-week alerts, personal-record celebrations) scheduled on your device. These are not push notifications and do not involve any server. You can disable them in the App or in iOS Settings.
6. Information we do not collect
- No analytics, telemetry, or usage tracking
- No advertising identifiers or ad networks
- No third-party trackers or data brokers
- No account or login is required, and we do not collect email addresses except when you voluntarily contact support
7. Contacting support
If you email us at support@ripfir.com, we receive the message you send (including the app version and device model the App attaches to help us troubleshoot). We use this only to respond to your request.
8. Children's privacy
RipFir Train is not directed to children under 13, and we do not knowingly collect personal information from children.
9. Your choices
- Revoke Health or Notification permissions in iOS Settings at any time
- Remove your Claude API key in the App to stop all network requests related to plan generation
- Delete the App to remove all locally stored RipFir Train data from your device
10. Changes to this policy
We may update this Privacy Policy as the App evolves. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, noted in the App.
11. Contact
Questions about this policy? Contact us at support@ripfir.com.
Draft for review. Before publishing: confirm the support email is live and have the final wording reviewed by qualified counsel. This describes the app's behavior as of the current TestFlight build and is not legal advice.