ASB Mobile Banking Security & Privacy Scorecard

ASB Mobile Banking

What This Means for You

App activity and crash data is shared with Adobe, Google, and Firebase. User location may be accessed via Google Maps integration. The app has several serious weaknesses in how financial data is stored and protected on the device.

Recommendation: Use With Caution

Best For: ASB customers comfortable with standard analytics
Avoid If: You want a banking app with strong data protection

Key Findings

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

Network Security - 2 findings (2 medium)

Code Safety - 0 findings

Privacy - 2 findings (2 high)

Privacy Concerns

What Data is Collected

The app collects in-app activity, crash and diagnostic data, and location information through its Google Maps integration.

Third-Party Data Sharing

Data is shared with the following third-party services:

• Adobe Marketing Cloud - marketing and behavioral analytics
• Akamai Bot Manager - traffic filtering and bot detection
• Firebase Crashlytics - crash reporting and diagnostics
• Firebase Cloud Messaging - push notification delivery
• Google Maps - location services

Understanding the Scores

Positive Security Features

• No notable positive security practices were identified in this version of the app.

Areas for Improvement

• Financial data stored locally on the device is not adequately protected, meaning user data may not be fully protected if the device is lost or stolen.
• The app's internal code structure has significant weaknesses that could allow someone with device access to retrieve sensitive account information.
• Users have limited ability to control what personal data the app collects or opt out of sharing it with third-party analytics services.

About This Analysis

This scorecard is based on automated static analysis of the app's published code and configuration. It reflects the app as it existed at the time of the scan and may not capture all runtime behaviors.

App Details