Privacy Policy for MySpends

MySpends ("we", "our", or "us") is dedicated to uncompromising personal privacy. This Privacy Policy outlines our strict data handling practices, permissions usage, and adherence to Google Play developer policies for the MySpends mobile application.

1. Architecture & Privacy Principles

• Local Storage Only: All personal financial information, expenses, and parsed messages are stored in an encrypted, sandboxed SQLite Room database on your physical device.
• Zero Cloud Databases: We have zero external servers receiving or storing your transaction history, account balances, or personal profiles.
• No User Account or Registration: You do not need to sign up, provide phone numbers, submit email addresses, or log into any server to use MySpends.
• Zero Third-Party Trackers & Ads: The app does not bundle advertising SDKs (e.g., Google AdMob), tracking frameworks, or third-party behavioral analytics.

2. Permissions Requested & Data Usage

A. SMS Permissions (READ_SMS & RECEIVE_SMS)

Strict Purpose: Automatically parsing incoming and historical bank transaction alerts to record debits, credits, account balances, and UPI payment references without tedious manual data entry.

• Financial-Only Scope: Our parsing engine parses messages solely from recognized financial institutions (e.g., HDFC, ICICI, SBI, Axis, Kotak, Union Bank, and UPI services).
• Non-Financial Messages Ignored: Personal chats, two-factor OTPs, verification codes, and unrelated SMS notifications are strictly ignored and never recorded.
• 100% On-Device Processing: SMS reading and regex categorization occur completely within the app's local sandbox. SMS content is never transmitted across the network.

B. Biometric Authentication (USE_BIOMETRIC)

Purpose: Optional App Lock feature (Fingerprint / Face Unlock) to secure your expense data when launching or resuming the application.

• Authentication is handled strictly by the native Android OS BiometricPrompt hardware interface.
• MySpends receives only a cryptographic success/failure callback. The app never accesses, stores, or processes raw biometric samples or templates.

C. Push Notifications & Local Reminders (POST_NOTIFICATIONS & RECEIVE_BOOT_COMPLETED)

Purpose: Delivering local spending alerts, monthly budget limits warnings, bill & recurring payment reminders, and daily financial wisdom notifications.

• All notifications are scheduled and dispatched locally on your device using Android's native AlarmManager and WorkManager frameworks.
• When your phone reboots, RECEIVE_BOOT_COMPLETED is utilized solely to restore your scheduled local reminder alarms locally on device.
• No remote push notification servers (e.g., FCM tracking servers) or cloud messaging tokens are utilized.
• Notification alert chimes are played from a bundled local audio asset directly on your phone.

D. Internet Access (INTERNET & ACCESS_NETWORK_STATE)

Transparency Disclosure: MySpends requests network access strictly for two lightweight client-side features:

1. Foreign Currency Exchange Rates: Querying public, non-authenticated exchange rates so you can view international expenses converted to local currency.
2. Dynamic Bank Icons: Loading public brand logos and category icons from public CDNs.

Zero Data Transmission: At no point is your financial data, parsed SMS text, account balance, user identity, or device telemetry transmitted over the network.

E. Approximate Location (ACCESS_COARSE_LOCATION - Optional)

Purpose: Optionally tagging the geographical location where a manual transaction was logged to populate the interactive spending heatmap. Location data remains entirely on-device and is never shared.

F. On-Device Financial Health Score & Spending Insights

100% Local Intelligence: All financial health score metrics (budget discipline, savings rate, recurring obligation tracking, and spend volatility) and deep spending insights (anomalies, category shifts, and month-over-month comparisons) are computed entirely on-device using deterministic, client-side algorithms.

No Third-Party AI Services: Your financial records, transaction histories, and category distributions are never sent to external AI APIs, cloud LLMs, or remote analytics platforms.

3. Data Retention, Export & Deletion Rights

• User Data Ownership: You retain complete ownership of all data entered or parsed by MySpends.
• Data Export: You can export your full transaction log to a standard .csv spreadsheet anytime directly from the Analytics screen.
• Right to Complete Erasure: You can delete any transaction individually, clear bank-specific data from Settings, or permanently erase all stored records by uninstalling the application or clearing App Data via Android Settings.

4. Children's Privacy

MySpends is a personal finance tool directed to individuals aged 18 and older. We do not knowingly collect or solicit any information from children under 18 years of age.

5. Google Play Policy Compliance

MySpends complies fully with the Google Play Developer Distribution Agreement, Google Play User Data Policy, and Specific SMS & Call Log Permissions Policies by ensuring that SMS permissions are utilized strictly for the core financial expense tracking functionality and handled 100% on-device.

6. Policy Updates

We may periodically update this policy to reflect new capabilities. Any revisions will be published here with an updated "Effective Date".

7. Contact Information

If you have any questions, feedback, or privacy concerns, please contact the developer team directly:

• Support Email: teamorbit2000@gmail.com