MyPaisa Privacy Policy
Your financial data stays on your device — always.
Updated: October 10, 2026
Request deletion of MyPaisa verification data
1. Introduction
MyPaisa ("the App") is a personal finance management application developed for individual use in India. This Privacy Policy explains how the App handles information on your device and verifies trial and Pro access. Financial records are stored locally; trial and Pro access are verified by a secure server.
By installing or using MyPaisa you agree to the practices described in this policy. If you do not agree, please uninstall the App.
2. Information the App Accesses
MyPaisa requests the following Android permissions. All data accessed through these permissions is processed entirely on your device.
| Permission | Why it is needed | Data stored? |
|---|---|---|
| READ_SMS / RECEIVE_SMS | Scans SMS on-device so MyPaisa can prepare debit and credit transactions for your review. Only SMS with an amount, debit/credit wording, and masked account/card digits are considered. OTP, login, security, personal, promotional, balance-only, statement, and reminder messages are ignored. | No SMS body stored |
| USE_BIOMETRIC / USE_FINGERPRINT | Allows you to unlock the App using fingerprint or face recognition as an alternative to your PIN. Biometric data itself is managed entirely by the Android operating system; the App never sees or stores raw biometric data. | OS-managed |
| INTERNET / ACCESS_NETWORK_STATE | Fetches public market prices using ticker symbols and scheme codes, and connects to our access service to verify trial and Pro access. Financial records, holdings quantities and CAMS documents are not sent to the account service. | Account verification only |
| POST_NOTIFICATIONS | Sends local reminders for upcoming bill due dates. Notifications are generated on-device by Android's WorkManager; no notification content is transmitted externally. | On-device only |
| RECEIVE_BOOT_COMPLETED | Reschedules bill-reminder alarms after the device reboots so you don't miss payment deadlines. | On-device only |
| VIBRATE | Provides haptic feedback on button taps for a better user experience. | On-device only |
3. How Your Data is Stored
All financial information you enter — accounts, transactions, investments, budgets, loans, bills — is stored in a local SQLite database on your device. This database is encrypted using SQLCipher (AES-256) with a unique encryption key generated on your device and secured using Android KeyStore. Financial records are not sent to the account service. An explicit password-encrypted backup includes the data and restore key at the destination you choose.
Your PIN is never stored in plain text. New PINs are hashed using PBKDF2-HMAC-SHA256 with a random salt before being saved to Android DataStore Preferences. The App cannot recover your original PIN.
android:allowBackup="false"
and explicitly excludes sensitive files from Android's Auto Backup service. Your financial
data is not automatically backed up to Google Drive or any other cloud service.
Retention: your data remains on your device until you uninstall the App or manually delete records within it. Uninstalling the App removes all locally stored data.
User-controlled backups
New backups are password-encrypted before being written to the file destination you choose. The archive includes the financial database and the key needed to restore it on another device. Keep your backup password safe; it cannot be recovered by us. Legacy ZIP backups are still accepted for restore, but are not password protected. Files may be stored with a cloud provider if you explicitly choose that provider in Android's file picker. Cached trial verification and Pro licences are not included in financial backups. Restoring a backup does not renew the original trial.
Automatic trial and Pro verification
MyPaisa 1.5.0 and later do not require Google sign-in or create an app account. To preserve your original 30-day trial after a reinstall, the App reads Android's app-scoped device identifier and sends a SHA-256 hash of it over HTTPS to our access service. The raw Android identifier stays on your phone. The service stores a further hashed record key and your original trial start and end dates in a private Google spreadsheet. This identifier is scoped to the App signing key, Android user profile and device; it is not your Google Play account or email address. A new device or factory reset may create a different trial identity.
The trial lasts 30 calendar days from its original start, including days when the App is uninstalled. Original dates from older App versions and restored backups may shorten the trial and cannot extend it. Trial history is retained to prevent normal reinstall resets.
Existing and new Google Play purchases are verified automatically when you open or return to the App. Purchase receipts are sent over HTTPS to our access service and checked with Google Play. Active lifetime purchases restore without MyPaisa sign-in; cancelled, refunded or pending purchases do not unlock Pro. The current restoration endpoint does not persist submitted purchase tokens in the database. Payment card details are handled by Google Play.
The service runs on Google Apps Script with a private Google spreadsheet. Only the service owner and explicitly authorized editors can access the spreadsheet. Google providers may process technical connection and service logs under their own policies. Application code does not log raw device identifiers, identity tokens, session credentials or purchase tokens. Financial records, holdings quantities, SMS messages and CAMS documents are not sent to this service.
Local cached access is encrypted with Android KeyStore and excluded from financial backups. Cached verification lasts at most 24 hours within the same device boot; reconnect after reboot or expiry. Uninstalling removes the local cache, but does not delete server trial history.
For users who signed in with versions before 1.5.0, existing hashed account trial history, purchase ownership history and saved verification records are retained for compatibility with those versions. Older sessions expire after 30 days. The new App removes local Google session credentials after carrying forward the original trial date and does not request Google identity tokens. To request deletion of legacy account sessions and saved purchase tokens, use the contact in Section 11 with the subject "MyPaisa account deletion". Identity verification is required; limited hashed trial dates and purchase ownership history remain to prevent abuse. You may also request deletion of device verification data through the same contact; we will explain any limited trial history that must be retained. Do not email financial statements, passwords or purchase tokens.
4. What We Do Not Collect
MyPaisa does not:
- Upload your imported CAMS statements or SMS messages to our servers.
- Upload your saved financial transactions, account balances or investment holdings to the account service.
- Use advertising SDKs (e.g., Google AdMob, Meta Audience Network) or display advertisements.
- Integrate analytics SDKs that profile your behaviour (e.g., Firebase Analytics, Mixpanel, Amplitude).
- Share any information with third parties for marketing or commercial purposes.
- Track your location.
- Access your contacts, camera, or microphone. The app accesses files you explicitly select for import, backup, or restore.
5. Network Requests
The App makes outbound network requests for trial and Pro access verification described above and for publicly available market prices:
- Mutual Fund NAV — queried from
api.mfapi.inusing only the publicly registered AMFI scheme code of a fund you have added. No account balances or unit counts are sent. - Stock Prices — queried from Yahoo Finance's public quote API using only the NSE/BSE ticker symbol you enter. No holding quantity or cost basis is sent.
All network communication uses HTTPS (TLS) exclusively. Plaintext HTTP traffic is blocked by the App's network security configuration.
These third-party services have their own privacy policies independent of MyPaisa.
6. SMS and Call Log Access
SMS-based money management is a core feature of MyPaisa. With your permission, the App reads SMS on your device, considers only transaction alerts, extracts fields such as amount, debit/credit type, merchant, date, and masked account/card suffix, and asks you to confirm before recording the transaction.
The App does not request Call Log access, send SMS messages, write SMS messages, or upload SMS content. OTP, login, security, personal, promotional, statement, reminder, and balance-only messages are ignored. SMS bodies are used only temporarily in memory for parsing; MyPaisa does not save or store SMS body text. Only parsed transaction fields are kept in the local encrypted database for review and duplicate prevention.
During update migration, any previously stored raw SMS review text or SMS previews are removed from the local encrypted database. Confirmed transaction records, account balances, budgets, and other user-entered finance data are preserved.
7. Security Measures
MyPaisa implements multiple layers of security appropriate for a financial application:
- AES-256 encrypted database (SQLCipher) with a hardware-backed key stored in the Android KeyStore.
- Optional PIN authentication with PBKDF2-HMAC-SHA256 hashing and failed-attempt delays.
- Biometric authentication via Android's BiometricPrompt API — raw biometric data is never accessible to the App.
- HTTPS-only networking enforced through Android's Network Security Configuration.
- ProGuard/R8 code obfuscation in release builds to resist reverse-engineering.
- App screenshot prevention in the Android task switcher.
- No automatic cloud backup of sensitive files; manual encrypted backups go to a destination you choose.
While we have taken reasonable precautions to protect your data, no security system is infallible. We recommend keeping your device PIN/password enabled and keeping the App up to date.
8. Children's Privacy
MyPaisa is not intended for use by children under the age of 18. We do not knowingly collect any information from minors. If you believe a minor has used this App, please contact us at the address below and we will provide guidance on removing locally stored data.
9. Access, Correction, Export and Deletion
Request deletion of verification data: email kapoorashish213@gmail.com with the subject "MyPaisa verification data deletion" and tell us whether your request concerns this phone's trial record or a legacy Google sign-in account. We will arrange identity/device verification before processing the request. Do not send financial documents, passwords or purchase tokens. We aim to respond within 30 days.
Verified requests can remove legacy sessions and saved purchase tokens. Limited hashed device/account trial and purchase ownership history may be retained while the access service operates to prevent repeat-trial and purchase abuse. Trial records are not automatically deleted after 30 days; the deadline remains recorded after expiry. Expired sign-in challenges and sessions are removed by the scheduled cleanup after their five-minute and 30-day expiry, respectively. Your phone's financial records are controlled locally and are not stored by us.
You can manage financial records directly in the App. Account service data is handled separately as described in the Automatic trial and Pro verification section. Available controls include:
- Right to access — all your data is visible within the App at all times.
- Right to correct — you can edit any record directly in the App.
- Deletion — delete records in the App or uninstall to remove local data. Contact us as described above to request deletion of access-service data. Limited hashed anti-abuse history remains as described above.
- Export — use password-encrypted backups and available PDF reports to export your records.
- Account deletion without the App — for legacy accounts, email the contact in Section 11 from the Google address used to sign in with the subject "MyPaisa account deletion". We will arrange identity verification before processing the request. Do not send financial statements, passwords, or purchase tokens by email.
If you have any questions about exercising these rights, please contact us using the details in Section 11.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the "Effective Date" at the top of this page and release an updated version of the App. Your continued use of the App after an update constitutes acceptance of the revised policy. Material changes will be highlighted in the App's release notes on Google Play.
11. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or the handling of your data, please reach out:
Developer: Ashish Kapoor
Email: kapoorashish213@gmail.com
App: MyPaisa — Personal Finance Manager
Country: India
We aim to respond to all privacy-related enquiries within 30 days.
© 2026 MyPaisa. All rights reserved.
This policy was last reviewed on October 4, 2026.