App analysis · 20.10.2026
The Battle for Wesnoth
org.wesnoth.Wesnoth · version 1.19.28
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 2 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (2)
- files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE
All manifest permissions (4)
android.permission.INTERNETandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.WRITE_EXTERNAL_STORAGEorg.wesnoth.Wesnoth.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
org.wesnoth.Wesnoth · version 1.19.28 (code 1192800002)ad2248ca2dc5a48cd8d63cc5025e6d6bee8710b65a798e19a6dc994af8061b353ff2fa4abe9ac48c0af7a6e8a71048d33a5f00a0256e87a20df6c7a67e95c7ddThe 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.