App analysis · 14.10.2026
Bible (YouVersion)
com.sirma.mobile.bible.android · version 11.33.1+7097493
Session recording is possible
Sentry ships with a screen-and-tap recording module. It comes with the SDK by default and is switched on by the developer's settings, which are not visible in the code. The capability is there.
In short
SDKs found: 11. Companies: 8, of which outside the EEA — 8. 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 Remote Config / A/B Testing — Google LLC, United States outside EEA удалённая настройка / A/B-тесты
- 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
- Amazon Device Messaging — Amazon.com, Inc., United States outside EEA push notifications
- Amplitude — Amplitude Inc., United States outside EEA analytics
- Branch — Branch Metrics, United States outside EEA attribution / глубокие ссылки
- Braze — Braze Inc., United States outside EEA маркетинг / push
- Sentry — Functional Software Inc., United States outside EEA crash reporting
- Huawei Ads Kit — Huawei, China outside EEA advertising
Sensitive permissions (10)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - contacts —
android.permission.READ_CONTACTS - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - fingerprint —
android.permission.USE_FINGERPRINT - 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_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACKandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.POST_PROMOTED_NOTIFICATIONSandroid.permission.READ_CONTACTSandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTandroid.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.sirma.mobile.bible.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
com.sirma.mobile.bible.android · version 11.33.1+7097493 (code 7097493)9d7aa0fc93dd0b360d98223270c21fa29d50939c8dc330be8cd4c85fb20bbd51d791238562e6b71590e3b911e2202680c4b7feb08a45fa33476f5807acbad95f13c27d15ac2eThe 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.