App analysis · 11.10.2026
KMI IRM
be.irm.kmi.meteo · version 4.4.9
In short
SDKs found: 4. Companies: 2, of which outside the EEA — 2. Sensitive permissions: 3 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Cloud Messaging — Google LLC, United States outside EEA push notifications
- Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
Sensitive permissions (3)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - camera —
android.permission.CAMERA
All manifest permissions (11)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.VIBRATEandroid.permission.WAKE_LOCKcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.providers.gsf.permission.READ_GSERVICES
Limits of the analysis
The analysis shows code inside the app file, not data transfers: an SDK being present means a transfer is possible, not that it happens. The country is where the company owning the SDK is registered, not where its servers are. Some code may have been renamed at build time, so the SDK list is a lower bound.
The legal assessment is made by the competent supervisory authority.
Evidence
be.irm.kmi.meteo · version 4.4.9 (code 242611337)ea3c8efd3ac831775d7620ba7c7e926c91cae996e5c049deb48af0f23f6840a00082eabe01f9a6f1a25788eefa1cfefc1180b81fdb456c4356d626180a5334d02769b78c1753The same file (same SHA-256) with the same library version gives the same result — check it on the APK check page. Licence CC BY 4.0, source — gdpru.eu; report errors to contact@gdpru.eu.