Can I trust My Orange Moldova?
This scan is more than 90 days old.
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
- The build includes the Firebase Analytics and Batch SDKs, whose code reads app usage data for usage insights and push notifications, with analytics requiring explicit user consent before activation. Identity verification flows rely on AriadNext IDcheckio and Unissey, which may process document or biometric data. Some user data may not be fully protected in all transmission scenarios.
- Main concern
- Hardcoded bearer token grants full unauthenticated access to Orange antispam production backend
- The developer's description
- Manage your Orange Moldova account: check balance, add services, manage favorite numbers, recharge online, and change tariff plans. Includes anti-spam protection to identify and block unwanted calls.
- Third-party services
- 14
- 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
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
StrongEverything visible
Why this result
The check compares the app's privacy disclosures against what the code does: the data categories collected, the companies named in code as their recipients, and the identifiers attached to each. The comparison covers the store listing, the in-app privacy text and any privacy manifest shipped in the build. Every claim compared matched the code here.
The app includes a built-in privacy disclosure panel that lists permissions and data uses, including phone access for the antispam feature. Consent controls for analytics are present, properly labeled, and set to off by default. No evidence was found of the app's privacy disclosures contradicting what the code actually does.
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 artificial barriers to leaving the service were found. Account data is managed through Orange's standard carrier account systems, accessible through the carrier's website and customer service channels in addition to this app. No proprietary data formats were found that would trap subscriber information or prevent switching.
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.
Strengths
- Firebase App Check with Play Integrity attestation active in production — modified APKs and unofficial clients rejected
- Firebase Analytics Consent Mode v2 fully configured with deny-by-default for all four consent signals
- Batch SDK device fingerprinting disabled (brand, model, GeoIP)
- READ_CALL_LOG and READ_PHONE_STATE scoped exclusively to anti-spam feature — not accessed by any analytics or marketing SDK
- Tink AES-GCM key management infrastructure present in codebase (pj/a.java, oq/a.java)
What the app contains
14 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Crashlytics
- Firebase Messaging (FCM)
- Firebase App Check
- Firebase Realtime Database
- Batch SDK
- Google Maps SDK
- Google ML Kit
- Huawei HMS (Push, Maps, Location, ML)
- AriadNext IDcheckio
- Unissey SDK
- OkHttp3
- Retrofit2
- Airbnb Lottie
Libraries
| Library | Version | Advisory |
|---|---|---|
| Room | not recorded | none confirmed |
| Lottie | not recorded | none confirmed |
| Facebook SDK | 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 |
Show all 30 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
- 27,571
- Scan date
- 13 June 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.