App analysis · 15.10.2026
VBRK App
app.connact.vbrk · version 3.1.64
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: 6. Companies: 3, of which outside the EEA — 3. 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
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google IMA SDK — Google LLC, United States outside EEA advertising
- Google reCAPTCHA — Google LLC, United States outside EEA защита от ботов
- Sentry — Functional Software Inc., United States outside EEA crash reporting
- Stripe — Stripe, Inc., United States outside EEA payments
Sensitive permissions (7)
- calendar —
android.permission.READ_CALENDAR - modify calendar —
android.permission.WRITE_CALENDAR - camera —
android.permission.CAMERA - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE - draw over other apps —
android.permission.SYSTEM_ALERT_WINDOW
All manifest permissions (39)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_NOTIFICATION_POLICYandroid.permission.ACCESS_WIFI_STATEandroid.permission.BROADCAST_CLOSE_SYSTEM_DIALOGSandroid.permission.CAMERAandroid.permission.DOWNLOAD_WITHOUT_NOTIFICATIONandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_APP_BADGEandroid.permission.READ_CALENDARandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.READ_PHONE_STATEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.SCHEDULE_EXACT_ALARMandroid.permission.SYSTEM_ALERT_WINDOWandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_CALENDARandroid.permission.WRITE_EXTERNAL_STORAGEapp.connact.vbrk.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.anddoes.launcher.permission.UPDATE_COUNTcom.android.vending.BILLINGcom.google.android.c2dm.permission.RECEIVEcom.google.android.providers.gsf.permission.READ_GSERVICEScom.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
app.connact.vbrk · version 3.1.64 (code 3146138)8dd38cd7359ba8eeaa16844b423abf1b72af153e50d4dc0c084dcdb981644d47295b0c93176b42a0423b90c119eca790707ceb4661a4061873e1d80a8db675e113c27d15ac2eThe 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.