App analysis · 17.10.2026

PPSS22 Emulator - PS2 Emulator

com.ppss22.emulator · version 446

17SDKs found
13companies
13companies outside the EEA
5sensitive permissions

In short

SDKs found: 17. Companies: 13, of which outside the EEA — 13. Sensitive permissions: 5 — 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
  • Google AdMob — Google LLC, United States outside EEA advertising
  • Google User Messaging Platform — Google LLC, United States outside EEA consent platform
  • 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
  • Pangle — ByteDance, China outside EEA advertising
  • Chartboost — Chartboost, United States outside EEA advertising
  • Fyber (Digital Turbine) ✓ — Digital Turbine, United States 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
  • myTarget — VK, Russia outside EEA advertising

Sensitive permissions (5)

  • write files on the device — android.permission.WRITE_EXTERNAL_STORAGE
  • 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 (14)
  • android.permission.ACCESS_ADSERVICES_AD_ID
  • android.permission.ACCESS_ADSERVICES_ATTRIBUTION
  • android.permission.ACCESS_ADSERVICES_TOPICS
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.BLUETOOTH_CONNECT
  • android.permission.FOREGROUND_SERVICE
  • android.permission.INTERNET
  • android.permission.READ_BASIC_PHONE_STATE
  • android.permission.VIBRATE
  • android.permission.WAKE_LOCK
  • android.permission.WRITE_EXTERNAL_STORAGE
  • com.google.android.gms.permission.AD_ID
  • com.ppss22.emulator.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
  • com.ppss22.emulator_archos.permission.FULLSCREEN.FULL

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

File: com.ppss22.emulator.xapk (60.1 MB)
Package: com.ppss22.emulator · version 446 (code 446)
Android: minimum API 26, target API 37
File SHA-256: 74dd58bcd7b72114ce117d749b6a7a395bc1467cab3ed243339243a82e3d498a
Developer signature (SHA-256): 9cfb654cadeb37edd98c1f358fc0f577a03890fbb0c5a7cd87a4d4f23f44b09b
Signed by: Google Inc. (Mountain View, US) · outside EEA · key since 2022-12-05
Library: 75 SDK · 81 permissions · 13c27d15ac2e
File source: APKPure (через apkeep)

The 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.

Download card (Markdown)

← All analysed apps · Check your own app