MetarBoard Wind — Privacy Policy

1. Location Data

• What: Your device’s approximate location (latitude and longitude), requested at kilometer-level accuracy.
• When: Only when you grant “When In Use” location permission. The app calls requestLocation() (a single one-time fix), not continuous tracking.
• Why: To find airports near your current position and display them in the Nearby Airports list.
• Storage: Location data is held in memory only for the current session. It is never saved to disk, uploaded to our servers, or shared with third parties.
• Your Choice: You can deny or revoke location permission at any time in Settings. The app remains fully functional — you can search for airports by ICAO code without location access.

2. Analytics Data (Firebase Analytics)

• What: Anonymous usage events describing how you interact with the app. Events include: airport selected, search performed, weather data source used, favorites added/removed, theme changed, tip jar interactions, and settings opened. Each event may include parameters such as ICAO codes and product identifiers.
• When: As you use the app. Events are batched and sent periodically by the Firebase SDK.
• Why: To understand which features are used, identify problems, and improve the app.
• What We Do NOT Collect: We do not collect your name, email, account information, advertising identifiers, or precise location via analytics. Automatic screen tracking and user property collection are disabled — only explicit event calls are sent.
• Third Party: Analytics data is processed by Google Firebase. See Google’s Privacy Policy.

3. Crash Reports (Firebase Crashlytics)

• What: Automatic crash reports including stack traces, device model, OS version, and app state at the time of a crash.
• When: When the app crashes or encounters a fatal error.
• Why: To identify and fix bugs.
• Third Party: Crash data is processed by Google Firebase.

4. Performance Data (Firebase Performance Monitoring)

• What: App startup time and network request latency metrics.
• When: Automatically sampled during normal app usage.
• Why: To monitor and improve app performance.
• Third Party: Performance data is processed by Google Firebase.

5. Purchase Data

• What: In-app purchase transactions for the optional tip jar (consumable products). The app logs the product identifier and display price of completed tips to analytics.
• When: When you choose to make a tip jar purchase.
• Why: To process your purchase and understand tip jar usage.
• Storage: All purchase processing and payment information is handled entirely by Apple through StoreKit. We never receive or store your payment details, Apple ID, or billing information.

6. Data We Do NOT Collect

MetarBoard Wind does not collect any of the following:

• No personal information (name, email, phone number, address)
• No account or login credentials (the app has no accounts)
• No advertising identifiers or ad tracking
• No photos, contacts, or other device data
• No precise location tracking or location history
• No user-generated content

7. Third-Party Services

MetarBoard Wind uses the following third-party services:

• Google Firebase (Analytics, Crashlytics, Performance) — Usage analytics, crash reports, performance monitoring. See Google’s Privacy Policy.
• Apple StoreKit — In-app purchase processing. See Apple’s Privacy Policy.
• NOAA Aviation Weather Center — Weather data (METAR/TAF). Public US government API, no user data sent beyond airport ICAO codes.
• FAA Aeronautical Information Services — Airport diagram PDFs. Public US government API, no user data sent beyond chart identifiers.

8. Data Retention

• Location data: Memory only, discarded when the app closes.
• Favorites and settings: Stored locally on your device via UserDefaults. Never transmitted to any server.
• Analytics and crash data: Retained by Firebase per Google’s standard retention policies (typically 14 months for analytics, 90 days for crash reports).

9. Children’s Privacy

MetarBoard Wind does not knowingly collect personal information from children under 13. The app does not require an account and does not collect personally identifiable information from any user.

10. Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected by an updated “Effective Date” at the top of this document. Continued use of the app after changes constitutes acceptance of the updated policy.