App analysis · 12.10.2026

eTilbudsavis

com.eTilbudsavis.eTilbudsavis · version 7.2

2SDKs found
1companies
1companies outside the EEA
2sensitive permissions

In short

SDKs found: 2. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 2 — 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
  • Google Firebase Analytics — Google LLC, United States outside EEA analytics

Sensitive permissions (2)

  • approximate location — android.permission.ACCESS_COARSE_LOCATION
  • precise location — android.permission.ACCESS_FINE_LOCATION
All manifest permissions (27)
  • android.permission.ACCESS_COARSE_LOCATION
  • android.permission.ACCESS_FINE_LOCATION
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.FOREGROUND_SERVICE
  • android.permission.INTERNET
  • android.permission.POST_NOTIFICATIONS
  • android.permission.READ_APP_BADGE
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.VIBRATE
  • android.permission.WAKE_LOCK
  • com.anddoes.launcher.permission.UPDATE_COUNT
  • com.eTilbudsavis.eTilbudsavis.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
  • com.google.android.c2dm.permission.RECEIVE
  • com.htc.launcher.permission.READ_SETTINGS
  • com.htc.launcher.permission.UPDATE_SHORTCUT
  • com.huawei.android.launcher.permission.CHANGE_BADGE
  • com.huawei.android.launcher.permission.READ_SETTINGS
  • com.huawei.android.launcher.permission.WRITE_SETTINGS
  • com.majeur.launcher.permission.UPDATE_BADGE
  • com.oppo.launcher.permission.READ_SETTINGS
  • com.oppo.launcher.permission.WRITE_SETTINGS
  • com.sec.android.provider.badge.permission.READ
  • com.sec.android.provider.badge.permission.WRITE
  • com.sonyericsson.home.permission.BROADCAST_BADGE
  • com.sonymobile.home.permission.PROVIDER_INSERT_BADGE
  • me.everything.badger.permission.BADGE_COUNT_READ
  • me.everything.badger.permission.BADGE_COUNT_WRITE

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.eTilbudsavis.eTilbudsavis.xapk (7.2 MB)
Package: com.eTilbudsavis.eTilbudsavis · version 7.2 (code 7000103)
Android: minimum API 24, target API 36
File SHA-256: c0ddc6f71026c6b4446176ab8e7606ce33b83fc1004d055d5ede0220c955ef67
Developer signature (SHA-256): dfdb12ff5895ae629f857bf07a04b4dc9cea7b5067a8133ea805a6c555422ea3
Signed by: eTilbudsavis (Aalborg, DK) · EEA · key since 2010-12-10
Library: 63 SDK · 81 permissions · 2769b78c1753
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