App analysis · 20.10.2026
AndrOBD
com.fr3ts0n.ecu.gui.androbd · version V2.7.10
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 5 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (5)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - scan for nearby Bluetooth devices —
android.permission.BLUETOOTH_SCAN - draw over other apps —
android.permission.SYSTEM_ALERT_WINDOW
All manifest permissions (15)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.BLUETOOTHandroid.permission.BLUETOOTH_ADMINandroid.permission.BLUETOOTH_CONNECTandroid.permission.BLUETOOTH_SCANandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_CONNECTED_DEVICEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.SYSTEM_ALERT_WINDOWandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.fr3ts0n.ecu.gui.androbd.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
com.fr3ts0n.ecu.gui.androbd · version V2.7.10 (code 20710)71d3cecd69b644da81682d95fd0030caad4ce90227859236486250d885f2d67e60d7575f56e8fe0e268365d0f90a8430721a0288f30f191435b12398ec1a3990The 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.