ExpenseWard Privacy Policy

Last Updated: September 2026

1. Introduction

ExpenseWard is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our mobile application on the Google Play Store. By using ExpenseWard, you agree to the collection and use of information in accordance with this policy.

2. Information Collection and Use

A. Personal Information (Account Data)

When you sign in using Google Sign-In, we collect:

Purpose: To manage your premium subscription status and identify your account across devices. This data is stored securely in Google's Firebase Firestore.

B. Financial Transaction Data (Local Storage)

Your financial data stays on your device & is encrypted.
  • Nature of Data: All income, expenses, categories, notes, and budget entries you input.
  • Encryption: Your local database is encrypted using SQLCipher. The encryption keys are stored securely in the Android Keystore system.
  • Our Access: We do NOT have access to your financial transactions.
  • Server Upload: Your financial data is never uploaded to our servers.
  • AI Assistant exception: If you choose to use the AI assistant ("Wally"), whatever you type or say to it is sent to our AI provider to interpret your request — see Section F below. This is separate from, and much narrower than, the database described here: it's only what you actively tell the assistant, never the database itself, and only if you use that feature.
  • Notification-detected transactions: If you enable Notification Access (Section G below), transactions suggested from your notifications are parsed and stored the same way — entirely on your device, in the same encrypted local database.
  • Backups: If you enable Google Drive backup, data is stored directly in your own private Google Drive. ExpenseWard only accesses the specific backup files it creates.

This local-first design ensures your financial data remains private and under your full control.

C. Payments & Subscriptions

We offer premium features via in-app purchases. All payment transactions are processed securely by the Google Play Store. We do not collect, process, or store your credit card numbers or banking information.

D. Media and Files

E. Sensitive Personal Information

F. AI Assistant ("Wally") & Voice Input

Talking to Wally sends your message — and only your message — to our AI provider.
  • What's sent: The text of what you type or say to the assistant, plus the names of your categories and accounts (e.g. "Groceries", "Cash") so it can understand your request. This is sent, via our own Firebase servers, to DeepSeek, the third-party AI service that powers the assistant.
  • What's NOT sent: Your transaction history, account balances, and budget totals are never sent to DeepSeek, and never touch our servers for this feature either. The app calculates all of that on your device and only asks the AI to identify what you're asking for — the AI never sees your actual financial data, only your words.
  • Voice input: If you use the microphone, your speech is converted to text on your device whenever possible. Only if your device can't do this on its own does the recording go to your device's speech recognition service (typically Google's) for transcription — and you're shown a clear explanation and asked to agree before this happens, every time it's needed. Voice input is entirely optional; you can always type instead.
  • Nothing is stored: We do not save your conversations with the assistant, and we do not save any voice recordings or transcripts, on our servers — not even temporarily beyond what it takes to answer your request.
  • Every action needs your OK: The assistant never adds, edits, or deletes a transaction, changes a budget, or exports data on its own. It always shows you exactly what it's about to do first and waits for you to confirm — nothing happens silently.

DeepSeek processes this data under its own privacy policy, linked in Section 3 below. We don't control and can't speak for their internal data practices beyond what they publish there, so we encourage you to review it if you'd like the details.

G. Notification Access (Auto-Detect Transactions)

Notification Access is optional and used only to auto-detect transactions from your notifications, entirely on your device.
  • What it is: If you turn on Notification Access in Settings, ExpenseWard uses Android's Notification Listener API to read the notifications posted on your device, so it can automatically suggest income and expense entries from things like bank, UPI, and payment app alerts — without you having to type them in manually.
  • Scope: Because of how this Android permission works, once granted it technically lets the app read notifications from any app, not just banking apps — Android does not allow us to restrict this to a chosen list of apps. We only use it to look for transaction-like messages; unrelated notifications (chats, social media, news, etc.) are not parsed into anything and are not of interest to us.
  • Where processing happens: All reading and parsing of notification text happens locally on your device. Nothing is uploaded to our servers, and nothing is sent to DeepSeek or any other third party as part of this feature.
  • What's kept: Notification text is briefly held on-device in a temporary queue only until the app next opens and processes it. Anything that looks like a transaction becomes a suggested entry in the app, which you review and confirm — nothing is added automatically or silently. Anything that isn't recognized as a transaction is simply discarded and is not stored anywhere.
  • Your control: Notification Access is off by default, only enabled if you turn it on via the Android system settings screen from within the app, and can be revoked at any time from your device's Settings with no effect on any other part of the app.

3. Third-Party Services

We use verified third-party services to operate and improve the app. These services collect identifiers as described in their respective policies:

4. GDPR Compliance (For EEA Users)

5. CCPA / CPRA Compliance (For California Residents)

6. Data Retention & Deletion

7. Children's Privacy

Our app is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13.

8. Changes to This Policy

We may update this Privacy Policy periodically. Any updates will be posted on this page with a revised "Last Updated" date.

9. Contact Us

If you have any questions about this Privacy Policy or your data, please contact us:

📧 help.expenseward@gmail.com