Pocket Flight Deck Privacy Policy

Effective date: 29 September 2026. Version: 1.1.


Pocket Flight Deck is developed and published by AYBEK TAKABAYEV, an individual developer located in Uzbekistan, operating under the name AybekTB. AYBEK TAKABAYEV is responsible for the processing performed by the developer as described in this policy and acts as controller where applicable data protection law uses that term. Google and other services may have separate responsibilities for their own processing.

Privacy questions and data requests: atb.energo@gmail.com

This policy describes how the Pocket Flight Deck Android app uses data. The app displays movement parameters using the phone’s satellite positioning data and allows users to save flight recordings. A separate Pocket Flight Deck account is not required.

The app is distributed through Google Play in countries and regions selected by the developer. Availability may differ by country, device and Google Play requirements.

The app is intended for users aged 13 and over and is not directed at children under 13. The developer does not request a date of birth or verify a user’s age. Flight recordings are processed locally as described above. If data from a child under 13 is sent to support, contact the email above so the developer can consider deletion and any necessary further action. Minors’ rights and the conditions for processing their data depend on applicable law; an intended audience of 13+ does not imply adulthood in all countries.

The developer does not knowingly solicit personal data from children under 13. Where local law requires parental or guardian authorisation for processing a minor’s data, that requirement applies. The 13+ audience label does not replace such requirements.

With your permission, the app accesses precise location, altitude, speed, direction of movement, measurement times, accuracy estimates and available satellite information. This information supports the instruments, globe position, route calculations and flight state estimates. Demonstration mode uses simulated data.

During a recording you start, the app saves coordinates, times, available movement parameters, signal quality information, the selected route, estimated flight phases and recording events. Algorithm versions and calculation settings are also saved to support interpretation of recordings.

During an active recording, location access may continue while the app is minimised or the screen is off; The recording uses an Android foreground service with a recording notification; where it is displayed depends on Android version and notification permissions. You can stop recording manually and revoke location permission in Android settings. Without permission, live readings are unavailable, but demonstration mode remains available.

Before first accessing location, the app explains its use and then requests Android permission. Before first recording, it separately explains recording while the app is in the background. You can stop recording and revoke permission in Android settings. Acknowledging this policy is not consent to all data processing. Where applicable law requires separate consent, it is requested separately.

Flight recordings and settings are stored locally on the device. The app does not automatically upload flight recordings to a developer server. The developer has no automatic or remote access to local recordings and receives them only if you voluntarily send them, for example for support. The app contains no advertising or analytics SDKs and does not send usage statistics to the developer.

The app obtains live satellite positioning through Android LocationManager and the GPS provider, not through FusedLocationProviderClient. Android and device-level positioning services may operate under their own settings and rules.

Exporting creates a file in a location you choose. If you select cloud storage or send a file through another app, that service processes the data under its own rules. Exports may contain precise coordinates and travel times.

Files you import are used for viewing and replaying data. Import and export take place at your request.

Google Play and Android may process information related to installation, store operations and diagnostics under Google’s policies and device settings. For example, crash and ANR reports may be sent to Google from devices whose users have opted to share usage and diagnostics data. This differs from uploading flight recordings to the developer; the app does not include its own crash reporting SDK. The developer may receive diagnostic information made available through Google Play Console. Diagnostic information that you voluntarily send to support is handled under section 7. The current internal test builds also write local Billing diagnostic messages containing response codes, purchase counts, acknowledgement state and only the last five digits of an order number when present. They do not log purchase tokens, full receipts or account details and do not automatically upload these messages to the developer.

Pro is a one-time, non-consumable purchase through Google Play. The app uses the Google Play Billing Library to purchase Pro, retrieve pricing, query current purchases, acknowledge delivery and restore access. These operations may require internet access and an available Google Play service. No separate Pocket Flight Deck account is created.

Google processes payments under its terms and privacy policy: https://policies.google.com/privacy. The app does not receive your payment card number or Google password. The developer may have access to order information and financial reports that Google Play provides to merchants.

The app receives purchase information: product identifier, app package, purchase token, purchase and acknowledgement states, purchase time and order identifier when present. The signed purchase receipt and its digital signature are stored locally in encrypted form using Android Keystore for verification and offline Pro access. The token is part of this receipt and is not used only once. The developer does not operate a purchase verification server. Billing sends the necessary purchase requests to Google Play. Flight coordinates and recordings are not included in Billing requests.

