App analysis · 14.10.2026
Jumia
com.jumia.android · version 20.1.0
In short
SDKs found: 12. Companies: 3, of which outside the EEA — 2. Sensitive permissions: 7 — 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 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 Analytics — Google LLC, United States outside EEA analytics
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google Tag Manager — Google LLC, United States outside EEA диспетчер тегов
- 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
- Adjust — Adjust GmbH, Germany EEA атрибуция установок
Sensitive permissions (7)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - microphone —
android.permission.RECORD_AUDIO - 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 (20)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_ADSERVICES_TOPICSandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.RECORD_AUDIOandroid.permission.REORDER_TASKSandroid.permission.WAKE_LOCKcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_IDcom.google.android.providers.gsf.permission.READ_GSERVICEScom.google.android.providers.gsf.permission.WRITE_GSERVICEScom.jumia.android.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.jumia.android.permission.A4S_SEND
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
com.jumia.android · version 20.1.0 (code 366)e1933815dee7accbbae9ed95739226f81a513299fa85fd4732cff4d080b5dd1e335cd0106ff6e6aa430725ecbcad25b9c656ab512a864df1ca3e9c1e1d00cb1e13c27d15ac2eThe 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.