Telegram
Telegram requests extensive permissions (71 total, 41 granted) including location, contacts, call logs, and camera - many beyond typical messaging needs. However, the app offers strong encryption (MTProto 2.0 for secret chats, TLS for cloud chats), is actively maintained, and has no major known security breaches. Risk is moderate due to permission scope and data collection practices, but mitigated by transparent encryption and regular updates.
So kommen wir auf 48.
71 total permissions requested; 41 granted including location, call logs, contacts, camera, microphone, clipboard
READ_CALL_LOG, ACCESS_BACKGROUND_LOCATION, READ_CLIPBOARD not essential for messaging
Collects phone number, contacts, IP address, device info; shares with third-party analytics
MTProto 2.0 E2E for secret chats; TLS for cloud chats; open-source protocol
Strong privacy advocacy; weekly updates; established since 2013
Firebase Analytics, ad SDKs in some regions
Servers in multiple countries; varying legal pressures; GDPR compliance unclear
Policy vague on data retention and third-party sharing specifics
Versteckt im Code.
Was sie verlangt.
Can read your call history - unnecessary for messaging
Tracks your location even when the app is closed
Can read anything you copy to clipboard
Can manage accounts on your device
Full access to your files and media
Knows your exact GPS coordinates
Aus dem Scan.
Weiter lesen.
What is a tracker in an app, and why should you care
A tracker is third-party code the developer bundled in. It reads device IDs, coarse location and your app list, with no ...
Why does this app need microphone permission?
Why do apps request microphone, location, or contacts access they don't need? A field guide to Android permission creep ...
Ähnliche Risikoprofile.
Scanne Telegram selbst.
Hol dir den vollständigen Report auf deinem Gerät - mit Echtzeit-DEX-Analyse, Berechtigungs-Audit und Breach-Monitoring. Kostenlos, ohne Konto.