Can I trust meross?
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
- No advertising networks or data broker SDKs are present in this build. The build includes code to send device usage statistics and crash reports to Firebase Analytics and Crashlytics. The build includes code that processes smart home device data through Meross infrastructure and AWS, and names no third-party monetization service in code as a destination of user data.
- Main concern
- WebView file access + cleartext HTTP enables auth token theft via CDN injection
- The developer's description
- Control Meross smart home devices including WiFi switches, plugs, and hubs. Set up automation, monitor device status in real-time, and integrate with Google Home and Alexa for centralized smart home control.
- Third-party services
- 22
- Findings rated low or higher
- 11
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.
No evidence was found of proprietary data formats that would trap the user's data, artificial barriers to account cancellation, or obstacles to switching to a different smart home platform. The app uses standard cloud account infrastructure and no confirmed lock-in mechanisms were identified in the code.
Strengths
- Local device communication uses ephemeral ECDH key exchange, providing forward secrecy per session
- No advertising networks or data broker SDKs are present in the app
- The build includes code to send data only to Meross's own infrastructure and Firebase/Google; no third-party data monetization SDKs are present
What the app contains
22 services
Third-party services the scan names in the build:
- Firebase Core
- Firebase Crashlytics
- Firebase Analytics
- Firebase Cloud Messaging
- AWS Amplify
- AWS Cognito
- AWS S3
- Eclipse Paho MQTT
- Alibaba FastJSON
- Alibaba ARouter
- Matter/CHIP SDK
- BouncyCastle
- Google Play Billing
- Dagger 2
- RxJava
- Glide
- ZXing
- Facebook Stetho
- Google Maps
- Google Sign-In
- KLog
- LuaJava/BeanShell
Libraries
| Library | Version | Advisory |
|---|---|---|
| Room | not recorded | none confirmed |
| Google Play Billing | not recorded | none confirmed |
| Stetho | not recorded | none confirmed |
| Jackson | not recorded | none confirmed |
| Glide | 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 |
Show all 24 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.
- Build SHA-256
- 91cf18e5a6c3663c503c31bb5d815afb2cf5ae7f95545e2d68ed030be59cdb0d
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 21,091
- Scan date
- 16 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.