Can I trust Monefy - Budget & Expenses app?
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 want financial records kept fully local
- What it means for you
- The app includes code to send app usage and crash data to Firebase Analytics, Crashlytics, and Sentry. The app includes code to send purchase and subscription activity to RevenueCat. Users can optionally sync financial records to Dropbox or Google Drive. Stored financial data may not be fully protected on device.
- Main concern
- This build contains code for this item; what that code does at run time was not observed.
- The developer's description
- Budget tracker that lets you quickly log daily expenses, track spending across categories, create budgets, and sync data across devices via Google Drive or Dropbox.
- Third-party services
- 14
- 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
An item rated high or above is openTracking 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.
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.
Red flags
Stores an identifier that survives a reinstall
Why this result
This build stores an identifier that survives deleting and reinstalling the app. An identifier of that kind links a new install back to the previous one, so removing the app does not end the profile built against it.
Strengths
- All network communication uses HTTPS
- Dropbox OAuth uses PKCE with system browser, preventing URI scheme hijacking
- Firebase Analytics provides a user opt-out mechanism
- RevenueCat respects limit-ad-tracking opt-out
- Sentry session replay SDK is bundled but not active (sessionSampleRate and onErrorSampleRate both null)
What the app contains
14 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Crashlytics
- Firebase Remote Config
- Firebase Performance
- Firebase Sessions
- Firebase Installations
- Sentry
- Dropbox SDK
- Google Drive API
- RevenueCat
- Google Play Billing
- OkHttp3
- ORMLite
- WorkManager
Libraries
| Library | Version | Advisory |
|---|---|---|
| Room | not recorded | none confirmed |
| Google Play Billing | not recorded | none confirmed |
| Jackson | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Mobile Ads (AdMob) | 12451000 | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
| Google Play Services Location | 12451000 | none confirmed |
| Material Components | not recorded | none confirmed |
| Gson | not recorded | none confirmed |
Show all 21 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
- 13,405
- 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.