Skip to content

NOC Downloader IOS app Privacy Policy

The NOC Downloader IOS app is developed by Gavin Engelbert. The privacy policy for that app is listed below.

PRIVACY POLICY NOC Roster Downloader

Last Updated: April 4, 2026

1. Introduction

This Privacy Policy describes how NOC Roster Downloader (“the Application”) handles information in connection with your use of the Application. The Application does not collect, transmit, or share personal data with the developer or any third parties for advertising, analytics, or any purpose other than the specific features described below.

2. Google Calendar Integration

2.1 Data Accessed

When you choose to connect a Google account, the Application accesses the following Google user data through the Google Calendar API:

  • A list of the names and identifiers of calendars associated with your Google account, solely to allow you to select a destination calendar.

The Application does not read, access, or store any calendar event data or any other Google account information.

2.2 Data Usage

Google account data is used exclusively to enable the following in-app features, at your explicit direction:

  • Displaying your calendar list so you can select a calendar to export flights to.
  • Creating new calendars in your Google account.
  • Adding flight schedule events (containing flight numbers, departure airports, and arrival airports) to a calendar you select.

Google user data is never used for advertising, analytics, profiling, or any purpose beyond the specific in-app features described above.

2.3 Data Sharing

The Application does not share Google user data with the developer or any third parties. Flight data added to your Google Calendar is transmitted directly from your device to Google’s servers and is not routed through or stored on any developer-controlled server.

2.4 Data Storage and Protection

The Application stores Google OAuth authentication tokens (access token, refresh token, and token expiry) locally on your device in the iOS Keychain. The iOS Keychain is an encrypted, secure storage system managed by Apple and is not accessible to the developer. No Google user data is stored on any external server controlled by the developer.

2.5 Data Retention and Deletion

Authentication tokens are retained only as long as you remain signed in. You may delete all stored Google authentication data at any time by signing out of your Google account within the Application. Signing out permanently removes all tokens from the device Keychain. Uninstalling the Application will also remove all locally stored data.

2.6 Google’s Privacy Policy

Your use of Google services through this Application is also governed by Google’s Privacy Policy, which can be reviewed at https://policies.google.com/privacy.

3. MyFlightBook Integration

3.1 Data Accessed

When you choose to connect a MyFlightBook account, the Application accesses the following data through the MyFlightBook API:

  • A list of aircraft registered in your MyFlightBook account, solely to allow you to associate a flight log entry with the correct aircraft.

The Application does not read, access, or store any existing logbook entries or any other MyFlightBook account data.

3.2 Data Usage

MyFlightBook account data is used exclusively to enable the following in-app feature, at your explicit direction:

  • Adding new flight log entries to your MyFlightBook logbook. Entries contain flight date, departure and arrival airports, flight duration, landing counts, block times, and crew names, all sourced from your imported roster data.

3.3 Data Sharing

The Application does not share MyFlightBook user data with the developer or any third parties. Flight log entries are transmitted directly from your device to MyFlightBook’s servers and are not routed through or stored on any developer-controlled server.

3.4 Data Storage and Protection

The Application stores MyFlightBook OAuth authentication tokens (access token, refresh token, and token expiry) locally on your device in the iOS Keychain. No MyFlightBook account data is stored on any external server controlled by the developer.

3.5 Data Retention and Deletion

Authentication tokens are retained only as long as you remain signed in. You may delete all stored MyFlightBook authentication data at any time by signing out within the Application, which permanently removes all tokens from the device Keychain.

3.6 MyFlightBook’s Privacy Policy

Your use of MyFlightBook through this Application is also governed by MyFlightBook’s Privacy Policy, which can be reviewed at https://myflightbook.com/logbook/Public/Privacy.aspx.

4. LogTen Pro Integration

The LogTen Pro integration does not require account sign-in and involves no network requests by the Application. Flight data from your imported roster (including flight date, departure and arrival airports, flight duration, aircraft type, tail number, and crew names) is packaged locally on your device and handed off directly to the LogTen Pro app via its published URL scheme. No data is transmitted to any server, and no data is stored by the Application as part of this process.

Your use of LogTen Pro is governed by Coradine Aviation Systems’ Privacy Policy, which can be reviewed at https://coradine.com/privacy-policy/.

5. Roster and Schedule Data

All roster data imported into the Application is stored locally on your device only. The developer has no access to your schedule information. Airline login credentials used to download your roster are used solely for that single request and are not stored or retained by the Application in any form.

6. Data the Developer Does Not Collect

The Application does not collect, transmit, or have access to:

  • Account credentials or passwords for any service.
  • Existing logbook entries, calendar events, or other account content.
  • Personal identification information.
  • Usage data or analytics.
  • Device identifiers or location data.

7. Children’s Privacy

This Application is not directed at children under the age of 13. The Application does not knowingly collect any personal information from children. If you believe a child under 13 has provided personal information through this Application, please contact the developer using the information in Section 9 and it will be promptly removed.

8. Changes to This Privacy Policy

This Privacy Policy may be updated from time to time. The current version will always be available at https://gavleng.com/appprivacypolicy/. Continued use of the Application following any update constitutes acceptance of the revised policy. The “Last Updated” date at the top of this page reflects when the most recent changes were made.

9. Contact

If you have any questions about this Privacy Policy or wish to request deletion of any data associated with your use of the Application, you may contact the developer through the App Store listing or through the Send Feedback link within the Application.