App analysis · 11.10.2026

Zimmo

be.zimmo.mobile · version 5.8.0

11SDKs found
3companies
3companies outside the EEA
8sensitive permissions

In short

SDKs found: 11. Companies: 3, of which outside the EEA — 3. Sensitive permissions: 8 — 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
  • Firebase Performance Monitoring — Google LLC, United States outside EEA performance monitoring
  • Google AdMob — Google LLC, United States outside EEA advertising
  • Google Analytics — Google LLC, United States outside EEA analytics
  • Google Firebase Analytics — Google LLC, United States outside EEA analytics
  • Google Tag Manager — Google LLC, United States outside EEA диспетчер тегов
  • Google User Messaging Platform — Google LLC, United States outside EEA consent platform
  • Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
  • Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
  • Huawei Ads Kit — Huawei, China outside EEA advertising

Sensitive permissions (8)

  • approximate location — android.permission.ACCESS_COARSE_LOCATION
  • precise location — android.permission.ACCESS_FINE_LOCATION
  • accounts on the device — android.permission.GET_ACCOUNTS
  • write files on the device — android.permission.WRITE_EXTERNAL_STORAGE
  • access credentials — android.permission.USE_CREDENTIALS
  • advertising ID (Privacy Sandbox) — android.permission.ACCESS_ADSERVICES_AD_ID
  • ad attribution (Privacy Sandbox) — android.permission.ACCESS_ADSERVICES_ATTRIBUTION
  • advertising ID — com.google.android.gms.permission.AD_ID
All manifest permissions (19)
  • android.permission.ACCESS_ADSERVICES_AD_ID
  • android.permission.ACCESS_ADSERVICES_ATTRIBUTION
  • android.permission.ACCESS_ADSERVICES_CUSTOM_AUDIENCE
  • android.permission.ACCESS_COARSE_LOCATION
  • android.permission.ACCESS_FINE_LOCATION
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.BLUETOOTH
  • android.permission.FOREGROUND_SERVICE
  • android.permission.GET_ACCOUNTS
  • android.permission.INTERNET
  • android.permission.POST_NOTIFICATIONS
  • android.permission.USE_CREDENTIALS
  • android.permission.WAKE_LOCK
  • android.permission.WRITE_EXTERNAL_STORAGE
  • be.zimmo.mobile.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
  • 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

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.zimmo.mobile.xapk (17.4 MB)
Package: be.zimmo.mobile · version 5.8.0 (code 50800)
Android: minimum API 25, target API 36
File SHA-256: f15325c13bc3e3b0c20e164e02b7f9dca96d3377f6376f5dc051043855c04757
Developer signature (SHA-256): e767b55fce1da44c041927fa78dc8a4510d8681c229ecd8efd2a8097ce9140e6
Signed by: Google Inc. (Mountain View, US) · outside EEA · key since 2020-10-26
Library: 63 SDK · 81 permissions · 2769b78c1753
File 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.

Download card (Markdown)

← All analysed apps · Check your own app