Privacy policy
Run2O
1. Overview
Run2O is a local-first running tracker for iPhone and Apple Watch. It does not require a Run2O account and does not include advertising, cross-app tracking, or a social feed.
Run2O needs to process sensitive fitness and location information to record a run. By default, that information is stored in the app’s sandbox on your device. iPocket does not operate a separate server that receives your run history. Data leaves the device only when you choose or use an Apple system feature that requires it, such as Apple Health, optional iCloud sync, WeatherKit, MapKit, StoreKit, or the system share sheet.
The current app privacy manifest declares no developer-collected data, no tracking, and no tracking domains. This does not mean the app processes no data: run and sensor information is processed on your devices to provide the features described below.
2. Data Run2O processes
Depending on the features and permissions you use, Run2O may process:
- Precise route coordinates, timestamps, accuracy, speed, and altitude
- Distance, moving and elapsed time, current and average pace, calories, cadence, elevation, and GPS quality
- Heart rate, metric samples, kilometer splits, pause intervals, and recording-device information
- Free-run or interval settings, stage goals, repetitions, progress, and completed interval segments
- Run notes and a weather summary associated with the run location
- Apple Health workout identifiers and synchronization state
- Local preferences, entitlement state, active-session recovery data, and iCloud synchronization metadata
This information is used to record the workout, recover an interrupted session, present live metrics, build run history and statistics, show run details, synchronize data you choose to sync, and generate exports you request.
3. Location, motion, weather, and maps
Run2O requests precise location to measure distance and record your route. During an active run, background location allows recording to continue when the screen is off or another app is open. Motion and pedometer data can support cadence, elevation gain, and distance estimates when available.
When a location is available for a run, Run2O may automatically enrich the record with weather. It sends a coordinate from the run to Apple WeatherKit and stores the returned temperature, apparent temperature, condition, humidity, and wind summary with that run. There is currently no separate weather switch. MapKit receives the map region needed to display or render a map; Run2O draws the route overlay and may cache a route snapshot locally.
You can deny or later revoke permissions in system Settings. Without location, Run2O cannot provide a normal GPS route recording; other denied permissions may make the corresponding metrics or features unavailable.
4. Apple Health
Apple Health access is optional and permission-controlled. Run2O may:
- Write a completed running workout and related route and metric information to Apple Health
- Read workouts marked as created by Run2O, together with their routes and heart-rate samples, to restore history and show details
- Store the associated Apple Health workout identifier in the local run record so duplicate saves, restoration, and supported deletion choices can be coordinated
Health permissions can be changed in Apple Health or system Settings. Data already saved in Apple Health is controlled separately from the Run2O app database. Removing Run2O does not automatically remove existing Apple Health records.
5. Optional iCloud synchronization
iCloud sync is off unless you enable it. When enabled, Run2O uses CloudKit in your Apple account and the app’s private database container to synchronize completed runs and interval settings across your devices. Synced data can include routes, raw metric samples, heart rate, notes, weather, interval data, Apple Health identifiers, and deletion markers.
Run2O does not use the CloudKit public database for this feature and does not turn your runs into public or social records. Turning sync off stops future synchronization but leaves local copies and any existing iCloud copies in place. Use the app’s delete-cloud-data or cross-device deletion controls when you intend to remove cloud copies.
6. Apple Watch and paired-device communication
The Apple Watch app can record independently and can coordinate live workout state, interval progress, metrics, and save or discard decisions with the paired iPhone. This communication uses Apple’s HealthKit workout mirroring and WatchConnectivity frameworks; iPocket does not relay the live session through a separate Run2O server.
7. Exports and sharing
Sharing is always initiated by you. Run2O can create:
- A visual run-summary image
- CSV files containing selected workout metrics, notes, weather, splits, and interval results
- GPX files containing route coordinates and timestamps for runs with a trustworthy route
Before sharing, review the file and destination carefully. Routes, timestamps, heart rate, notes, and other workout details can reveal sensitive information. After you save or send an export, the destination and recipient control their copy, and Run2O cannot retrieve it for you.
8. Run2O Pro purchases
Run2O offers an optional one-time Pro purchase for advanced interval features. Apple processes payment, purchase restoration, refunds, and transaction records through the App Store and StoreKit. iPocket does not receive your complete payment-card details or Apple account password.
9. Data security and retention
Local data relies on Apple’s app sandboxing, device data protection, and your device passcode. iCloud, Health, StoreKit, WeatherKit, and MapKit are Apple services subject to your Apple account and Apple privacy settings.
Local run records remain until you delete them, clear app data, or remove the app. Apple Health records, iCloud copies, and exported files are separate copies and may remain after local deletion unless you remove them through the relevant service or destination. No method of storage or transmission can guarantee absolute security.
10. Your choices and deletion controls
You can:
- Use the app without creating a Run2O account
- Decline or revoke Location, Motion & Fitness, and Health permissions
- Keep iCloud sync off, turn it off later, or use the in-app cloud-data deletion control
- Delete an individual run locally or across synced Run2O devices
- Separately choose whether supported run deletion should also remove the associated Apple Health workout
- Manage Health permissions and Health data in Apple’s Health app
- Avoid Apple Health, exports, and sharing; weather enrichment has no separate switch and depends on an available run location
- Delete exported files from their saved destination
- Remove Run2O to clear local app data from the device
Some copies, such as exports already sent to another person, are outside Run2O’s control.
11. Children’s privacy
Run2O is not designed specifically for children under 13. We do not knowingly use the app to collect personal information from children on iPocket-operated servers. A parent or guardian should supervise a child’s use of location, health, export, and sharing features.
12. Policy updates
If Run2O’s data handling or service providers change materially, we will update this policy and may provide notice through the website, app release notes, or another appropriate channel. The updated policy takes effect on the date shown on this page.
13. Contact
If you have questions about Run2O privacy or data deletion, contact:
- Email: contact@ipocket.xyz