App analysis · 12.10.2026
eMAG.hu
hu.emag.android · version 4.56.0
In short
SDKs found: 12. Companies: 4, of which outside the EEA — 4. Sensitive permissions: 10 — 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
- Firebase Dynamic Links — Google LLC, United States outside EEA attribution / глубокие ссылки
- Firebase Performance Monitoring — Google LLC, United States outside EEA performance monitoring
- Firebase Remote Config / A/B Testing — Google LLC, United States outside EEA удалённая настройка / A/B-тесты
- Google AdMob — Google LLC, United States outside EEA advertising
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google User Messaging Platform — Google LLC, United States outside EEA consent platform
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- AppsFlyer — AppsFlyer Ltd, Israel outside EEA атрибуция установок
- Sentry — Functional Software Inc., United States outside EEA crash reporting
Sensitive permissions (10)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - camera —
android.permission.CAMERA - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - installed app sizes —
android.permission.GET_PACKAGE_SIZE - advertising ID (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_AD_ID - ad attribution (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_ATTRIBUTION - ad interests (Privacy Sandbox Topics) —
android.permission.ACCESS_ADSERVICES_TOPICS - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (23)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_ADSERVICES_CUSTOM_AUDIENCEandroid.permission.ACCESS_ADSERVICES_TOPICSandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.GET_PACKAGE_SIZEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_IDcom.huawei.appmarket.service.commondata.permission.GET_COMMON_DATAcom.samsung.android.mapsagent.permission.READ_APP_INFOhu.emag.android.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
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
hu.emag.android · version 4.56.0 (code 356)a51e5c9cf4afae83e12108d896190a9b9d7e44537e9fd6ea9f7bb81906f12a8a142b50bc26725da4aa84469254433f790588f252e0ac87936949025a2d0bd71c13c27d15ac2eThe 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.