Privacy Policy

FanLine for iOS · Last updated: 2026-05-26

This Privacy Policy explains how the FanLine iOS app ("FanLine", "we", "the app") handles your information. The short version: FanLine does not collect any personally-identifying data. What does leave your device is anonymized crash reports and anonymized usage diagnostics, used solely to fix bugs and understand how the app is used in aggregate. No advertising identifiers are collected and no App Tracking Transparency prompt is shown.

1. Information We Do Not Collect

FanLine does not collect, process, or transmit any of the following:

• Your name, email address, phone number, or any other identifying contact information
• Your location, including precise or approximate GPS data
• Your photos, camera roll, contacts, calendar, or any other personal data Apple's APIs make available
• The Advertising Identifier (IDFA) or any cross-app advertising data — we link only FirebaseAnalyticsCore, not FirebaseAnalyticsIdentitySupport, so no IDFA is collected and no ATT prompt is shown
• Browsing history or activity outside the FanLine app
• The content of your favourites list — which specific races or riders you favourite stays on your device

2. Information Stored Locally on Your Device

The app stores the following data only on your device, never transmitted anywhere:

• Favourite races and riders — items you save for quick access and notifications, stored in Apple's local SwiftData database
• Cached race data — refreshed JSON files (stage results, standings, startlists) downloaded from our hosting endpoint and stored in the app's Documents directory
• Notification preferences — your race-start and stage-start toggles, stored in Apple's UserDefaults
• Purchase entitlement — whether you have unlocked Full Access via the in-app purchase, managed by Apple's StoreKit

You can clear all of this data at any time by uninstalling FanLine.

3. Crash Reports (Firebase Crashlytics)

FanLine uses Firebase Crashlytics, a Google service, to automatically collect anonymized crash reports when the app crashes unexpectedly. We use this data solely to identify and fix bugs that affect real users.

What is transmitted when a crash occurs:

• The crash stack trace and exception type
• Your device model (e.g. "iPhone 17 Pro") and iOS version
• The FanLine app version that crashed
• An anonymized installation ID generated by Firebase — not linked to your Apple ID, name, or any other personal identifier
• Approximate region, derived from your IP address at the time the crash report is sent; the IP itself is not stored

What Crashlytics does NOT collect:

• Your name, email, phone number, or any contact information
• Your precise location or GPS data
• The Advertising Identifier (IDFA)
• The specific races or riders you have favourited
• Any data that would let us or Google identify you personally

4. Anonymous Usage Analytics (Firebase Analytics Core)

FanLine uses Firebase Analytics in its IDFA-free configuration to understand how the app is used in aggregate — how many people open it each day, which screens are most viewed, which features drive upgrades. This data is fully anonymized; we cannot identify you from it.

What is transmitted:

• Standard Firebase Analytics events: app open, session start, screen views (e.g. "Calendar", "RaceDetail", "Settings")
• Custom events specific to FanLine: favorite_added (with a type label of "race" or "rider"), paywall_shown (with a trigger label), and in-app-purchase events handled automatically by Apple's StoreKit
• Your device model, iOS version, and FanLine app version
• An anonymized installation ID and an anonymized app-instance ID, both generated by Firebase and not linked to your Apple ID
• Approximate region, derived from your IP address at the time the event is sent; the IP itself is not stored

What Analytics does NOT collect:

• The Advertising Identifier (IDFA) — we deliberately link only the FirebaseAnalyticsCore SPM product and do not link FirebaseAnalyticsIdentitySupport
• Cross-app behavioral tracking — Firebase cannot link your activity in FanLine to your activity in any other app
• The specific races, riders, or teams you view, favourite, or search for — only the screen names are logged, not the content
• Any contact information, location, or personal identifier

Google's handling of analytics data is additionally governed by Firebase's Privacy Information and Google's general privacy policy.

5. Network Requests

FanLine makes anonymous HTTPS requests to https://fanline-data.web.app/, our static hosting endpoint on Google Firebase Hosting, to fetch refreshed race information (calendar, stage results, standings, route profiles, team rosters) so the app can stay current without an App Store update. These requests carry no app-generated user identifier.

Firebase Hosting's handling of access logs is governed by Firebase's Privacy Information and Google's general privacy policy.

6. Notifications

FanLine schedules notifications locally on your device using Apple's UNUserNotificationCenter. The app does not use Apple Push Notification Service (APNs); no notification content is generated by or transmitted through any server we control.

When you favourite a race or rider, the app schedules a local notification for the morning of each relevant race. Toggling notification permissions for FanLine in iOS Settings will silence them; uninstalling the app cancels all pending notifications.

7. In-App Purchase

FanLine offers one optional in-app purchase that removes the free-tier limit on favourites. This purchase is processed entirely by Apple's StoreKit framework. Apple — not FanLine — receives and processes your payment information. FanLine never sees your credit card, billing address, or Apple ID.

Refunds are handled by Apple per their App Store refund policy. We have no ability to issue or deny refunds directly.

8. External Links

Race detail screens link out to Wikipedia, ProCyclingStats, and official race-organiser websites (e.g. letour.fr, giroditalia.it). These open inside the app in an in-app Safari View Controller — Safari handles its own privacy and may set its own cookies according to your settings; we have no visibility into your browsing within those sessions.

9. Children's Privacy

FanLine is suitable for ages 4+ and does not knowingly collect personal information from anyone, including children. The data collected via Crashlytics and Analytics (Sections 3 and 4) is anonymized and contains no personal identifiers that could be used to identify a child specifically.

10. International Users (GDPR, CCPA, etc.)

FanLine collects no personally-identifying data. The aggregated, anonymized data described in Sections 3 and 4 is most-regulator-treated as non-personal data when it cannot be linked to an individual (as is the case here). You retain all the rights guaranteed by GDPR, CCPA, and similar laws:

• Right to access: personal data on your device is visible in the app; we hold no other personal data about you.
• Right to deletion: uninstall the app to clear all on-device data. Anonymous crash and analytics records cannot be linked back to a specific user, and so cannot be selectively deleted on request — they remain in Google's aggregate dataset.
• Right to portability: there is no personal data to port.
• Right to opt out of sale of personal data: we have no personal data to sell.

11. Data Sources and Attribution

Race information displayed in FanLine is sourced primarily from Wikipedia (CC BY-SA 4.0), with official route profiles from race-organiser websites. FanLine respects the licenses of its source material and provides attribution links in the app.

12. Changes to This Policy

If we change this Privacy Policy materially, we will update the date at the top of this document. Continued use of FanLine after the effective date of a change constitutes acceptance of the updated policy.

13. Contact

Questions about this Privacy Policy or how FanLine handles data? Email slidappquestions@gmail.com.