Skip to content

Can I trust Money manager & expenses?

unTRUSTED 84 Android Version 1.12.0 (versionCode 4237) Scanned build downloaded: Store version released: Last checked: ru.innim.my_finance Scanned

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.

Avoid if
Users who prefer apps with no advertising SDKs
What it means for you
The build includes the AppMetrica (Yandex), Facebook, and VK SDKs, whose code reads app usage data for analytics. Ads are served through Google AdMob and Yandex Mobile Ads. Locally stored data is well protected, though the app includes code that may send some app data with less protection than expected on certain connections.
Main concern
Unencrypted financial database readable on rooted/accessed devices
The developer's description
Money manager & expenses tracker with comprehensive budgeting tools. Track transactions, create custom categories, view spending charts, and receive reminders for recurring payments. Supports multiple currencies.
Third-party services
12
Findings rated low or higher
6

How the score and the label work

Open on Google PlayOpens the app's listing on Google Play in a new tab.

Full findings

Open this scan in your dashboard

The account that ran this scan sees every finding and the Rescan button there.

Trust checks

  • Secure by Design

    One criterion not met

    Security 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

    One criterion not met

    Tracking 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

    Items recorded, result pending review

    Disclosure 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

    Strong

    No 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.

  • Truly Local

    Strong

    Stays on the device

    Why this result

    This app presents itself as working offline or on the device alone. The check looks for any code written to send personal data to a server, including analytics, crash reporting and advertising code. None was recorded in this build.

    Your actual financial records (transactions, balances, and budgets) are stored on your device, and the code names only your personal Google account, through Android's standard backup, as their destination. No code was found to transmit financial transaction content to advertising companies, data brokers, or other third parties. Analytics SDKs in the build include code that reads only basic device and session information, not the details of your spending or accounts.

Strengths

  • Android Keystore-backed credential storage via FlutterSecureStorage (AES256-GCM)
  • Firebase Analytics explicitly disabled at manifest level
  • AppAuth PKCE for Google OAuth2 flows with state parameter validation
  • No cleartext HTTP traffic permitted
  • No server-side secrets or credentials embedded in APK
  • Proper TLS hostname verification — no ALLOW_ALL bypass
  • AdMob measurement deferred until user consent (DELAY_APP_MEASUREMENT_INIT=true)

What the app contains

  • 12 services

    Third-party services the scan names in the build:

    • Firebase Crashlytics
    • Firebase Remote Config
    • Firebase Messaging (FCM)
    • AppMetrica (Yandex) v7.10.0
    • Google Mobile Ads (AdMob)
    • Yandex Mobile Ads
    • Google Privacy Sandbox
    • Facebook SDK
    • VK SDK 3.5.0
    • Google Sign-In / AppAuth
    • Sign in with Apple
    • Google Play Billing

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
17,587
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.