The short version
Mera Kharcha does not read SMS on your phone. It stores your expense records in your account and uses service providers for features such as sign-in, AI, and notifications. Optional imports arrive from Mera SMS after your consent there. You control sharing, imports, and deletion.
Who this policy covers
Mera Kharcha and Mera SMS are provided by Codexcollab. For privacy questions, account requests, or concerns, email merakharcha.support@gmail.com. Include the app name and the Google email associated with your account where relevant. Do not send passwords, verification codes, or full card details.
This policy applies to Mera Kharcha and this website. Mera SMS has a separate policy.
Your account and expense records
Mera Kharcha does not request SMS access, contacts access, or bank login credentials. It stores the information you enter or import: expenses and income, amounts, dates, categories, merchants, notes, payment methods, bank/card labels, reminders, and shared-group records.
Google sign-in uses Firebase Authentication and shares your account identity, name, and email with the service. Guest use creates an anonymous account. Guest sessions send a hashed device identifier derived from Android’s app-scoped ID to limit repeated guest-account creation. It allows up to 2 guest accounts per phone. New accounts, including guests, start with a 7-day Premium trial; linking Google later keeps the same account and trial. Preferences such as currency, timezone, and language support formatting and account features.
Your records are stored on our backend and cached on your phone. Signing in lets you access your account across devices. This is not a device-only expense store.
Optional payments from Mera SMS
Mera SMS can send eligible payment messages after its own sign-in and consent flow. Both apps must use the same Google account. Our server receives the sender, message body, timestamp, message key, and connected-phone details. It extracts payment information and stores recognized payments with their original messages. Mera Kharcha shows these records without reading your phone’s inbox.
The full payment text may contain balances, merchant information, or partial account identifiers included by the sender. Review is on by default. You can choose which imports to keep, disable review for future imports, or pause/remove a phone under Profile → Auto-track payments.
AI questions, summaries, and voice
When you use AI, our backend processes your prompt and relevant account context using Google Gemini through Vertex AI. Relevant expense records, aggregates, merchant names, notes, categories, payment labels, reminders, and shared information you are allowed to access may be used to answer. Do not put passwords, verification codes, or unnecessary sensitive information into prompts or notes.
This is not a guarantee of anonymized processing: you may include personal information in your prompt or records. Access to family records depends on membership and feature permissions. The expense-query interface does not include the original SMS body as a transaction field.
Saved AI conversations are retained for up to 30 days, with up to 50 answers available in the app. AI expense entries remain as expenses until deleted. Token usage and purchases are recorded to manage allowances.
Voice uses your phone’s speech-recognition service, which may process audio under that provider’s policy. Mera Kharcha receives the resulting text and sends it for the action you choose. It does not directly record audio or request microphone permission.
Family and split sharing
Joining a family shares expense records with members who have the required access. Split participants can see the split’s shared payments and balances. Join only groups whose members you trust, and only enter information you intend to share. Leaving or removing a member changes future access; it cannot retract copies someone already made.
We use OneSignal to deliver relevant notifications, such as family and split updates. Device push identifiers and delivery information are processed for that purpose. See OneSignal’s privacy policy.
Purchases, ads, and diagnostics
Google Play Billing: handles subscription and token-pack purchases. Our backend verifies purchase tokens and stores entitlement and purchase information. We do not receive your payment-card details from Google Play.
Google AdMob: shows ads to free users and optional rewarded ads. Google may process advertising identifiers, IP address, device information, and ad interactions. We do not attach expense records, message content, contacts, or AI questions to ad requests for targeting. Manage consent through Ad privacy choices where available.
Meta App Events (Facebook SDK): used to measure ad campaigns, such as installs and sign-ups. It starts only when configured. It reads the advertising ID and logs automatic app events only after you allow ads in the consent form. Events we send describe actions (for example, a sign-up or a purchase with Play’s price) and never include expense amounts, notes, AI questions or message content. See Meta’s privacy policy.
Firebase: Authentication handles sign-in; Analytics measures app usage; Crashlytics processes crash diagnostics; Remote Config manages app availability and settings. These services may process installation identifiers, device/app information, usage events, and diagnostic data. We do not intentionally include raw expense or message content in analytics or crash events.
Google’s services have their own privacy information: Google Privacy Policy, Firebase privacy and security, and Google’s advertising and partner services.
This website
This site uses Firebase Analytics to understand page visits and interactions such as app-download clicks, FAQs, and support links. It may use browser storage and identifiers under Google’s policies. The account-deletion page uses Firebase Authentication to identify the account you choose. Website analytics is not an expense-tracking feature and does not read your account’s expense records.
Retention and your controls
Active expense and account records remain until you delete them or the account. When “Keep deleted items for 30 days” is enabled, eligible items stay in Recently deleted for up to 30 days and can be restored or permanently deleted earlier. With the setting off, new deletions are permanent; items already in Recently deleted keep their existing expiry.
Discarding an imported payment during review clears its message text, sender, merchant, and account fields immediately. A duplicate-prevention record, including its key and amount, remains. For added SMS expenses, original messages remain while an expense is active or restorable; scheduled cleanup clears the text after permanent expense deletion. Minimal import records remain until account deletion.
Pausing sync, removing a phone, signing out, or uninstalling does not delete already stored expenses. You can edit records, leave shared groups, change consent options where available, and contact us about your data.
You can delete the shared account in Mera Kharcha under Profile → Delete account, or use our account-deletion page. Account deletion removes the account’s expense records, imported payment messages, device registrations, lists, reminders, chat history, and other account data from our application database, and deletes its authentication account. Shared groups with other members may continue under another owner. This does not erase messages in your phone’s SMS store or files you exported.
Deleting an account or uninstalling an app does not cancel a Google Play subscription. Cancel it separately in Google Play. Service providers may retain their own billing, security, or diagnostic records according to their policies and legal requirements.
Bill reminders stay in your account without Premium, but their alerts only ring while you have Premium or a trial.
Security and processing locations
We use HTTPS for app-server communication and authenticated account access. Hosting, database, authentication, AI, diagnostics, advertising and ad-measurement (Google, Meta), and notification providers process information to provide their services. Processing may take place outside your country. We do not sell expense records or payment-message content. Information may be disclosed where required by a valid legal obligation. No storage or transmission method is completely risk-free.
Launch notification emails
If you use “Notify me” on this website, we store your email address, the phone type you choose (Android or iPhone), the button you used, and the time. We use it only to email you about the new Mera Kharcha and Mera SMS apps and Mera Kharcha on iPhone. It is stored in Firebase Realtime Database and is not visible to other visitors. To limit abuse, we count sign-ups per hour using a one-way hash of your IP address; the IP address itself is not stored.
We delete the list and these counts after the launch emails are sent. Email us to be removed sooner.
Children, updates, and contact
Mera Kharcha is not directed at children under 13. Contact us if you believe a child has provided personal information so we can investigate. We update this page and its date when practices change and provide additional notices when appropriate.
Mera Kharcha and Mera SMS are provided by Codexcollab. For privacy questions, account requests, or concerns, email merakharcha.support@gmail.com. Include the app name and the Google email associated with your account where relevant. Do not send passwords, verification codes, or full card details.
