This policy explains how the developer (the “Provider”) of the iOS application “Train Net” (the “App”) handles user information.
01Principles
- We collect only the minimum information needed to provide and improve the App.
- Location processing is completed on the device; detailed movement traces are never transmitted externally.
- Every third-party service (SDK) the App uses, and what it receives, is disclosed in this policy.
02Location data
- Purpose — Location data is used solely to determine which railway segments you rode. It is never used for, or shared with, advertising or analytics.
- How it flows — The GPS trace between start and stop is processed on the device, and the raw trace is discarded once ride segments have been determined. Only the result — which segments of which lines you rode — is kept.
- Background use — While recording, the App may request “Always” or “While Using” location permission so tracking continues with the screen off. No positioning occurs while you are not recording.
- Your control — You can change location permissions at any time in iOS Settings.
03Information we process
| Information | Source | Purpose / storage |
|---|---|---|
| Location (while recording only) | Device GPS etc. | Ride segment detection. Processed on device; raw trace discarded after detection |
| Ride records (segments, dates, distance) | Generated as detection results | Log, map and statistics display. Stored on device (and in your iCloud with Pro) |
| Purchase information (receipt, anonymous ID) | App Store / RevenueCat | Verifying and restoring Pro purchases |
| Usage and crash data | Firebase SDK | Improving features and fixing bugs. Never includes location or personally identifying content |
| Advertising identifiers (IDFA) etc. | Google Mobile Ads SDK | Serving ads. Personalization only with your consent (ATT) |
04Third-party services (SDKs)
The App uses the following services. For details of what each receives, see their privacy policies.
| Service | Purpose | Policy |
|---|---|---|
| Firebase Analytics / Crashlytics (Google) | Usage measurement and crash reporting | Google Privacy Policy |
| Google AdMob | Serving ads | Google Advertising Policy |
| RevenueCat | In-app purchase management | RevenueCat Privacy Policy |
| Apple iCloud (CloudKit) | Syncing ride records (Pro, optional) | Apple Privacy Policy |
Analytics events are limited to aggregate values (durations, segment counts) and line codes. Station names, notes, photos and location itself are never sent.
05Ads and tracking consent
- The App may show ads to support its free features.
- Personalized ads that involve tracking across apps and websites are shown only with your permission via iOS App Tracking Transparency (ATT). If you decline, non-personalized ads are shown instead.
- You can change ATT permission at any time in iOS Settings → Privacy & Security → Tracking. In some regions, a consent dialog required by law (such as GDPR) is shown.
06iCloud sync
Pro’s iCloud sync stores your log in the private database (CloudKit) of your own Apple account. Only your account can access this data; the Provider cannot view or retrieve it. You can stop syncing and delete the data from the App and from iOS iCloud settings.
07Retention and deletion
- Ride records are kept on your device until you delete them. Deleting the App removes all on-device data.
- Data in iCloud remains under your control and can be deleted from iOS settings.
- Crash and usage data is deleted automatically according to Google’s retention periods.
08Sharing with third parties
The Provider does not sell or provide user information to third parties except as required by law. Transmissions to the SDKs listed in this policy are limited to what each service needs to function.
09Children’s privacy
The App is not directed at children under 13, and we do not knowingly collect personal information from children.
10Changes to this policy
Material changes to what we collect or why will be announced on this site or in the App. The latest version is always published on this page.
11Contact
For questions about this policy or your data, please use the contact listed on the Support page.