Last updated: 12 September 2026
Flight Chat is provided by Krzysztof Dąbrowski, an individual based in Poland. I am the controller for the personal data processing described in this policy that I determine. For privacy questions or requests, contact [email protected].
This policy covers Flight Chat for Android and iOS and the Flight Chat website. Features, service integrations and data handling vary by app version and platform; the descriptions below apply where the relevant feature or service is included.
Flight Chat lets nearby devices exchange text messages and, in versions that support it, make live audio calls through Google Nearby Connections, using Bluetooth or Wi-Fi depending on the platform and connection. Messages and call audio are delivered directly between connected devices rather than through a messaging server operated by me.
The app does use online services for crash diagnostics, version-dependent app analytics and, on iOS, the optional audio-call purchase. These services can communicate over the internet when connectivity is available.
You do not need to create an account or provide a phone number or email address to chat. You choose a nickname, which is stored on your device and shared with nearby devices during discovery and connection setup. The app also stores and shares a persistent random peer ID used to coordinate connections and enable device-local blocking. The same ID and the peer's nickname can be included in an abuse-report email draft prepared by another user. The ID is reused across app launches, so nearby devices may recognize the same ID on later occasions, but it can change if app data is cleared or the app is reinstalled.
Connected devices exchange the messages or live audio you send, along with technical information needed for messaging, connection management and call control. The person you communicate with can retain or share what they receive. Deleting data from your device does not delete copies held by another person.
Flight Chat does not provide a central chat-history service and does not create saved recordings of audio calls. Messages, nicknames and unsent text can remain temporarily in app or operating-system state. Notifications can include a peer's nickname and message text and may be visible on the lock screen or in notification history, depending on your device settings.
If you choose Report, Flight Chat opens your email app with an editable draft addressed to [email protected] and prefilled with the reported peer's nickname and persistent random peer ID. No messages are attached automatically. You can edit or discard the draft, and I receive its contents only if you send the email.
If sent, I and the relevant email providers receive your sender address, the peer details you leave in the draft, and anything else you add. Your operating system, email app or email provider may also process or synchronize the draft when it is opened.
Flight Chat stores your nickname, your persistent random peer ID, your connection preference, the version of the Terms of Service you accepted, and the persistent random peer IDs of peers you block. Service providers can also store local information needed for diagnostics and, on iOS, purchase management.
Android backup behavior depends on the app version. Versions configured to opt out exclude app data from standard cloud backup and device-to-device transfer; in versions that allow backup, eligible data may be backed up or transferred. An opt-out does not erase existing backups or control every manufacturer-specific migration tool. On iOS, eligible app data can be included in iCloud or computer backups and device transfers, depending on your settings.
Flight Chat uses Firebase Crashlytics on Android and iOS to identify crashes and improve reliability. Crashlytics can receive crash traces, non-fatal errors, diagnostic events, timestamps, app and operating-system versions, device characteristics, generated installation and session identifiers, and network information such as an IP address. Crash reporting starts automatically and there is currently no diagnostic opt-out inside the app.
I use this information only to diagnose technical problems and improve the app. Diagnostic details vary by version. Current versions are designed not to include message or draft contents, peer nicknames, authentication tokens or audio content in app-authored diagnostic logs. See Firebase privacy and security information.
Depending on the app version, Google Analytics for Firebase may collect app-usage events and associated app, device and installation information to help understand how the app is used. This is separate from Crashlytics crash reporting and only applies to versions with the Analytics integration. See Firebase privacy and security information.
Nearby Connections provides device discovery and peer-to-peer transport. On Android, Google documents that Google Play services collects connection performance metrics and device information, including latency, reliability, throughput, device model, country, build version and package name, to improve Nearby. Google states that this collection can be controlled through the device's Google Usage & diagnostics setting. This setting does not disable Flight Chat's Firebase Crashlytics reporting or Firebase Analytics. See the Nearby Connections documentation and Google Privacy Policy.
On iOS, initiating audio calls can be unlocked with an optional one-time in-app purchase. Apple processes App Store payments, and Flight Chat uses RevenueCat to retrieve the offer and price, validate and restore the purchase, determine whether the feature is unlocked, and provide purchase reporting. Receiving calls does not require a purchase. Where audio calls are available on Android, they are free and this purchase is not enabled.
Flight Chat does not receive your payment-card details. RevenueCat generates a random app user identifier that can be associated with purchase and usage records. It is not your Flight Chat nickname and does not make the associated records anonymous. RevenueCat can process that identifier, product and transaction information, purchase dates, entitlement status, device and operating-system information, first and last contact times, and country information. RevenueCat starts with the iOS app to check purchase status and load offers, including before you choose to buy anything.
See RevenueCat's Privacy Policy and Apple's App Store privacy information.
This website uses Cloudflare Web Analytics to understand aggregated page usage and improve the website. Cloudflare states that Web Analytics does not use cookies, local storage or cross-site tracking to collect its metrics. Cloudflare processes technical web-request information to provide this service. Cloudflare states that unsampled beacon data is retained for 7 days; older data is aggregated, and Web Analytics reports are available for the previous six months. See the Cloudflare Privacy Policy.
You can review or revoke permissions, change notification previews and manage backups through your device settings. Denying a permission can prevent the related feature from working.
Where the GDPR applies to processing I determine, the purposes and legal bases are as follows. A basis applies only to the processing necessary for that purpose, not automatically to every activity of a service provider.
These GDPR bases do not replace separate consent requirements for storing or accessing information on a device or using third-party services. Reading this policy, using the app or granting an operating-system permission does not by itself provide consent to unrelated data processing. Automatic SDK behavior and the available controls are described above.
Information can be received by the nearby people you communicate with; Google for Nearby, Firebase diagnostics and version-dependent app analytics; RevenueCat and Apple for iOS purchases; Cloudflare for website analytics and delivery; your operating system and backup provider; and your email app and email provider when you prepare or send a support request or abuse report. Providers' roles differ: some process data on my behalf, while others also process information for their own purposes, such as Apple operating the App Store. Their independent processing is described in their own privacy notices.
Providers and their subprocessors may process personal data outside the European Economic Area, including in the United States, where data-protection laws may differ. Google and Cloudflare describe reliance on the EU-US Data Privacy Framework for transfers covered by the recipient's certification and European Commission Standard Contractual Clauses where applicable. RevenueCat's data-processing agreement provides Standard Contractual Clauses for restricted transfers. The mechanism depends on the recipient and transfer, rather than applying identically to all processing.
Details and contractual safeguards are available in the Firebase data-processing terms (for Crashlytics), Google Ads Data Processing Terms (for Google Analytics for Firebase), RevenueCat data-processing agreement and Cloudflare data-processing agreement. Contact me to request information or a copy of the safeguards applicable to Flight Chat's transfers.
Local preferences remain until you change them, clear app data or delete the app, subject to operating-system backups. Clearing Android app storage or deleting the iOS app removes its active app-container data; this does not remove another participant's copies, existing backups or information already sent to service providers.
Firebase states that Crashlytics retains crash stack traces and associated identifiers for 90 days before beginning removal. RevenueCat and Apple retain purchase records as needed to provide purchase validation and restoration and meet contractual or legal obligations. Support correspondence and abuse reports are kept only as long as reasonably necessary to answer the request, assess the report, take related action, and handle applicable legal obligations.
The Crashlytics period is not an app-wide retention period. Firebase Analytics retention depends on the Analytics property's retention settings and Google's retention rules; uninstalling the app does not automatically erase provider records. Contact me for help identifying the data and retention settings applicable to your app version.
Depending on applicable law, you may have rights to access, correct, delete, restrict or receive your personal data in a portable format, and to object to processing based on legitimate interests. Contact [email protected] to make a request. Because Flight Chat has no user accounts and providers use generated identifiers, a nickname or email address may not be enough to locate provider records.
If processing is based on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal.
You may also complain to your competent data-protection authority, including Poland's President of the Personal Data Protection Office (UODO). Information processed independently by Apple, Google, RevenueCat or Cloudflare is also subject to their respective privacy procedures.
You must be at least 18 years old to use Flight Chat. The app is not intended for children or minors and does not verify users' ages. If you believe a child has used Flight Chat or sent personal data to me, contact me using the address above.
Nearby Connections encrypts established device-to-device connections in transit. This does not hide your discovery nickname or prevent a recipient from copying content. No method of transmission or storage is completely secure.
I may update this policy when Flight Chat or its service providers change. Updates will be published here with a revised date, with any additional notice required by law. The Terms of Service describe the conditions for using Flight Chat.
For privacy questions or requests, contact Krzysztof Dąbrowski at [email protected]. Include your app version and platform where relevant. Do not send payment-card details or private conversations unless necessary to explain the issue.