Overview
RitualMoney ("we", "our", "the app") is an educational financial resilience tool for Indian households. It helps you understand how many days your household could manage if regular income stopped — using the income, expenses, EMIs, and savings you enter.
This Privacy Policy applies to the RitualMoney Android application on Google Play. By using the app, you agree to the practices described here.
If we introduce features that require new data collection, we will update this policy and tell you clearly before anything changes.
What we do not collect on our servers
We operate no backend that stores your financial data. We do not collect, request, or process on our servers:
- Your name, email, phone number, or identity (unless you email us voluntarily)
- Your income, salary, savings, EMI amounts, or any financial figures you enter in the app
- Device location (GPS or network-based)
- Advertising IDs for profiling or ad targeting
- Analytics events tied to your financial numbers
- Crash reports containing your financial data sent to third-party services
What stays on your device
RitualMoney stores the following locally on your device (Android local storage). This data does not leave your device unless you explicitly export a backup file or use the system share sheet.
| Data | Purpose | Sent anywhere? |
|---|---|---|
| Income, expenses, EMIs, savings, runway | Calculate runway days and plans | Never (unless you share) |
| Goals, wedding/trip planners, bills, transactions | Plan tab, Records hub, trackers | Never (unless you share) |
| Wealth holdings (EPF, gold, property, etc.) | Wealth tab totals | Never |
| Streak, bricks, journal entries | Habit tracking | Never |
| Salary day & notification preferences | Local reminders | Never |
| Encrypted backup file | Optional export you save where you choose | Only where you save it |
| Payment-alert parse queue | Suggest expenses from notifications you enabled | Never — cleared after you confirm or dismiss |
Android permissions we use
RitualMoney requests only the permissions needed for features you use. You can deny optional permissions and still use the core app.
Core (local reminders)
- POST_NOTIFICATIONS — Optional local reminders (daily brick, salary day, payday playbook). Scheduled on your device. No server.
- RECEIVE_BOOT_COMPLETED — Reschedule local notifications after device restart. No data transmitted.
- USE_BIOMETRIC / USE_FINGERPRINT — Optional app lock. Biometric data stays in Android OS; we never see it.
- VIBRATE — Haptic feedback on actions.
Optional capture (you must turn on)
- Notification listener (BIND_NOTIFICATION_LISTENER) — Off until you enable it in Android Settings → Apps → RitualMoney → Notification access. When enabled, the app reads text from payment-related notifications (e.g. UPI, bank alerts) on your device to suggest an expense amount and merchant. Suggestions sit in an inbox until you confirm or dismiss. Parsed text is not uploaded to our servers. You can disable this anytime in system settings.
- CAMERA — Only when you open receipt capture. Photos are processed on-device for OCR; not uploaded by RitualMoney.
- READ_MEDIA_IMAGES — Only when you choose screenshot import. Image stays on-device for parsing.
What we do not use
- READ_SMS / RECEIVE_SMS — We do not automatically read your SMS inbox. You may manually paste SMS text into the app if you choose; that text is parsed locally and not retained after you save.
- READ_CONTACTS, LOCATION, READ_CALL_LOG
- Background upload of financial data to our servers
SMS paste (manual only)
If you use "Paste SMS", you copy text yourself. We parse amount and merchant locally to pre-fill a transaction. The pasted text is not uploaded and is not stored after you save or cancel.
Notifications
All RitualMoney reminders are local notifications scheduled on your device. They do not connect to our servers and do not track whether you open them. Disable anytime in Settings → Apps → RitualMoney → Notifications.
Sharing features
When you tap Share (runway card, plan, etc.), Android's share sheet sends content you choose to apps you pick (e.g. WhatsApp). We do not receive a copy.
Encrypted backup
Profile → Backup lets you export an encrypted file to storage you control (Drive, Files, etc.). The file is encrypted with a password you set. RitualMoney does not host or receive this file.
Third-party services
RitualMoney does not integrate third-party analytics, advertising, or crash-reporting SDKs that collect your financial data. The app is built with React Native and Expo using local storage, local notifications, and on-device parsing libraries.
Children's privacy
RitualMoney is for adults managing household finances. It is not directed at children under 13. We do not knowingly collect personal data from children.
Data security
Your data security depends on your device (screen lock, encryption). We recommend a device PIN/biometric lock and keeping Android updated. Optional app lock adds a second gate inside RitualMoney.
Your rights & deletion
Because we hold no server copy of your data:
- Uninstall the app — deletes all local data
- Profile → Wipe all data — resets the app without uninstalling
- Disable notification access — stops payment-alert parsing immediately
Google Play Data safety
| Question | Answer (current version) |
|---|---|
| Does the app collect or share required user data types with us? | No — financial data stays on device |
| Is data encrypted in transit to our servers? | N/A — we do not receive it |
| Can users request deletion? | Yes — uninstall or wipe in app |
| Optional notification access | Declared; user-enabled in system settings; on-device only |
Changes to this policy
We will update the "Last updated" date for material changes and notify in-app when possible. Continued use after changes means acceptance. If you disagree, uninstall the app.
Contact
RitualMoney
We aim to respond within 7 business days.