Privacy Policy

Last updated: August 2, 2026

This Privacy Policy explains how Personal Finance Manager (the "App", "we", "us") handles information when you use the App. The App is built around a simple principle: your financial data lives on your device. We do not run a server that stores your transactions, contacts, balances, or notes, and we do not sell your data.

If anything here is unclear, contact us any time at mediamansoftwaresolutions@gmail.com.

1. Information processed on your device

Financial data you enter

Expenses, income, transfers, lending/borrowing entries, contacts, categories, and accounts you create are stored in a local database on your device, encrypted at rest (SQLCipher, AES-256). We have no access to this data unless you explicitly choose to back it up (see below) or share it with us yourself, for example by emailing us for support.

Notifications

If you grant notification access, the App reads notifications from banking and wallet apps on your device to recognize transaction alerts, so it can suggest a ready-made entry for you to review and confirm. This detection runs entirely on your device — notification content is never uploaded, transmitted, or stored by us on any server. This only catches transactions your bank or wallet actually sends as a notification; the App does not read SMS messages. You can revoke notification access at any time in Android Settings without losing any previously entered data.

Camera

If you use the bill-scanning feature, the App uses your camera and processes the photo with on-device text recognition to help you fill in an entry. Photos are not uploaded anywhere by the App and are not retained beyond the scanning session unless you choose to keep the image yourself.

Biometric unlock

If you enable the optional app lock, biometric authentication (fingerprint/face) is handled entirely by your device's operating system. The App never receives, stores, or transmits your biometric data — it only receives a yes/no result from the OS indicating whether you unlocked successfully.

2. Optional cloud backup (Google Drive)

Backup is off by default. If you turn it on, the App will:

Ask you to sign in with a Google account, using Google Sign-In.
Request access limited to its own hidden application-data folder in your Drive (the drive.appdata scope) — not your general Drive files or folders.
Encrypt your backup (AES-256-GCM) with a passphrase that only you set and only you know, before it ever leaves your device. We cannot read the contents of your backups, and if you forget your passphrase we cannot recover it for you.

You can disable backup and sign out of Google at any time from Settings → Backup within the App. See our Data Deletion page for how to remove backup data entirely.

3. Advertising (Google AdMob)

Free use of the App shows ads served by Google AdMob. AdMob may collect device and advertising identifiers (such as your advertising ID), general device information, and ad interaction data in order to serve, measure, and personalize ads, in accordance with Google's advertising and privacy policies. This applies only while you are on the free tier — Premium subscribers do not see ads, and this ad-related data collection does not apply to them.

4. Crash & diagnostic reporting (Firebase Crashlytics)

We use Firebase Crashlytics to automatically receive crash and error reports — things like stack traces, device model, OS version, and app version — so we can find and fix bugs. These reports do not include your financial entries, contacts, or backup passphrase.

5. Subscription purchases (Google Play Billing)

Premium subscription purchases are handled entirely by Google Play Billing. We receive only a purchase and entitlement status (e.g., "subscribed" / "not subscribed") — we never see your payment method, card details, or billing address. Refunds, cancellations, and payment management are handled through Google Play; see Billing in our Terms of Service.

6. Permissions this app requests

Permission	Why we ask
Internet / network state	Live currency exchange rates, ads, cloud backup, and crash reporting.
Notification access	Optional, on-device transaction detection from bank/wallet notifications.
Camera	Optional bill scanning with on-device text recognition.
Post notifications	Reminders and alerts for detected transactions and recurring entries.

Sensitive permission, used narrowly. Notification access exists solely to detect transactions and turn them into pre-filled entries for your review — nothing is transmitted off your device for this purpose, and every detected entry can be edited or discarded before it's saved.

7. Data security

Your on-device database is encrypted at rest using SQLCipher (AES-256). Backup passphrases and app-lock keys are protected using the Android Keystore. Any CSV/PDF export or Drive backup you create stays on your device or in your own Google Drive — we do not receive a copy.

8. Data retention and your choices

Uninstalling the App, or clearing its storage in Android Settings, permanently deletes all local data.
You can revoke notification access, camera, or notification-post permissions at any time in Android Settings without losing previously entered data.
You can turn off ad personalization in your device's Google Settings → Ads.
You can disable backup, sign out of Google, and remove Drive backup files at any time — see Data Deletion for details.

9. Children's privacy

The App is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will address it.

10. Changes to this policy

We may update this Privacy Policy as the App changes. We'll update the "Last updated" date above when we do, and material changes will be reflected here before they take effect.

11. Contact us

Questions about this policy or your data? Email mediamansoftwaresolutions@gmail.com.