App analysis · 12.10.2026

RFM

pt.rfm.android · version 1.10.0

12SDKs found

5companies

5companies outside the EEA

7sensitive permissions

In short

SDKs found: 12. Companies: 5, of which outside the EEA — 5. Sensitive permissions: 7 — 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 IMA SDK — Google LLC, United States outside EEA advertising
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
Huawei Ads Kit — Huawei, China outside EEA advertising
InMobi — InMobi, India outside EEA advertising
WeChat OpenSDK — Tencent, China outside EEA social login

Sensitive permissions (7)

approximate location — android.permission.ACCESS_COARSE_LOCATION
accounts on the device — android.permission.GET_ACCOUNTS
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 (17)

android.permission.ACCESS_ADSERVICES_AD_ID
android.permission.ACCESS_ADSERVICES_ATTRIBUTION
android.permission.ACCESS_ADSERVICES_TOPICS
android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_NETWORK_STATE
android.permission.FOREGROUND_SERVICE
android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK
android.permission.GET_ACCOUNTS
android.permission.INTERNET
android.permission.POST_NOTIFICATIONS
android.permission.VIBRATE
android.permission.WAKE_LOCK
android.permission.WRITE_EXTERNAL_STORAGE
com.google.android.c2dm.permission.RECEIVE
com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
com.google.android.gms.permission.AD_ID
pt.rfm.android.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION

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: pt.rfm.android.apk (16.0 MB)

Package: pt.rfm.android · version 1.10.0 (code 139)

Android: minimum API 23, target API 35

File SHA-256: cff9faf9de37f81499a8cd03f97aba10b31a24314cc4a19ab642262ed4259bb5

Developer signature (SHA-256): b5161667906881d85fde523265620cb7ec91539de2fadd0c9439c371d239173f

Signed by: Grupo Renascença (Lisbon, PT) · EEA · key since 2018-07-10

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