App analysis · 11.10.2026
JBC
be.jbc.app · version 1.0.5.12
8SDKs found
5companies
5companies outside the EEA
6sensitive permissions
In short
SDKs found: 8. Companies: 5, of which outside the EEA — 5. Sensitive permissions: 6 — 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
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- Sentry — Functional Software Inc., United States outside EEA crash reporting
- Huawei Push Kit — Huawei, China outside EEA push notifications
- OneSignal — OneSignal Inc., United States outside EEA push notifications
Sensitive permissions (6)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - camera —
android.permission.CAMERA - 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
All manifest permissions (35)
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.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_APP_BADGEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.REORDER_TASKSandroid.permission.VIBRATEandroid.permission.WAKE_LOCKbe.jbc.app.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONbe.jbc.app.permission.C2D_MESSAGEcom.anddoes.launcher.permission.UPDATE_COUNTcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.htc.launcher.permission.READ_SETTINGScom.htc.launcher.permission.UPDATE_SHORTCUTcom.huawei.android.launcher.permission.CHANGE_BADGEcom.huawei.android.launcher.permission.READ_SETTINGScom.huawei.android.launcher.permission.WRITE_SETTINGScom.majeur.launcher.permission.UPDATE_BADGEcom.oppo.launcher.permission.READ_SETTINGScom.oppo.launcher.permission.WRITE_SETTINGScom.sec.android.provider.badge.permission.READcom.sec.android.provider.badge.permission.WRITEcom.sonyericsson.home.permission.BROADCAST_BADGEcom.sonymobile.home.permission.PROVIDER_INSERT_BADGEme.everything.badger.permission.BADGE_COUNT_READme.everything.badger.permission.BADGE_COUNT_WRITE
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
File: be.jbc.app.xapk (83.3 MB)
Package:
be.jbc.app · version 1.0.5.12 (code 100050012)Android: minimum API 28, target API 35
File SHA-256:
66fcb454a10f6cdcab0a0548888a36faffaf8c8f2812a46c5d22c70248caeed7Developer signature (SHA-256):
eca6bee997277ba4b7e0b04d138f0ec672fd9c57c6d0eb998a3014e9fdcfce2aSigned by: Google Inc. (Mountain View, US) · outside EEA · key since 2024-06-07
Library: 63 SDK · 81 permissions ·
2769b78c1753File source: APKPure (через apkeep)
The 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.