Privacy Policy

About this policy

Updated September 28, 2026, for Coaster Tool 1.1. Developer: Yangyuxuan,Xiao. Coaster Tool requires no separate app account. It records and analyzes rides without providing safety assessments. Optional purchases and cloud backups use your App Store and iCloud accounts respectively.

Data processed on device

The app processes motion, available pressure and relative altitude measurements, optional precise GPS locations, timestamps, ride names, parks, seats, notes, favorites, settings and selected photos on device. Only photos chosen in the system picker are copied. Original EXIF/GPS metadata is removed from copies; library originals are unchanged. Note drafts are stored separately in a local directory excluded from system device backups. On update, the previous preferences copy is removed only after the draft is successfully saved there. Failures retain the original and offer a retry. Ordinary settings and ride-name, park and seat drafts may be included in system device backups.

Watch transfers and local storage

Watch recordings transfer to the paired iPhone via WatchConnectivity. Local recordings, photos, Watch originals, the inbox and note drafts are excluded from system device backups; ordinary preferences may be backed up. Before migrating or reinstalling, manually create an iCloud backup without notes, or export the recordings you want to keep. Recording JSON keeps notes; photos must be saved separately.

Manual iCloud backup and restore

Manual iCloud backup and restore are available for free, without a purchase or purchase restoration. Only when you tap “Back up to iCloud now” does the app create an independent snapshot of recordings already saved on this iPhone and save it to your current iCloud account. Purchasing recording capacity, restoring a purchase or opening the page does not upload recordings automatically. This feature does not perform automatic backups or two-way sync.

New snapshots contain raw motion samples, pressure and relative altitude, precise GPS locations, timestamps, ride names, parks, seats, four-channel forces, calibration, analysis ranges, favorites and photos. They preserve recording identifiers and Watch source digests for duplicate detection. All notes, app settings, unsynced Watch recordings, Watch originals and the inbox are excluded. Local notes remain, but cannot be recovered from new snapshots. Recording JSON exports you initiate still include notes.

Backups use your own iCloud Drive storage, with storage and transfer services provided by Apple. The developer cannot access your iCloud Drive. You need to sign in to iCloud, enable iCloud Drive and have available space. The system schedules uploads; a local write to the iCloud Drive folder does not confirm a completed upload. Check the cloud status before changing devices or uninstalling the app.

You choose and confirm a snapshot to restore. The app adds only missing records that have not been deleted on this device and keeps existing edits. Unsupported or damaged snapshots are not imported, and cloud originals are kept. Changing iCloud accounts clears the visible backup list; results from the previous operation are not committed locally.

Restore remains subject to local recording capacity. If there is not enough room for all records to be added, the app adds none. You can free space or increase capacity and retry; the cloud snapshot stays unchanged.

Backups include the complete raw samples of all saved recordings, beyond the selected recording or analysis range. Trimming the analysis range does not remove GPS or other samples outside that range from a snapshot. Watch recordings must first transfer successfully and be saved on iPhone to be included. Opening the backup page reads the existing snapshot list and upload status without creating a new snapshot.

In-app purchases and restoring purchases

The free local capacity is 50 recordings. Apple in-app purchases can raise the total to 100 or unlimited recordings. Capacity purchases are one-time and non-consumable, not subscriptions; prices are shown by the App Store. Each tier is charged separately, and upgrades cost the full displayed price without credit for earlier purchases. iCloud backup and restore are free. Capacity purchases do not add iCloud storage or change recording-duration or file-size limits.

Apple processes payment. On your device, the app uses StoreKit product information, transaction and product identifiers, and purchase or revocation status to verify capacity entitlements; the highest valid tier applies. Entitlements are checked at launch, when returning to the foreground and on transaction updates. Only tapping “Restore purchases” starts the purchase restoration flow, which may ask you to authenticate your App Store account. This does not upload ride records, locations or photos to the developer. The developer does not receive your payment card details or Apple Account password and runs no server receiving transactions.

Apple separately processes account, payment and purchase data and may provide the developer with purchase and refund reports that do not directly identify you. Deleting the app does not erase Apple’s transaction records. See App Store & Privacy.

Use “Restore purchases” on the Recording space purchase screen. Capacity entitlements follow the App Store account used for the purchase; backups follow the current iCloud account. These accounts may differ. Restoring purchases does not automatically upload recordings or restore backups. A refund or revocation returns capacity to the remaining valid tier or the free 50 recordings, keeping local recordings and cloud snapshots. Existing recordings remain available to view, edit, export and delete; new records must fit within the current capacity.

See the Apple Standard End User License Agreement (EULA) for app terms, and Apple Account and iCloud privacy information for iCloud service data processing.

Exports and sharing you control

PNG, CSV and four-array JSON contain no GPS coordinates. Recording JSON includes raw locations, sensor data, calibration and notes. Replay photos are not included in these exports and must be saved separately.

You initiate sharing. Files go to the apps or recipients you choose; you manage exported copies.

Retention and deletion

Local recordings remain until you delete them. Deleting an iPhone recording and its photo does not delete Watch originals, exports or iCloud snapshots. Successful sync does not automatically delete Watch files. Deleting the app from a device removes its local data.

Each manual backup keeps an independent snapshot. Deleting local recordings, closing the app or obtaining a refund does not delete cloud copies. Manage or delete snapshots in Files → iCloud Drive → CoasterTool → Backups-v1. Older snapshots may contain notes and are not automatically changed or deleted. Restoring a supported older snapshot can recover its notes; a new backup excludes them.

Local deletion markers retain record identifiers and, where applicable, Watch source digests to prevent late Watch transfers or restore operations from recreating deleted records. Uninstalling removes those markers, so records in older snapshots can still be restored manually after reinstalling or on another device. You and your chosen recipients manage exported copies.

These system device backup exclusions apply to current local storage. They do not retroactively clear previously created system device backups, which may still contain note drafts saved by older versions. Manage those backups through the system’s backup controls.

Permissions and withdrawal

Change motion and location permissions in system settings. Revoking access or stopping capture does not delete saved copies; delete the relevant recordings to remove them. After recording starts in the foreground with location permission, iPhone continues background location use when the screen locks or you switch apps, with a system location indicator. Watch can also record in the background with location permission. Without it, foreground recording remains available on both devices, but entering the background stops and saves the recording.

Service providers

The developer runs no server collecting ride records. The app has no ads, third-party analytics SDKs or cross-app tracking. Apple provides MapKit, App Store in-app purchases and optional iCloud Drive services, and handles related data under its privacy policy. GitHub Pages hosts the website and may process request information such as IP addresses. The site has no analytics scripts or tracking cookies. Apple and GitHub privacy statements are linked below.

The website stores only your manually selected language preference in browser local storage for future visits. “Use browser language” clears this preference. It is not used for tracking.

Contact and updates

For privacy questions, contact the developer through GitHub Issues or by email. If your question concerns an issue using the app, include the device model, OS version (iOS/watchOS), app version, a description of the problem, expected and actual results, and specific steps to reproduce it in your issue or email. GitHub Issues are public; whichever method you use, do not include precise locations, private photos or raw recordings. Policy changes will update the date.

Apple Privacy Policy · GitHub Privacy Statement

Contact developer (public issues) · Email feedback: xiaoyangyuxuan@126.com