Can I trust Fly Delta?
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- What it means for you
- Passport and boarding pass scanning is processed on the device, and trip itinerary calendar data is stored locally without being shared with Delta servers or third-party platforms. The build includes code to pass usage activity, device signals, and in-app behavior to analytics and performance services including Adobe Analytics, Firebase Analytics, Quantum Metric, and Dynatrace.
- Main concern
- Biometric password and PII stored unencrypted in database, extractable via ADB backup
- The developer's description
- Fly Delta is the official airline app for booking flights, managing SkyMiles upgrades, checking in, viewing digital boarding passes, tracking flights in real time, and accessing live customer support.
- Third-party services
- 29
- Findings rated low or higher
- 7
Open on Google PlayOpens the app's listing on Google Play in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
One criterion not metSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Data Minimization
One criterion not metTracking lacks clear disclosure
Why this result
This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
The analysis found no proprietary data formats that would trap user data, no technical barriers designed to prevent account deletion, and no artificial obstacles to switching away from the service. Data is stored in standard formats and the app does not appear to introduce mechanisms intended to make leaving unreasonably difficult.
Strengths
- OAuth access tokens and refresh tokens are encrypted with Android Keystore-backed AES-256-GCM and RSA before storage — key material never leaves the hardware security module
- Login passwords are encrypted with Keystore-backed RSA before being written to the database — plaintext passwords never touch disk
- All app traffic is forced over HTTPS app-wide with no cleartext connections permitted
- WebView SSL errors are properly rejected in all production code paths
- Passport and barcode scanning processed entirely on-device via Google ML Kit with no observed cloud transmission of image data
- Trip itinerary calendar data stays on the device — not transmitted to Delta servers or third-party analytics platforms
What the app contains
29 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Auth
- Firebase Crashlytics
- Firebase Messaging (FCM)
- Firebase Remote Config
- Firebase Installations
- Adobe Analytics
- Adobe Target
- Adobe Experience Platform (AEP)
- Adobe Optimize
- Quantum Metric
- Dynatrace
- OneTrust
- Radar SDK
- Akamai Bot Manager
- PingOne Signals / PingIdentity
- Cardinal Commerce
- Cyberfend
- LocusLabs
- Radius Networks iBeacon
- Google ML Kit
- Google Maps
- Google Credentials / Passkey
- Google AdServices (Privacy Sandbox)
- MapLibre
- Rhino JS Engine
- CameraX
- Qualtrics
- WorkManager
Libraries
| Library | Version | Advisory |
|---|---|---|
| Room | not recorded | none confirmed |
| Dynatrace | not recorded | none confirmed |
| Glide | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
| Google Play Services Location | 12451000 | none confirmed |
| Google Maps SDK | 12451000 | none confirmed |
| Material Components | not recorded | none confirmed |
| Play Core | not recorded | none confirmed |
Show all 26 librariesShow fewer
Changes since the previous scan
- Version 7.14 (versionCode 24428), score 72.
- Score 55 before, 72 after.
- Version 7.7 (Build 24269) before, 7.14 (versionCode 24428) after.
- Score change since version 7.7 (Build 24269): +17 points.
- Since the previous scan: 20 findings added, 11 removed.
- Version 7.7 (Build 24269), score 55.
- First public scan of this app.
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Build SHA-256
- fa4aee1f93939c15983e7438117134f9c64b58f2137f5f10cfb781bb7b536f68
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 52,830
- Scan date
- 12 August 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.