App analysis · 19.10.2026
Royal Match
com.dreamgames.royalmatch · version 38911
In short
SDKs found: 16. Companies: 9, of which outside the EEA — 9. Sensitive permissions: 4 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Cloud Messaging — Google LLC, United States outside EEA push notifications
- Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
- Firebase Remote Config / A/B Testing — Google LLC, United States outside EEA удалённая настройка / A/B-тесты
- Google AdMob — Google LLC, United States outside EEA advertising
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google User Messaging Platform — Google LLC, United States outside EEA consent platform
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- ironSource — Unity Technologies, Israel outside EEA advertising
- Unity Ads — Unity Technologies, United States outside EEA advertising
- AppLovin — AppLovin Corp., United States outside EEA advertising
- AppsFlyer — AppsFlyer Ltd, Israel outside EEA атрибуция установок
- Fyber (Digital Turbine) ✓ — Digital Turbine, United States outside EEA advertising
- IAB Open Measurement SDK — IAB Tech Lab, United States outside EEA ad measurement
- Mintegral — Mobvista, China outside EEA advertising
- WeChat OpenSDK — Tencent, China outside EEA social login
Sensitive permissions (4)
- advertising ID (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_AD_ID - ad attribution (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_ATTRIBUTION - ad interests (Privacy Sandbox Topics) —
android.permission.ACCESS_ADSERVICES_TOPICS - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (18)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_ADSERVICES_TOPICSandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.VIBRATEandroid.permission.WAKE_LOCKcom.android.vending.BILLINGcom.android.vending.CHECK_LICENSEcom.dreamgames.royalmatch.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.dreamgames.royalmatch.permission.C2D_MESSAGEcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_IDcom.huawei.appmarket.service.commondata.permission.GET_COMMON_DATAcom.samsung.android.iap.permission.BILLING
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.dreamgames.royalmatch · version 38911 (code 38911)4e2674b93778116bf7482fce17a670a9d0e9d90e9dc731c5716671f0c5331dc202cdbfc5fad42a13f40eb3aec3cf0e51f3badf6ce3747486766fdd3a246b1dcfThe 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.