App analysis · 20.10.2026
Spectre
dev.thomasbuilds.spectre · version 0.1.3
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 4 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (4)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - scan for nearby Bluetooth devices —
android.permission.BLUETOOTH_SCAN - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE
All manifest permissions (16)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_LOCAL_NETWORKandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.BLUETOOTH_ADVERTISEandroid.permission.BLUETOOTH_CONNECTandroid.permission.BLUETOOTH_SCANandroid.permission.CHANGE_WIFI_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_LOCATIONandroid.permission.FOREGROUND_SERVICE_SPECIAL_USEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_PHONE_STATEdev.thomasbuilds.spectre.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
dev.thomasbuilds.spectre · version 0.1.3 (code 103999)a61a075c103f1c8a699655a9554479cbb434d807d981f225bf2344b99c945e45c411409b94f36b678ca8c957b675d2f1ad5b7fc01a352bff4c99ed2ffbc11b39The 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.