FlyPrep Privacy Policy

Posted on Edited on

FlyPrep Privacy Policy

Last updated: September 6, 2026

Welcome to FlyPrep (hereinafter referred to as “this App”). This Privacy Policy explains how we collect, use, store, share and protect information, and the rights you have in relation to that information.

The operator of this App (hereinafter referred to as “we”) is an independent developer. You may contact us at wonglvy1997hk@gmail.com. We respect your privacy and aim to comply with applicable privacy laws, including the EU General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act as amended by the CPRA (CCPA/CPRA), and the California Online Privacy Protection Act (CalOPPA).

Please read this Policy before using the App. You must tap Agree in the in-app privacy dialog to continue. If you tap Disagree (Android) or leave the App without agreeing (iOS), we will not treat you as having accepted this Policy. Simply installing the App does not constitute consent.

This App is a local scheduling and reminder tool. We do not operate a user-account system and we do not upload your schedule content to our own servers. Third-party SDKs (Google) process limited device and advertising data as described below.

  1. Definitions
    1.1 Key terms
    This App: the FlyPrep application on Android and iOS.
    We / operator: the independent developer of FlyPrep, reachable at the email in Section 9.
    You: the natural person using the App.
    Personal data / personal information: information relating to an identified or identifiable natural person (GDPR) or “personal information” (CCPA/CPRA), including device identifiers processed by SDKs.
    Schedule data: schedules, nodes, template graphs, reminder settings, time-zone favorites and related content you create. This is stored on your device.
    Local preferences: appearance (light/dark/system), color palette, 12/24-hour format, and the version of this Policy you accepted. Stored on your device.
    SDK: a third-party software development kit. Google’s privacy terms apply to SDK processing (see Section 3).
    Offline processing: processing completed on your device without sending schedule data to our servers.

    1.2 Third-party privacy documents
    Firebase (Analytics and Crashlytics): https://firebase.google.com/support/privacy
    Google AdMob / advertising: https://policies.google.com/privacy
    How Google uses data from partner sites and apps: https://policies.google.com/technologies/partner-sites
    Google User Messaging Platform (UMP) / consent messages: configured in our AdMob / Funding Choices account and presented by Google’s SDK.

  2. Information we process locally (not uploaded to our servers)
    This App is designed as an offline productivity tool. We do not collect your schedule content on our servers. Apart from the SDKs in Section 3, the App does not upload schedule data, names, contacts, or precise GPS location to us.

    2.1 Schedule data and local preferences
    Scope: schedule nodes and times, templates, reminder levels, time-zone favorites, and local preferences listed in Section 1.1.
    Purpose: offline schedule management, reverse countdown from a takeoff time you enter, and reminders you configure.
    Storage: on-device databases and preference stores (for example Room and DataStore on Android). You can edit or delete individual schedules in the App. You can delete all local App data by clearing the App’s storage in system settings or uninstalling the App.
    Accounts: the App has no registration or sign-in. There is no cloud account to delete. Uninstalling or clearing App data deletes local schedule data.

    2.2 Device backup
    On Android, the system may include App data in the device’s backup (the App currently allows standard backup). Backed-up data stays under your Google Account / device backup settings, not on a FlyPrep server. You can disable backup in system settings if you do not want schedule data included.

    2.3 Permissions and system capabilities (Android and iOS as applicable)
    The App requests only what reminders need. Each sensitive permission is explained in the App before the system prompt. You may deny optional permissions; reminder features that depend on them will be limited or fall back (for example, a notification instead of an overlay).

    Notifications (including promoted / live-progress notifications where the OS supports them): deliver start/end alerts, progress, and alarm notifications for schedules you created.
    Exact alarms / Alarms & reminders: fire reminders at the time you scheduled, including when the App is in the background.
    Display over other apps (Android overlay): optional. Shows a floating countdown for Medium reminders while you use other apps. The App does not record your screen or other apps, and does not place ads in the overlay.
    Full-screen intent (Android): show the alarm dismiss screen when the device is locked or the screen is off.
    Foreground service (Android, alarm ringing): keep the alarm sound playing until you dismiss it. This service is not used as a general “keep-alive”.
    Boot completed (Android): after reboot, re-register alarms that have not yet fired.
    Wake lock (Android): briefly wake the device to handle a scheduled alarm.
    Set alarm / query clock apps (Android): optional path to open the system Clock app to create a system alarm.
    Internet, network state, and Wi-Fi state: allow SDKs (ads, analytics, crash reporting) and loading this Policy in a browser. Core scheduling works offline; ads and SDK reporting require a network.
    Advertising ID (Android AAID / iOS advertising identifier as used by Google ads): read by Google’s advertising SDK for ad serving and measurement, subject to UMP and device ad settings. The App’s own code does not use your advertising ID for schedule features.
    Alarms (iOS AlarmKit, where the OS supports it): Strong and Medium reminders that ring with a system-alarm experience. The App shows an in-app disclosure before the system AlarmKit prompt.
    Live Activities (iOS): optional Medium-reminder countdown on the Lock Screen or Dynamic Island. You can disable Live Activities in iOS Settings → FlyPrep.

    The App does not request SMS, call log, contacts, camera, microphone, or precise location.

    You may withdraw permission later in system settings (notifications, alarms, overlay, and so on). After withdrawal, related reminder functions stop; processing already completed remains lawful.

  3. Information processed by third-party SDKs
    We integrate Google SDKs. Those providers determine their detailed practices. They may transfer data to countries where they operate (see Section 7). We do not sell your personal information. Google advertising may constitute “sharing” for cross-context behavioral advertising under CCPA/CPRA as described in Google’s policies.

    3.1 Google Firebase Analytics (Android; iOS reserved / not fully wired in all versions)
    Data types (typical): app interaction events, device and app version, instance identifiers, and identifiers Google associates with Analytics (which may include advertising identifiers depending on OS settings).
    Purpose: understand feature usage and improve stability and product quality.
    Policy: https://firebase.google.com/support/privacy
    Opt-out: use device settings that limit analytics / advertising; you may also stop using the App. We do not currently provide a separate in-app Analytics toggle.

    3.2 Google Firebase Crashlytics (Android; iOS reserved / not fully wired in all versions)
    Data types (typical): crash stack traces, device model and OS, App version, and diagnostic state at crash time. Crash reports are not your schedule titles or node lists.
    Purpose: diagnose and fix crashes.
    Policy: https://firebase.google.com/support/privacy

    On Android, Analytics and Crashlytics collection is off by default and is turned on only after you accept this Policy in the App. iOS Analytics / Crashlytics remain reserved / not fully wired in all versions. If you do not accept this Policy, disagree in the dialog and stop using the App.

    3.3 Google AdMob and Google User Messaging Platform (UMP)
    Data types (typical): advertising ID, IP address (which Google may use to infer approximate region—not a GPS permission from this App), device and app information, and ad interaction (impressions, clicks). AdMob may serve personalized or non-personalized ads depending on consent and device settings.
    Purpose: show banner and interstitial ads in the App UI (not on the alarm dismiss screen and not in the overlay). Measure ads.
    Policies: https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites

    Consent sequence:

    1. You accept this Privacy Policy in the App.
    2. Where Google requires it (including the EEA, UK and Switzerland), UMP shows Google’s consent / privacy message before ads are requested.
    3. The App initializes the ads SDK and loads ads only if UMP reports that ads may be requested (canRequestAds).
    4. If Google requires a privacy-options entry, the App shows Privacy options (advertising privacy options) in the Profile tab so you can change or withdraw ad consent.

    You may also limit personalized ads in device settings (for example “Opt out of Ads Personalization” / reset advertising ID on Android, or tracking-related settings on iOS). App Tracking Transparency (ATT) on iOS, if shown by the OS or a future App update, is an additional Apple prompt and is not a replacement for this Policy or UMP.

  4. Legal bases (EEA / UK / similar)
    Where GDPR applies, we rely on:
    Consent: the in-app Privacy Policy dialog (on Android this also enables Firebase Analytics and Crashlytics); UMP consent for advertising / personalization where Google requires it; optional system permissions (notifications, overlay, exact alarms, AlarmKit, Live Activities).
    Performance of a contract / steps at your request: storing and running the schedules and reminders you create on your device.
    Legitimate interests (where applicable and not overridden by your rights, and only after you have accepted this Policy): diagnosing crashes via Crashlytics so the App remains usable. You may object using Section 9.

  5. Children
    The App is a productivity tool for adults, including professional flight-prep workflows. It is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal data from children. The App is not enrolled in Google Play’s Designed for Families program. If you believe a child has provided data via SDKs, contact us and we will work with Google’s deletion processes where applicable.

  6. Retention and deletion
    6.1 Local data
    Kept until you delete the relevant schedule in the App, clear App storage, or uninstall. We cannot remotely wipe your device.

    6.2 SDK data
    Retention follows Google’s policies for Firebase and AdMob. We do not operate a separate cloud copy of your schedules.

  7. Security and international transfers
    Local schedule data is stored in the App’s private storage, accessible to the App (and to the OS backup system if enabled).
    SDK data may be processed on Google’s infrastructure, which may be outside your country. Google states that it uses appropriate transfer mechanisms (such as Standard Contractual Clauses) as described in Google’s privacy documentation. We do not control Google’s data centers.

  8. Your rights
    8.1 Local data
    Access and correction: view and edit schedules and settings in the App.
    Deletion and restriction: delete schedules in the App, or clear App data / uninstall.
    No data portability of a cloud profile: there is no FlyPrep cloud account. You may screenshot or manually copy local content if you need a copy.
    Withdraw permission: system settings for notifications, alarms, overlay, and similar.

    8.2 SDK and advertising data
    Use UMP Privacy options in Profile when shown; use Google’s privacy tools and device ad settings; or email us (Section 9). We will forward deletion or access requests that we cannot fulfill ourselves to the extent the SDK provider allows.
    CCPA/CPRA: we do not sell personal information for money. We do not discriminate against you for exercising privacy rights. To opt out of “sharing” for advertising, use UMP privacy options (when required), device ad settings, and Google’s ad settings.
    GDPR: you may request access, correction, deletion, restriction, objection, and (where applicable) portability of personal data we control. You may lodge a complaint with your supervisory authority. For data Google controls as an independent controller, exercise rights with Google as well.

    8.3 Where to find this Policy in the App
    Open the Profile tab and tap Privacy policy (not a separate “About” page).

  9. Contact
    Email: wonglvy1997hk@gmail.com
    We aim to respond within one month (we may extend as permitted by law for complex requests). GDPR and CCPA time limits apply where those laws apply.

  10. Changes
    We may update this Policy. We will change the “Last updated” date and, for material changes, require you to accept a new in-app version before continuing. Please review this page when prompted.

Effective date of the original publication of this URL: August 8, 2026
This revision: September 6, 2026