App analysis · 11.10.2026
Metro de Madrid
es.metromadrid.metroandroid · version 3.41
In short
SDKs found: 1. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 3 — 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
Sensitive permissions (3)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - NFC: reading cards, documents and tags —
android.permission.NFC
All manifest permissions (15)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.BLUETOOTHandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.google.android.c2dm.permission.RECEIVEcom.google.android.providers.gsf.permission.READ_GSERVICESes.metromadrid.metroandroid.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONes.metromadrid.metroandroid.permission.MAPS_RECEIVE
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
es.metromadrid.metroandroid · version 3.41 (code 341)692c2d60169139ad5a4db0be3bd7cc2b3b1233e36425e06f3cc62896c8dca442888d6ecc0b45c575bbe7608dba55e9bb703e4bc9879a9e6ba15f25ae6bb738472769b78c1753The 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.