Telegram Security & Privacy Scorecard

Telegram

Version: 12.3.1 (Build 63852)
Scan Date: January 31, 2026

What This Means for You

Messages are delivered through Google's Firebase infrastructure, and the device interacts with Google Play Services and SafetyNet. Payments processed through Stripe follow standard financial data handling. Usage data touches several Google-operated services, though no advertising or behavioral tracking SDKs are present.

Recommendation: Use With Caution

Best For: Everyday messaging with standard Google integrations

Key Findings

Data Security - 9 findings (1 critical, 1 high, 4 medium, 3 low)

Network Security - 2 findings (1 medium, 1 low)

Code Safety - 0 findings

Privacy - 1 finding (1 medium)

Privacy Concerns

What Data is Collected

Telegram collects device identifiers and usage information through Google Play Services and Firebase. Payment details are handled by Stripe when users make in-app purchases. User location may be accessed through Google Maps when location-sharing features are used.

Third-Party Data Sharing

User data is shared with the following third-party services:

• Google (Firebase Cloud Messaging, Firebase Remote Config, Google Play Services, Google Play Billing, Google Maps, ML Kit, SafetyNet): Message delivery, app configuration, device security checks, and billing.
• Stripe: Processing of any payments made within the app.
• ZXing: QR code reading, processed locally on the device.
• NanoHTTPD: Local network functionality within the app.

No advertising networks or behavioral profiling services are embedded in this build.

Understanding the Scores

Positive Security Features

• Data collection exposure is minimal: the app scores 100/100 for Data Collection, reflecting that it requests only what is needed for core functionality.
• Users retain strong control over their data, reflected in a perfect User Control score of 100/100.
• No advertising or behavioral tracking services are included in this version of the app.

Areas for Improvement

• Local data stored on the device is not fully protected, meaning sensitive information could be exposed if someone gained physical access to the device.
• Some network communications could be made more robust to better protect user data while it travels between the device and Telegram's servers.
• Certain internal operations could be handled more securely to reduce risk if the app is running on a rooted or compromised device.

About This Analysis

This scorecard is generated through automated static analysis of the Android application binary. It reflects the security and privacy posture of this specific version and build.

App Details