Intesa Sanpaolo Mobile Security & Privacy Scorecard

Intesa Sanpaolo Mobile

com.latuabancaperandroid | Version 4.0.4 (Build 25120101) | Scanned: January 31, 2026

What This Means for You

User activity is shared with analytics, marketing, and behavioral tracking services including Adjust and Salesforce Marketing Cloud. Crash reports and device data are collected by third parties. User data may not be fully protected during transmission and in storage, which is a significant concern for an app that handles sensitive financial information.

Recommendation: Unsafe

Best For: Intesa Sanpaolo customers who need mobile banking
Avoid If: You use the app on shared or work-managed devices

Key Findings

Data Security - 6 findings (2 critical, 1 high, 3 medium)

Network Security - 3 findings (1 critical, 2 high)

Code Safety - 0 findings

Privacy - 5 findings (1 critical, 1 high, 3 medium)

Privacy Concerns

What Data is Collected

Device identifiers, behavioral patterns, crash reports, and technical diagnostics about the device are collected. Multiple third-party services embedded in the app gather data about how users interact with it and the device it runs on.

Third-Party Data Sharing

User data reaches a broad set of external parties: Adjust and Salesforce Marketing Cloud receive data for advertising and marketing purposes, Tealium and Dynatrace receive behavioral and performance data, Firebase Crashlytics receives crash and device reports, and Cleafy, CA Risk Minder, Unblu, Cisco Webex, and Realm provide operational and engagement services that also receive app data.

Understanding the Scores

Positive Security Features

• The app relies on standard platform-level security without implementing notable additional protective layers.

Areas for Improvement

• Protection of financial data during transmission and in storage requires significant strengthening for an app handling sensitive banking information.
• Marketing and advertising data collection should be made optional, so users are not required to share banking activity with third-party services.
• More user-facing controls are needed so users can manage what the app collects and limit which outside parties receive their information.

About This Analysis

This scorecard is based on static analysis of the app's code and configuration. It reflects observable behaviors and settings at the time of the scan and does not capture all possible runtime behaviors.

App Details