Crafting and Building

In short

SDKs found: 21. Companies: 15, of which outside the EEA — 15. Sensitive permissions: 9 — all code inside the app, including embedded SDKs, can use them.

What is inside — embedded SDKs

• ironSource — Unity Technologies, Israel outside EEA advertising
• Tapjoy — Unity Technologies, United States outside EEA advertising
• Unity Ads — Unity Technologies, United States outside EEA advertising
• AppTracer ✓ — VK, Russia outside EEA crash reporting / performance
• myTarget — VK, Russia outside EEA advertising
• myTracker — VK, Russia outside EEA analytics / attribution
• Google AdMob — Google LLC, United States outside EEA advertising
• Google Firebase Analytics — Google LLC, United States outside EEA analytics
• Yandex Mobile Ads — Yandex, Russia outside EEA advertising
• Yandex Mobile Ads (monetization) ✓ — Yandex, Russia outside EEA advertising
• AppLovin — AppLovin Corp., United States outside EEA advertising
• BIGO Ads ✓ — BIGO Technology, Singapore outside EEA advertising
• Pangle — ByteDance, China outside EEA advertising
• Chartboost — Chartboost, United States outside EEA advertising
• Fyber (Digital Turbine) ✓ — Digital Turbine, United States outside EEA advertising
• Huawei Ads Kit — Huawei, China outside EEA advertising
• IAB Open Measurement SDK — IAB Tech Lab, United States outside EEA ad measurement
• InMobi — InMobi, India outside EEA advertising
• Vungle (Liftoff) — Liftoff Mobile, United States outside EEA advertising
• Meta Audience Network — Meta Platforms, United States outside EEA advertising
• Mintegral — Mobvista, China outside EEA advertising

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.