Can I trust my moldcell?
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.
- Avoid if
- Users on public or untrusted Wi-Fi networks
- What it means for you
- The app includes code to send account and usage data to Firebase Analytics, Facebook, and Google Ad Services for analytics and advertising purposes. Some code may send activity with less protection than expected on some network connections. An EVAM SDK also includes code to route data to a third-party provider outside major platform ecosystems.
- Main concern
- SSL validation disabled in two production clients — silent MitM interception possible
- The developer's description
- Mobile account manager for Moldcell subscribers. Check balance, tariff plans, usage, pay bills, activate services, and contact customer support.
- Third-party services
- 12
- Findings rated low or higher
- 10
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
An item rated high or above is openSecurity 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
An item rated high or above is openTracking 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
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.
This app is an interface for managing an existing telecom account. It does not create unique user-generated data or use proprietary formats that would trap your information. No artificial barriers to canceling service or switching providers were found.
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.
The code addresses precise location to endpoints associated with data brokers
Why this result
This build contains code written to send precise location to endpoints associated with companies that buy and resell location data. Precise location identifies a home, a workplace and a daily routine, and it has the largest resale market of any category here.
Stores an identifier that survives a reinstall
Why this result
This build stores an identifier that survives deleting and reinstalling the app. An identifier of that kind links a new install back to the previous one, so removing the app does not end the profile built against it.
Strengths
- Main Hilt-injected OkHttpClient correctly configured with TrustManagerFactory and pinned CA certificate (res/raw/moldcell_cercert_prod.crt)
- Network security config blocks plain HTTP at runtime (http://www.moldcell.md/ string resource blocked by NSC)
What the app contains
12 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Crashlytics
- Firebase Cloud Messaging
- Firebase Auth
- Firebase Realtime Database
- EVAM SDK (Evam AB)
- Google Maps Android
- Google Ad Services
- Facebook SDK
- Google Play Core
- Glide
- YouTubePlayer
Libraries
| Library | Version | Advisory |
|---|---|---|
| Lottie | not recorded | none confirmed |
| Glide | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Mobile Ads (AdMob) | 12451000 | 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
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
- 26,166
- 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.