Skip to content

Can I trust Budget planner—Expense tracker?

NOT ASSESSED 75 Android Version 9.0.1 (versionCode 363265241) Scanned build downloaded: Store version released: Last checked: com.colpit.diamondcoming.isavemoney Scanned

This scan is more than 90 days old.

This app has an open trust check or a verdict held for review.

Best for
Users comfortable with ad-supported free apps
Avoid if
Users who prefer not to share data with Yandex
What it means for you
The build includes code to send usage and behavioral data to multiple advertising networks, including Facebook Audience Network, AppLovin, Vungle, and Yandex Mobile Ads, for targeted advertising. The build also includes code to send analytics to Firebase Analytics and Yandex AppMetrica, a Russian analytics provider. All backend communication uses HTTPS, and Google Drive backup is gated behind explicit user consent.
Main concern
Unauthenticated deep-link resets PIN, and unencrypted DB is exposed via backup without root
The developer's description
All-in-one budget planner and daily expense tracker simplifying money management. Features receipt scanning, account management, spending dashboard, and six-month budget forecasting. Export reports to CSV, PDF, or Excel.
Third-party services
18
Findings rated low or higher
10

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

    Items recorded, result pending review

    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.

    Financial transactions, budgets, account balances, and payee records are stored on your device. Cloud backup goes to your own Google Drive account, which you control. The advertising and analytics services include code to read general usage and device data but not your financial records, and the analysis found no evidence of code to send your actual spending data, balances, or payee information to third-party servers.

Strengths

  • All backend API communication uses HTTPS
  • Google Drive backup is routed through explicit OAuth2 user consent scope

What the app contains

  • 18 services

    Third-party services the scan names in the build:

    • Firebase Auth
    • Firebase Crashlytics
    • Firebase Messaging (FCM)
    • Firebase Remote Config
    • Firebase Analytics
    • Firebase A/B Testing
    • Google AdMob
    • AppLovin MAX
    • Vungle (Liftoff)
    • Facebook Audience Network
    • Yandex Mobile Ads
    • Yandex AppMetrica
    • Singular
    • Google Sign-In
    • Google Drive API
    • Google Play Billing
    • ZipoApps PremiumHelper
    • ZipoApps Blytics

Libraries

Libraries in the build of Budget planner—Expense tracker
LibraryVersionAdvisory
Roomnot recordednone confirmed
Google Play Billingnot recordednone confirmed
AppLovin MAXnot recordednone confirmed
Facebook Audience Networknot recordednone confirmed
Facebook SDKnot recordednone confirmed
Jacksonnot recordednone confirmed
Glidenot recordednone confirmed
Datatransportnot recordednone confirmed
Google Mobile Ads (AdMob)12451000none confirmed
Google Sign-In12451000none confirmed
Show all 27 libraries

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
26,572
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.