Fio Smartbanking CZ Security & Privacy Scorecard

Android

85
Overall trust score
Trustworthy
78
Security
100
Privacy

No analytics, advertising, or behavioral tracking SDKs are present. Firebase is used only for push notifications, with analytics explicitly disabled. User data stays on device and travels to bank servers only, with no third-party data sharing detected.

Best for

Everyday banking with strong privacy expectations

Findings

  • 0 critical
  • 1 high
  • 3 medium
  • 0 low
  • 0 info

1 issue identified across security and privacy analysis.

Top security issues

  • Raw SHA-256 Used as PIN-Derived Key for Banking Authentication Private Key Wrapping
  • AES-256-ECB NoPadding for Signing Key Storage — No IV, No Integrity Protection
  • PSD2 OAuth Redirect URI Not Validated Before Opening — Potential URI Injection

Top privacy issues

  • FLAG_SECURE Set Only on Pause — Banking UI Screenshottable While Active
  • Raw SHA-256 Used as PIN-Derived Key for Banking Authentication Private Key Wrapping
  • PSD2 OAuth Redirect URI Not Validated Before Opening — Potential URI Injection

Full analysis

Fio Smartbanking CZ

What This Means for You

All your banking transactions and account activity are sent directly to Fio banka, keeping your financial life between you and your bank. The main area for improvement is how your PIN protects the keys used to authorize payments.

Recommendation: Trustworthy

Fio Smartbanking is a secure Czech banking app with strong network protections, no advertising or tracking, and biometric authentication. Ideal for Czech banking customers who value privacy and need reliable financial management tools.

Best For: Czech banking customers who want a no-tracking, no-ads app with strong network security and zero third-party analytics

Key Findings

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

Network Security - 0 findings

Code Safety - 1 finding (1 medium)

Privacy - 0 findings

Privacy Concerns

What Data is Collected

  • Account and banking information: sent to Fio banka's servers to power account management, payments, and transactions
  • Location: accessed on your device for ATM and branch finder features
  • Contacts: accessed on your device to enable payments by phone number
  • Camera: used on your device for QR code and payment slip scanning

Third-Party Data Sharing

No third-party data sharing was identified in this analysis.

Understanding the Scores

Security: 78/100
Privacy: 100/100

Security Breakdown

  • Data Security: 67/100 - Private key storage for payment authorization uses a protection method that could be significantly strengthened. Other aspects of data handling meet standard practices for a banking app.
  • Network Security: 100/100 - All communications with Fio banka's servers are strongly encrypted and protected against interception, with unencrypted traffic fully blocked.
  • Code Safety: 88/100 - The app is built with solid security practices throughout. One area around third-party payment redirect handling could be further hardened.

Privacy Breakdown

  • Data Collection: 100/100 - Only the data needed to deliver banking services is involved. No advertising, analytics, or behavioral tracking tools are present.
  • Data Sharing: 100/100 - No data reaches advertising networks, analytics companies, or other third parties outside Fio banka's own infrastructure.
  • User Control: 100/100 - You remain in full control of your account data, with the ability to request data deletion and configure the app to your preferences.

Positive Security Features

  • All connections to Fio banka's servers are verified against Fio banka's own trusted certificates, not general internet authorities
  • Unencrypted network traffic is fully blocked at the app level
  • Backup of sensitive data to cloud or via USB is disabled, protecting private key material if your device is accessed by others
  • Biometric authentication is protected by hardware-level security on your device
  • No advertising, analytics, attribution, or behavioral tracking tools were detected
  • Firebase Analytics is explicitly disabled, including advertising ID collection
  • Login session data is held only in memory and never written to device storage
  • Secure link handling prevents other apps from hijacking banking-related links on your device
  • The stronger key protection method (with random salt and memory-intensive processing) is already built into the app and requires only a configuration update to activate

Areas for Improvement

GDPR / CCPA Compliance

The app's privacy practices could be strengthened by:

  1. Screen Content Protection
    Banking screens showing account balances, transaction history, and payment details can be captured by screenshot tools or accessibility services while you are actively using the app. Keeping screen protection active during use would prevent your sensitive financial information from being captured without your consent.

Security Enhancements

  1. Strengthen PIN Key Protection
    The method used to protect payment signing keys derived from your PIN relies on a single fast-processing step, which makes guessing the PIN significantly faster for someone who has extracted key files from your device. Switching to the slower, memory-intensive method already present in the app would make such attempts vastly more time-consuming and impractical.

  2. Payment Redirect Validation
    After third-party payment (PSD2) authorization, the destination the app opens is not verified against a list of trusted addresses. Validating this redirect would prevent malicious redirection to fraudulent pages.

  3. Key Storage Mode Upgrade
    Signing keys are wrapped using an encryption mode that does not protect against undetected changes on a compromised device. Upgrading to an authenticated encryption approach would ensure that any tampering with stored key material is detected before use.

Technical Context

App Type: Financial / Banking (sensitive data)
Classes Analyzed: 1,200
Third-Party Services: 13 identified (primarily infrastructure and networking libraries; no analytics or advertising SDKs)
Context Tags: financial, sensitive_data


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: Fio banka, a.s.
Version: 2.10.24-cz (Build 396)
Analysis Date: June 13, 2026
Package: cz.fio.sb2

Analysis Limitations

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

Versions & scan history

ScanDateOverall score
#1 (current) 85/100