App analysis · 04.10.2026

cz.zasilkovna.app

cz.zasilkovna.app · version 1.39.0

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

In short

SDKs found: 6. 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
  • Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
  • Google Firebase Analytics — Google LLC, United States outside EEA analytics
  • Google Tag Manager — Google LLC, United States outside EEA диспетчер тегов
  • Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
  • Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics

Sensitive permissions (7)

  • approximate location — android.permission.ACCESS_COARSE_LOCATION
  • precise location — android.permission.ACCESS_FINE_LOCATION
  • scan for nearby Bluetooth devices — android.permission.BLUETOOTH_SCAN
  • 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 (21)
  • android.permission.ACCESS_ADSERVICES_AD_ID
  • android.permission.ACCESS_ADSERVICES_ATTRIBUTION
  • android.permission.ACCESS_ADSERVICES_CUSTOM_AUDIENCE
  • android.permission.ACCESS_ADSERVICES_TOPICS
  • android.permission.ACCESS_COARSE_LOCATION
  • android.permission.ACCESS_FINE_LOCATION
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.BLUETOOTH
  • android.permission.BLUETOOTH_ADMIN
  • android.permission.BLUETOOTH_CONNECT
  • android.permission.BLUETOOTH_SCAN
  • android.permission.FOREGROUND_SERVICE
  • android.permission.INTERNET
  • android.permission.POST_NOTIFICATIONS
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.WAKE_LOCK
  • com.google.android.c2dm.permission.RECEIVE
  • com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
  • com.google.android.gms.permission.AD_ID
  • com.google.android.providers.gsf.permission.READ_GSERVICES
  • cz.zasilkovna.app.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

File: cz.zasilkovna.app_1.39.0-3110_4arch_7dpi_94d0b1eec7ae5d1c96636e01bcf6860e_apkmirror.com.apkm (23.9 MB)
Package: cz.zasilkovna.app · version 1.39.0 (code 3110)
Android: minimum API 23, target API 36
File SHA-256: eafa4645b49e4a845f1cc619cf4739cbd35008a65cc1c6b21d693fc9436ae4ee
Developer signature (SHA-256): 931e6bd9b614c6a7d1753b5dd255039d5a3ecad17868625c5c6b35cad0dd473b
Library: 63 SDK · 81 permissions · 2769b78c1753
File source: APKMirror

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