App analysis · 04.10.2026
Url Video Player
info.t4w.vp · version 4.0
In short
SDKs found: 1. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 4 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Google AdMob — Google LLC, United States outside EEA advertising
Sensitive permissions (4)
- 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 (11)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_ADSERVICES_TOPICSandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CHANGE_WIFI_MULTICAST_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.WAKE_LOCKcom.google.android.gms.permission.AD_IDinfo.t4w.vp.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
info.t4w.vp · version 4.0 (code 413)7a70a66f4ce8cf1a8b7586cc0cc969eec59e3a01ce459ce52921ed10ac0a2c1918b1ce3ff4697b26a0426d127fb34dc86d500182bb5e4775970674008b4478c52769b78c1753The 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.