App analysis · 20.10.2026
Mastodon
org.joinmastodon.android · version 2.13.4
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 (9)
android.permission.ACCESS_LOCAL_NETWORKandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACKandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.VIBRATEandroid.permission.WRITE_EXTERNAL_STORAGEcom.google.android.c2dm.permission.RECEIVEorg.joinmastodon.android.permission.C2D_MESSAGE
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.joinmastodon.android · version 2.13.4 (code 191)ce1a8222a1f9a59cdde0816a64a39692123c3bc05f64966abae5b0ea2dfe709e83cb2cd2bdd51031044cd276852324b2e96fbe3d87298df7b6794c9dea345504The 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.