App analysis · 11.10.2026

EMT Madrid

com.emtmadrid.emt · version 9.10.0

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
  • Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
  • Google Firebase Analytics — Google LLC, United States outside EEA analytics
  • Flurry — Yahoo, United States outside EEA analytics

Sensitive permissions (7)

  • background location — android.permission.ACCESS_BACKGROUND_LOCATION
  • approximate location — android.permission.ACCESS_COARSE_LOCATION
  • precise location — android.permission.ACCESS_FINE_LOCATION
  • camera — android.permission.CAMERA
  • NFC: reading cards, documents and tags — android.permission.NFC
  • phone data (carrier, call state) — android.permission.READ_PHONE_STATE
  • advertising ID — com.google.android.gms.permission.AD_ID
All manifest permissions (19)
  • android.permission.ACCESS_BACKGROUND_LOCATION
  • android.permission.ACCESS_COARSE_LOCATION
  • android.permission.ACCESS_FINE_LOCATION
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.ACCESS_WIFI_STATE
  • android.permission.CAMERA
  • android.permission.DISABLE_KEYGUARD
  • android.permission.FOREGROUND_SERVICE
  • android.permission.INTERNET
  • android.permission.NFC
  • android.permission.READ_PHONE_STATE
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.VIBRATE
  • android.permission.WAKE_LOCK
  • com.emtmadrid.emt.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: com.emtmadrid.emt.apk (28.8 MB)
Package: com.emtmadrid.emt · version 9.10.0 (code 242)
Android: minimum API 21, target API 35
File SHA-256: 48334b755887809a5fb9d232bcfc9078b9a04b8e4a058bca5c2b7f212811673b
Developer signature (SHA-256): e76734b2ecd924c1c40d3b44ff281ef2936889bbf17f062b0a50d6d22b6a1169
Signed by: EMT (Madrid, 34) · outside EEA · key since 2013-02-27
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