The local receipt is retained until a successful Play query establishes that there is no current entitlement, you delete all app data, clear Android app storage or uninstall the app. A connection error alone does not remove previously verified access. After clearing data, restoration uses Google Play. Removing the local receipt does not cancel the purchase or delete Google’s order records; refunds and account information are managed separately through Google Play. Google’s retention periods follow its policies and applicable obligations.

Authorised app review may use a separate signed Pro access credential for a specific version. If entered, the credential is stored only on the device in encrypted form using Android Keystore until reviewer access is disabled, all app data is cleared or the app is uninstalled. A new version checks the credential against its version again. The credential does not create a purchase and is not sent to Google Play Billing or the developer.

Google provides the developer with order information and financial reports in Play Console, which may include order numbers, products, purchase dates, prices, country, status and buyer information where provided. The developer uses the necessary information to provide purchased features, handle refunds and support, prevent purchase-related abuse, and meet applicable accounting and tax obligations. Google maintains its own records under its policies. The developer remains responsible for the developer’s use and any copies of this information; necessary copies are retained only for the support, dispute or legal purposes described in sections 7 and 8.

To restore Pro on a new device or after reinstalling, use the Google Play account used for the purchase. The app requests purchase information from Google Play.

If you contact the developer, the developer receives your sender address, message and any attachments you voluntarily provide. These are used to respond and investigate the issue. Correspondence is processed by Gmail (Google). Ordinary support enquiries are retained for up to six months after resolution to address follow-up questions and check fixes. Attached flight recordings containing coordinates and their working copies are deleted within 30 days after diagnostics are completed, if they are no longer needed to resolve the issue.

Information needed to resolve a dispute or fulfil legal obligations may be retained separately for longer, limited to the necessary information and a justified period. Closed enquiries are reviewed monthly; expired messages, attachments and working copies are deleted. Deletion requests are considered without waiting for the ordinary retention period to end; any necessary retention exceptions are explained. Do not attach sensitive information unnecessary for resolving the issue.

Local recordings remain until you delete them or clear app data. You can delete recordings in the app or clear app storage in Android settings. Uninstalling the app removes its internal data through Android. Previously exported files and copies sent to other services remain outside app storage and must be deleted separately.

Contact the email above about deleting data voluntarily sent to support. Retention of purchase information is described in section 6.

Settings and the locally stored purchase receipt are removed when you clear all app data or uninstall the app. Reviewer access can also be disabled in the app. Deleting local data does not cancel a Google Play purchase or erase Google’s order records. Information retained for a dispute or legal obligation is limited to what is necessary and the period justified by that purpose or required by applicable law.

Subject to applicable law, you may request access to personal data processed by the developer, correction or deletion, and restriction of processing, portability or object to processing where the relevant right is provided by law. Where processing relies on consent, you may withdraw it. You may complain to a competent data protection authority. Contact atb.energo@gmail.com. Requests are handled within the time limits prescribed by applicable law; conditions and exceptions may apply.

The developer cannot remotely read, export or delete recordings stored only on your device. You control those recordings in the app and Android settings. If you sent a copy to support, you can request deletion of that copy from the developer.

Requests about Google’s own records and processing go to Google. Requests about how the developer uses order information received from Google or any copies held by the developer go to the developer; they are not excluded merely because the information came from Google.

The developer is located in Uzbekistan, where support correspondence and order information accessed by the developer may be processed. Google Play, Gmail and the website hosting provider may process information in other countries. Google describes its processing and transfer safeguards at https://policies.google.com/privacy and https://policies.google.com/privacy/frameworks.

The app does not send local flight recordings to the developer unless you choose to share them. Sending a recording or enquiry to support involves the email provider and receipt by the developer in Uzbekistan.

The developer’s processing and transfers must comply with applicable law. For questions about this processing, contact the email above.

Internal app data is protected by Android access controls. Automatic backup through standard Android Backup is disabled in the app configuration. You are responsible for access to your device and the storage destination chosen for exported files. Absolute security of any device or transmission method cannot be guaranteed.

Purchase receipts and reviewer access credentials are stored locally in encrypted form using Android Keystore. This does not mean that every flight recording or exported file has separate app-level encryption. Access to support correspondence and order information is limited to what the developer needs for the stated purposes.

Opening the policy webpage connects your browser to its hosting provider. If hosted on Google Sites, Google processes technical request information under its privacy policy: https://policies.google.com/privacy. This website connection is separate from local processing of flight recordings in the app.

The current policy is available on this page and in the app. Its effective date is shown above. Material changes to data handling will be explained in the app; any necessary permissions or consent are requested separately.

This revision replaces version 1. The app stores the revision identifier and the time you acknowledge the offline policy locally. Acknowledgement records that you read the policy; it is not blanket consent to processing.