My Orange Moldova Security & Privacy Scorecard

My Orange Moldova

What This Means for You

Your account login and billing history are stored on your device without a full encryption layer, which means they could be read by someone who has physical access to your unlocked phone.

Recommendation: Trustworthy

This account management app implements strong integrity protections and consent controls that put privacy choices in your hands. Subscriber data and payments are handled securely in transit, and analytics are only shared after your explicit consent. The app is a solid choice for Orange Moldova subscribers, and works best on devices that have not had their system protections modified.

Best For: Orange Moldova subscribers managing their mobile account and making payments

Key Findings

Data Security - 1 finding (1 medium)

Network Security - 1 finding (1 medium)

Code Safety - 7 findings (1 high, 1 medium, 2 low, 3 info)

Privacy - 5 findings (1 medium, 1 low, 3 info)

Privacy Concerns

What Data is Collected

• Account information: your Orange customer ID and phone number are sent to Orange Moldova's servers to manage your account and services.

• Subscriber plan details: your plan name, plan type, and number of lines may be sent to Batch (a push notification service) at login.

• Analytics: your app usage data may be sent to Firebase Analytics, but only after your explicit consent.

• Call log and contacts: read on your device by the anti-spam feature to identify incoming calls. This data stays on your device.

• Location: your location may be sent to Orange Moldova's servers or mapping services if you use location-based features.

Third-Party Data Sharing

The following third parties may receive your data:

• Batch - push notification delivery and marketing communications; may receive your subscriber identity and account attributes
• Google (Firebase) - analytics (consent-gated), crash reporting, push notifications, and app integrity verification
• Huawei (HMS) - push notification delivery for Huawei devices
• AriadNext - identity verification services
• Unissey - identity verification services

Understanding the Scores

Security: 82/100
Privacy: 87/100

Security Breakdown

• Data Security: 50/100 - Login credentials and billing records are stored on your device without an added encryption layer, creating a risk if the phone is accessed by someone else.

• Network Security: 87/100 - All primary connections use encrypted channels, and app integrity verification blocks unofficial clients on every request.

• Code Safety: 80/100 - A service credential for Orange's anti-spam backend is embedded directly in the app package. Separate test-environment credentials are also present in the production app, though they are never active at runtime.

Privacy Breakdown

• Data Collection: 88/100 - The app gathers only what is needed to manage your account. Third-party SDK data collection is explicitly limited through data minimization settings.

• Data Sharing: 88/100 - Analytics sharing is consent-gated with a compliant implementation. Device fingerprinting through the push SDK is disabled.

• User Control: 87/100 - All four categories of analytics and advertising signals default to denied, requiring your opt-in before any analytics data is shared. You can also request data deletion through Orange Moldova's support channel.

Positive Security Features

• Firebase App Check with Play Integrity is active in production, allowing Orange's servers to reject requests from modified or unofficial versions of the app.
• Firebase Analytics defaults all four consent signal types to denied, requiring your explicit opt-in before any analytics data is shared.
• The Batch push SDK has automatic device fingerprinting disabled, reducing data collection to the minimum needed for push delivery.
• Call log and phone state access are used exclusively for the anti-spam feature and are not shared with any analytics or marketing service.
• Data protection infrastructure is present in the codebase and applied in several areas of the app.

Areas for Improvement

GDPR / CCPA Compliance

The app's privacy practices could be strengthened by:

1. Aligning Push Marketing Data Timing with Consent
   Subscriber identity and account attributes are sent to the push notification service at login before verifying whether the user has consented to marketing communications. Linking this transfer to the consent check would better honor user preferences.

2. Encrypting On-Device Account Data
   The data protection tools already present in the codebase could be applied to stored login credentials and billing records, protecting them if the device is accessed by someone other than you.

Security Enhancements

1. Moving the Anti-Spam Service Credential Off-Device
   The service credential used to authenticate with Orange's anti-spam backend is embedded in the app and could be extracted from any downloaded copy. Fetching it dynamically from a secure server would remove it from the app package entirely.

2. Adding a Network Security Configuration
   A network security configuration file could specify which connections are permitted to use unencrypted channels, reducing the exposure surface for third-party components included in the app.

3. Guarding the Payment History Screen
   The payment and action history screen can be opened by other apps installed on the same device without requiring an active login session. Adding a session check before the screen loads would prevent unauthorized access.

Technical Context

App Type: Telecom account management, financial and personal data sensitivity
Classes Analyzed: 3,200
Third-Party Services: 14
Context Tags: financial, sensitive_data, telecom, identity, camera

---

About This Analysis

This security analysis was conducted by CITT (Can I Trust That), an independent security analysis service. We perform static code analysis on Android applications to help users make informed decisions about app security and privacy.

App Details

Developer: Orange Moldova (INTREPRINDEREA MIXTA ORANGE MOLDOVA, SA)
Version: 8.6.0 (versionCode 1143)
Analysis Date: 2026-06-13
Package: com.orange.myorange.omd

Analysis Limitations

• Static analysis only (code review without running the app)
• Based on APK version 8.6.0 analyzed on 2026-06-13
• May not reflect server-side security controls
• Cannot detect all runtime behaviors