Can I trust Bono?
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
- Authentication is handled via Google Sign-In, Apple Sign-In, and FIDO2 passkeys. Push notifications are handled through Firebase, and the build includes code to pass a device identifier to Google. The app includes code to send install referral data to Google when the app is first installed.
- The developer's description
- Loyalty rewards app. Sign in via Google account or on-device biometric authentication. App interface is served from a remote server.
- Third-party services
- 12
- Findings rated low or higher
- 8
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
StrongTracking done right
Why this result
The check looks at analytics and attribution code for companies other than the developer: the data it reads, the companies named in code as recipients, and whether a consent step runs before that code. In this build, either no such code was recorded, or a consent step runs before it and the app's own disclosures describe the collection.
No advertising networks, behavioral analytics platforms, attribution services, or data broker SDKs are present in the app. The only third-party connections are Google Sign-In for authentication, Firebase for push notification delivery, and Google Play for one-time install attribution. None of these constitute behavioral tracking of the kind this stamp assesses, so no consent timing question arises.
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.
No proprietary data formats, artificial barriers to account deletion, or obstacles to leaving the service were found in the app's code or configuration. The app's interface is loaded from the developer's web service, where account and data management features would typically reside. No evidence of lock-in mechanisms was identified.
Strengths
- No advertising, analytics, attribution, or session recording SDKs are present
- No data is shared with advertising networks or data brokers
- Biometric authentication is processed entirely on-device with no credential data transmitted
- Passkey/FIDO2 authentication support keeps credentials on-device
- All primary app content is loaded over HTTPS
What the app contains
12 services
Third-party services the scan names in the build:
- Firebase FCM
- Firebase Installations
- Google Sign-In (Capawesome plugin)
- Google Play Install Referrer
- Apple Sign-In
- FIDO2/Passkeys (Google)
- AndroidX Biometric
- Capacitor
- Ionic Camera Library
- OkIO
- Gson
- Cordova
Libraries
| Library | Version | Advisory |
|---|---|---|
| Datatransport | not recorded | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
| Google Play Services Location | 12451000 | none confirmed |
| Material Components | not recorded | none confirmed |
| Play Core | not recorded | none confirmed |
| Gson | not recorded | none confirmed |
| Firebase | 12451000 | none confirmed |
| Okio | not recorded | none confirmed |
| Kotlin Coroutines | not recorded | none confirmed |
Changes since the previous scan
- Version 1.0.306 (build code 306), score 87.
- Score 70 before, 87 after.
- Version 1.0.271 (Build 271) before, 1.0.306 (build code 306) after.
- Score change since version 1.0.271 (Build 271): +17 points.
- Since the previous scan: 11 findings added, 13 removed.
- Version 1.0.271 (Build 271), score 70.
- 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
- 83778a67d22296419c2421587fd4e4b791fba66ada3fa578ccd46c67d25cd8cb
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 7,226
- Scan date
- 11 August 2026
Corrections
- : Automated regeneration changed a published public claim.
- : Automated regeneration changed a published public claim.
- : Automated regeneration changed a published public claim.
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.