App analysis · 18.10.2026
FD VR - Virtual App Launcher
in.fulldive.applicationslauncher · version 3.6.1
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
- Flurry — Yahoo, United States outside EEA analytics
Sensitive permissions (4)
- files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - NFC: reading cards, documents and tags —
android.permission.NFC - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE
All manifest permissions (8)
android.permission.ACCESS_NETWORK_STATEandroid.permission.INTERNETandroid.permission.NFCandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.READ_PHONE_STATEandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGE
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
in.fulldive.applicationslauncher · version 3.6.1 (code 306001)24da2fabe54e50b1ac2cfa062fb9074f09fee366cc95eb725ceb85f5c0cea5cacd36dfc9d12e199c94c24829f4c143610562b86bc7eb875cd8e3c1f8f79ab4ca13c27d15ac2eThe 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.