App analysis · 14.10.2026
VP Bank e-banking
com.vpbank.ebanking.mobile · version 8.0.8-prod.80
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 1 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (1)
- write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE
All manifest permissions (7)
android.permission.ACCESS_NETWORK_STATEandroid.permission.INTERNETandroid.permission.WRITE_EXTERNAL_STORAGEcom.vpbank.ebanking.mobile.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.vpbank.qtoken.debug.permission.WAKEUP_FOR_SIGNcom.vpbank.qtoken.permission.WAKEUP_FOR_SIGNcom.vpbank.qtoken.stage.permission.WAKEUP_FOR_SIGN
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
com.vpbank.ebanking.mobile · version 8.0.8-prod.80 (code 80)902a18f082d6f04b0da3d3456c07b7e046e023e743161bec5b499d73a582c7cee087e5856facf57b50895ee34c9d23f0d2b28f1a27aead5cfba9e9f557605ed313c27d15ac2eThe 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.