App analysis · 12.10.2026
eZóna SSE
sk.sse.ezona · version 1.4.22
In short
SDKs found: 4. Companies: 2, of which outside the EEA — 2. Sensitive permissions: 4 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
Sensitive permissions (4)
- camera —
android.permission.CAMERA - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - fingerprint —
android.permission.USE_FINGERPRINT - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (8)
android.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.INTERNETandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTandroid.permission.WAKE_LOCKcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_ID
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
sk.sse.ezona · version 1.4.22 (code 25052313)4fd15e58e618071ae503d2b383832294558abaa995e321aace9450ea479cf4a6c88f7c63696073ca157bf387e1d566788c869d5035419073f122e06c2432c4c813c27d15ac2eThe 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.