Can I trust George Česko?
This scan is more than 90 days old.
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- What it means for you
- The app includes code to send app usage and analytics data to PostHog, Sentry, and Dynatrace for behavioral analytics, crash reporting, and performance monitoring. Firebase is used only for push notifications, not for analytics tracking. The build includes the ThreatMark and Innovatrics SDKs, whose code reads device security signals for fraud protection. Some user data may not be fully protected in all scenarios.
- Main concern
- AES-GCM fixed IV reuse exposes all locker credentials on compromised devices
- The developer's description
- Join 3 million users managing finances with George. Track income, expenses, and investments. Make fast payments, earn cashback, invest in ETFs and funds, apply for products, and access child-friendly banking—all in one secure app.
- Third-party services
- 13
- Findings rated low or higher
- 7
Open on Google PlayOpens the app's listing on Google Play in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
One criterion not metSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Data Minimization
Items recorded, result pending reviewTracking lacks clear disclosure
Why this result
This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
As an EU-regulated bank operating under the Payment Services Directive, Česká spořitelna is required to support account portability and facilitate switching. Bank statements and transaction history are standard exports available through the bank. No proprietary data formats that would trap user financial data or artificial barriers to account closure were found.
Truly Local
One criterion not metContains code to send personal data off the device
Why this result
This app presents itself as working offline or on the device alone, and this build contains code written to send personal data to servers. The check covers analytics, crash reporting, advertising code and any first-party endpoint the code addresses personal data to. Code of this kind is common; what this check reports is the distance between that code and how the app describes itself.
Strengths
- Dual-layer certificate pinning: 17 certificates across 5 domain groups in NSC plus runtime OkHttp interceptor
- No cleartext HTTP: cleartextTrafficPermitted=false globally in production
- Firebase Analytics explicitly disabled — Firebase used exclusively for FCM push
- Hardware-backed Android Keystore with isInsideSecureHardware() verification at runtime
- Backup fully disabled: android:allowBackup=false prevents cloud backup of all app data
- No WebView remote debugging in production builds
- No SSL bypass: no insecure onReceivedSslError override, no empty checkServerTrusted
- The build includes code to place bearer tokens in the Authorization header, never in URL query parameters
- Root and tamper detection: ThreatMark SDK + Innovatrics DOT REQUIRE_SECURE_ENV=1 + SecurityCheckActivity
- Aggressive ProGuard/R8 obfuscation with runtime string obfuscation pool
What the app contains
13 services
Third-party services the scan names in the build:
- Dynatrace OneAgent
- Sentry
- PostHog
- ThreatMark
- Firebase (FCM)
- Azure Communication Services
- HID Global ActivIdentity
- Innovatrics DOT
- GetStream
- Google Maps
- Google Pay / Wallet
- Huawei HMS
- Microblink PhotoPay
Libraries
| Library | Version | Advisory |
|---|---|---|
| ExoPlayer / media3 | not recorded | none confirmed |
| Room | not recorded | none confirmed |
| Lottie | not recorded | none confirmed |
| Dynatrace | not recorded | none confirmed |
| Facebook SDK | not recorded | none confirmed |
| Jackson | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
| Google Play Services Location | 12451000 | none confirmed |
Show all 22 librariesShow fewer
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Files decompiled
- 51,408
- Scan date
- 13 June 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.