MyFinPal ("the App") is operated by Shivputra Neelakandan / spxandroid ("we", "us", "our"). We are committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights.
In short: your financial records and SMS stay on your device unless you turn on Google Drive backup. Google Firebase handles only your sign-in account and limited technical data (usage, notification token, crash reports). MyFinPal's AI features run on your device. We do not sell your data or show ads. You can delete your account and cloud data in the app at any time. The sections below give the detail.
Your financial records and figures, and your SMS content, stay on your device, in encrypted storage, unless you turn on Google Drive backup. MyFinPal does not send your net worth, income, expenses, transactions, budgets, goals, bills, debts, or any totals or counts of them, to Firebase or to any system operated by MyFinPal. Google Drive backup is off by default and is the only feature that copies your records off the device (section 6).
MyFinPal does not operate its own backend for financial records. Google Firebase and the optional Google Drive backup are still network services (sections 5 and 6).
MyFinPal's AI features (the Pluto assistant, the AI Insights chat and the SMS analyzer) run on your device using Gemini Nano through Android AICore. What you type into them is processed in the mobile and is not uploaded (section 7).
Separately, MyFinPal uses Google Firebase for a limited amount of account and technical data even when Drive backup is off: your sign-in account, contact details you give at sign-up, usage and engagement events, a push-notification token, and crash and performance reports. Section 2 lists exactly what, and section 5 lists each Firebase service. SMS message text is never uploaded.
| Data | Sent to | Purpose |
|---|---|---|
| Name, email address, mobile number (if you enter one), sign-up method (Google, Apple or email) | Cloud Firestore | Account creation, preventing duplicate accounts, account lookup |
| Sign-in identifiers, including an anonymous Firebase account ID | Firebase Authentication | Signing you in and identifying your account in Firebase |
| Feature usage and engagement: screens and Pro features viewed, upgrade-button taps, onboarding steps, session counts, daily active use, and that an action happened (for example that a transaction was added and whether it was income or an expense) — never amounts, balances, scores or totals | Cloud Firestore; Firebase Analytics | Understanding usage and improving the app |
| Device push token (FCM) and platform | Cloud Firestore; Firebase Cloud Messaging | Delivering notifications to your device |
| Crash reports, performance traces, app-instance and device identifiers, your account ID | Firebase Crashlytics, Performance Monitoring and Analytics | Fixing bugs and measuring app speed |
| Data | Sent to | Purpose |
|---|---|---|
| Messages and context you choose to provide in the AI Insights chat, and SMS text you paste into the SMS analyzer | In mobile AI services (Gemini Nano on your device); not uploaded | Generating a reply or reading a transaction |
| Backup file (only if you enable Google Drive backup) | Your Google Drive (hidden app data folder) | Backup and restore |
No financial data (figures, totals, counts or records) is sent to Firebase. Most of the data above is linked to your account. We do not sell any of it.
Sole purpose. MyFinPal uses the SMS permission only to find financial transaction and bill messages (for example bank credits and debits, UPI payments, EMI deductions and bill payments) and turn them into transaction or bill suggestions for you. It is not used for anything else.
What is stored. When you accept a suggestion, the saved transaction keeps the fields you approved (amount, date, category, merchant) and a link to its source message (message ID, sender and text) so you can see where it came from. This stays in MyFinPal's encrypted storage on your device and is included in a Google Drive backup only if you enable one. Your individual transactions, including any source message text, are not uploaded by MyFinPal unless you enable Google Drive backup. The app also keeps a list of message IDs already handled so the same message is not suggested twice. Messages you deny are not saved as transactions.
Every permission below is optional. The app is usable without any of them; the related feature simply stays off. You can revoke each one at any time in Android Settings → Apps → MyFinPal → Permissions.
| Permission | Purpose | Optional? | Data accessed | Leaves the device? | How to revoke |
|---|---|---|---|---|---|
| SMS (READ_SMS) |
Detect bank transactions and bill payments (credits, UPI payments, EMIs) so you can review and import them. | Yes. You can add transactions and bills manually. | Inbox messages: sender, text and date. Read when you run SMS sync, and while the app is open to check newly received messages for you to review. | SMS text is analysed on the device and is not uploaded by MyFinPal. Transactions you import become ordinary MyFinPal records; they leave the device only if you turn on Google Drive backup (section 6). | Android Settings → Apps → MyFinPal → Permissions → SMS → Don't allow. |
| Camera (CAMERA) |
Scan a family member's QR code in the Family section. | Yes. You can join or add members without scanning. | Live camera frames, used only while the scanner screen is open, to read the QR code. Photos are not taken or saved. | No. Frames stay on the device. The code you scan is used to add the member. | Android Settings → Apps → MyFinPal → Permissions → Camera → Don't allow. |
| Contacts (READ_CONTACTS) |
Let you pick people from your address book when creating split-expense groups and debt entries. | Yes. You can type names manually. | Contact names and, in Group Split, phone numbers and email addresses shown in the picker. | The contact list itself is not uploaded. Names or details you select are saved as records in MyFinPal and leave the device only if you enable Google Drive backup. | Android Settings → Apps → MyFinPal → Permissions → Contacts → Don't allow. |
| Notifications (POST_NOTIFICATIONS) |
Bill due dates, budget alerts, reminders and messages from us. | Yes. | No personal data is read. The app schedules reminders from your own bills and budgets on the device. | Reminders are generated locally. To deliver push messages, Firebase Cloud Messaging registers a device token, which is stored with your account (section 5). | Profile → Settings → Notifications (in the app), or Android Settings → Apps → MyFinPal → Notifications. |
| Biometrics (USE_BIOMETRIC, USE_FINGERPRINT) |
Unlock the app with fingerprint or face instead of a PIN. | Yes. A PIN can be used instead, or no lock at all. | None. Android performs the match and tells the app only whether it succeeded. MyFinPal never receives, stores or transmits fingerprint or face data. | No. | Profile → Settings → Security & Password → turn off biometric unlock, or remove the permission in Android Settings → Apps → MyFinPal → Permissions. |
MyFinPal also lets you attach receipt images to expenses. These are picked from your gallery or files (not taken with the camera), stored on your device, and included in a Google Drive backup if you enable it. The app also uses a foreground service so a running SMS sync can finish while the app is in the background; it collects nothing additional.
| Service | What we use it for |
|---|---|
| Firebase Authentication | Sign-in with Google, Apple or email. The app may also create an anonymous Firebase account (no name or email) so that it can use Firebase services such as Cloud Firestore and Cloud Messaging before or without a full sign-in. |
| Cloud Firestore | Stores the account, usage and device-token data listed in section 2. It does not store any financial data. |
| Firebase Cloud Messaging | Push notifications. Registers a device token linked to your account. |
| Firebase Analytics | Usage events and device/app identifiers, linked to your account ID. |
| Firebase Crashlytics | Crash and error reports with device and app-state information, linked to your account ID. |
| Firebase Performance Monitoring | Timing traces (for example app start-up and SMS processing) and network performance data. |
| Firebase Remote Config | Fetches feature flags and messages from us. Sends app-instance identifiers to Firebase to do so. |
| Google Sign-In / Google Drive API | Sign-in and optional backup (section 6). |
MyFinPal does not use Firebase Storage. Google processes this data under its own terms; see policies.google.com/privacy and firebase.google.com/support/privacy.
Cloud backup is off by default. If you turn it on and sign in with Google, MyFinPal asks for the Google Drive app data permission (drive.appdata). Your backup file (myfinpal_backup.json) is then saved to a hidden application-data folder in your own Google Drive. That folder is visible only to MyFinPal under your Google account; the app cannot see your other Drive files, and we cannot access your Drive.
The backup can include your MyFinPal records and app data: transactions, income, savings, assets, liabilities, debts, budgets, bills, goals, calendar items, groups, recurring records, accounts and projection data. It can also include your profile photo, receipt images and savings attachments when present. It does not include your login credentials or security settings. The backup is protected by Google's encryption in transit and at rest and by your Google account security; it is not separately encrypted by MyFinPal with a key only you hold. MyFinPal never deletes this backup for you, not even when you delete your account, because it is stored in your own Google account. You can remove it yourself under Google Drive → Settings → Manage apps → MyFinPal → Delete hidden app data.
The Pluto assistant, the AI Insights chat and the SMS analyzer run in the mobile using Gemini Nano through Android AICore on supported devices. Your messages, the context you choose to provide, and any SMS text you paste stay on your device and are not uploaded by MyFinPal. On devices that do not support Gemini Nano these features are unavailable. AI responses give general planning help only; they are not regulated investment, tax, legal or lending advice.
Data stored on your device is kept in encrypted storage, and you can add a PIN or biometric lock. Data sent to Firebase or Google Drive travels over encrypted connections (HTTPS/TLS). As explained in section 6, the Google Drive backup file is protected by Google and by your Google account, not by a separate key held only by you. No system is completely secure, so please also keep your phone and Google account protected. If you suspect unauthorised access, contact us using the details in section 16.
Google may store and process Firebase and Google Drive data on servers in India or in other countries. By using those features you understand your data may be processed outside India, under the safeguards of those providers.
The myfinpal.app website does not use analytics or advertising cookies. Its pages load fonts from Google Fonts, so your browser contacts Google when you visit. The early-access button opens your own email app; we receive your email address only if you send the message.
MyFinPal is intended for people aged 18 and over and is not directed at children. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, contact us and we will delete it.
We may update this policy from time to time. We will post the new version on this page with a new version number and date, and for material changes we also show a summary inside the app the next time you open it after an update. If you do not agree with a change, you can stop using the app and delete your account.
Questions about this privacy policy, or requests to access, correct or delete your data? This is also our data-protection and grievance contact. We will acknowledge your request and respond within a reasonable time.
Contact us at:
Email: admin@myfinpal.app
Operator: MyFinPal, operated by Shivputra Neelakandan / spxandroid
Location: Chennai, Tamil Nadu, India
Current version: 1.0. Material changes are listed below and are also shown inside the app the next time you open it after an update.
| Version | Date | Material changes |
|---|---|---|
| 1.0 | September 2026 | First published version. |