Can I trust Hearoes?
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
- Hearing training data, exercise progress, game scores, and user profiles are stored in the developer's own Firebase systems and not shared with data brokers or advertising networks. The build includes code to send usage and crash data to Firebase Analytics and Firebase Crashlytics, and purchase activity is handled by RevenueCat. Some data on the device may not be fully protected. All network requests in the code use encrypted connections.
- Main concern
- Firebase and GAID collected without consent; Play Store privacy label is false
- The developer's description
- Interactive auditory training platform for cochlear implant and hearing aid users. Features 50+ gamified exercises covering environmental sounds, speech recognition, and vocabulary improvement for hearing rehabilitation.
- Third-party services
- 21
- Findings rated low or higher
- 9
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
Items recorded, result pending reviewSecurity 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
An item rated high or above is openDisclosure 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
Items recorded, result pending reviewHard to leave
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. At least one of the two was not found in this build. Leaving therefore means either abandoning the data or contacting the developer to ask for it.
Truly Local
One criterion not metContains code to send personal data off the device
Why this result
This app presents itself as working offline or on the device alone, and this build contains code written to send personal data to servers. The check covers analytics, crash reporting, advertising code and any first-party endpoint the code addresses personal data to. Code of this kind is common; what this check reports is the distance between that code and how the app describes itself.
Red flags
The app's privacy declarations do not match its code
Why this result
The privacy declarations shipped in this build, or the ones on the store listing, state less than the code does. Declarations of this kind are what a store, a regulator and a person comparing two apps rely on.
Strengths
- Firebase backend APIs are protected by Play Integrity attestation, preventing unauthorized access from modified or sideloaded installs
- GWP-ASan memory safety hardening is enabled for native code in production, detecting heap corruption in the Unity binary
- No advertising networks are present — despite having advertising ID permissions, no ad SDK receives behavioral targeting data
- Hearing training data (exercise progress, game scores, user profiles) is stored in the developer's own Firebase infrastructure and not shared with data brokers or third-party analytics platforms
- No data broker, session recording, or analytics aggregator SDKs are present — the SDK footprint is lean for a Unity game
- Both RevenueCat and Unity honor the user's 'Opt out of Ads Personalization' setting and skip GAID collection when Limit Ad Tracking is enabled
- All network communications use HTTPS or WSS (TLS) — no plaintext HTTP endpoints were identified
What the app contains
21 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Crashlytics
- Firebase Realtime Database
- Firebase Firestore
- Firebase Cloud Messaging
- Firebase Remote Config
- Firebase App Check
- Firebase Dynamic Links
- Firebase Installations
- Firebase Auth
- Firebase Storage
- RevenueCat
- Unity Engine
- Google Play Games
- Google Sign-In
- Google Play Billing
- Google reCAPTCHA
- Google AdServices
- Amazon IAP
- Samsung Game SDK
- PairIP
Libraries
| Library | Version | Advisory |
|---|---|---|
| Google Play Billing | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Advertising ID client | 12451000 | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
| Google Play Services Location | 12451000 | none confirmed |
| Play Core | not recorded | none confirmed |
| Play Integrity | not recorded | none confirmed |
| Gson | not recorded | none confirmed |
| Google Tink | not recorded | none confirmed |
Show all 16 librariesShow fewer
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.
- Files decompiled
- 14,183
- Scan date
- 6 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.