RU EN
www.

App analysis · 05.10.2026

VBRK App

app.connact.vbrk · version 3.1.62

4SDKs found
2companies
2companies outside the EEA
7sensitive permissions

In short

SDKs found: 4. Companies: 2, 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
  • Google Firebase Analytics — Google LLC, United States outside EEA analytics
  • Google IMA SDK — Google LLC, United States outside EEA advertising
  • Sentry — Functional Software Inc., United States outside EEA crash reporting

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_STATE
  • android.permission.ACCESS_NOTIFICATION_POLICY
  • android.permission.ACCESS_WIFI_STATE
  • android.permission.BROADCAST_CLOSE_SYSTEM_DIALOGS
  • android.permission.CAMERA
  • android.permission.DOWNLOAD_WITHOUT_NOTIFICATION
  • android.permission.FOREGROUND_SERVICE
  • android.permission.INTERNET
  • android.permission.POST_NOTIFICATIONS
  • android.permission.READ_APP_BADGE
  • android.permission.READ_CALENDAR
  • android.permission.READ_EXTERNAL_STORAGE
  • android.permission.READ_PHONE_STATE
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.SCHEDULE_EXACT_ALARM
  • android.permission.SYSTEM_ALERT_WINDOW
  • android.permission.VIBRATE
  • android.permission.WAKE_LOCK
  • android.permission.WRITE_CALENDAR
  • android.permission.WRITE_EXTERNAL_STORAGE
  • app.connact.vbrk.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
  • com.anddoes.launcher.permission.UPDATE_COUNT
  • com.android.vending.BILLING
  • com.google.android.c2dm.permission.RECEIVE
  • com.google.android.providers.gsf.permission.READ_GSERVICES
  • com.htc.launcher.permission.READ_SETTINGS
  • com.htc.launcher.permission.UPDATE_SHORTCUT
  • com.huawei.android.launcher.permission.CHANGE_BADGE
  • com.huawei.android.launcher.permission.READ_SETTINGS
  • com.huawei.android.launcher.permission.WRITE_SETTINGS
  • com.majeur.launcher.permission.UPDATE_BADGE
  • com.oppo.launcher.permission.READ_SETTINGS
  • com.oppo.launcher.permission.WRITE_SETTINGS
  • com.sec.android.provider.badge.permission.READ
  • com.sec.android.provider.badge.permission.WRITE
  • com.sonyericsson.home.permission.BROADCAST_BADGE
  • com.sonymobile.home.permission.PROVIDER_INSERT_BADGE
  • me.everything.badger.permission.BADGE_COUNT_READ
  • me.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: VBRK+App_3.1.62_APKPure.xapk (75.2 MB)
Package: app.connact.vbrk · version 3.1.62 (code 3146136)
Android: minimum API 24, target API 36
File SHA-256: 5771bc01c503bbbf84cfa35f45b3db3367ffc87f5a27871c8afce62c85712d8f
Developer signature (SHA-256): 295b0c93176b42a0423b90c119eca790707ceb4661a4061873e1d80a8db675e1
Library: 63 SDK · 81 permissions · 2769b78c1753
File source: APKPure

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.

Download card (Markdown)

← All analysed apps · Check your own app