Privacy Policy for Ledger

Last Updated: July 19, 2026

This Privacy Policy applies to the Android application Ledger published on Google Play by MetroPhoenixIND.

This Privacy Policy describes how MetroPhoenixIND ("we," "us," or "our") collects, uses, discloses, and safeguards information in connection with your use of the Ledger mobile application (the "App"). By downloading, installing, or using Ledger, you agree to the practices described in this Privacy Policy. If you do not agree with these practices, please do not use the App.

1. Introduction

Ledger is a personal finance and expense tracking application developed and published by MetroPhoenixIND for the Android platform. Ledger's core functionality is to help users track income and expenses by:

• Automatically detecting and parsing financial transaction information from bank and financial institution SMS messages;
• Allowing users to manually create, edit, categorize, and organize transactions;
• Providing budgeting tools, spending analytics, summaries, and financial insights, including optional AI-powered features.

MetroPhoenixIND is committed to protecting the privacy of Ledger's users. This Privacy Policy explains what information the App collects, how that information is used and stored, who it may be shared with, and the choices and rights available to you.

2. Information We Collect

Ledger collects the following categories of information in order to provide its core features:

2.1 Account and Identity Information

When you sign in to Ledger using Google Sign-In, we collect, via Firebase Authentication:

• Your name (as provided by your Google account);
• Your email address;
• Your Google account profile photo (if available);
• A unique Firebase User ID, which is used internally to associate your data with your account.

This information is used solely to authenticate you, create and maintain your Ledger account, and ensure that your financial data is accessible only to you.

2.2 Financial Transaction Information

Ledger collects and stores financial transaction data that you create or that is derived from SMS parsing, including:

• Transaction amounts;
• Transaction dates and times;
• Merchant or payee names;
• Transaction descriptions and notes;
• Categories, tags, and labels assigned to transactions;
• Budgets, spending summaries, and financial insights generated from the above data.

This data is entered manually by you or extracted automatically from SMS messages as described in Section 3 below.

2.3 SMS-Derived Transaction Information

If you grant SMS permissions, Ledger reads incoming and existing SMS messages solely to identify messages sent by banks, card issuers, wallets, and other financial institutions, and to extract transaction details (amount, merchant, date, and transaction type) from those messages. See Section 3 ("SMS and Call Log Permissions") for a full explanation of this process.

2.4 Device Information and Diagnostics

To maintain and improve the App, we may collect:

• Device model, manufacturer, and operating system version;
• App version and build information;
• Crash logs, stack traces, and error diagnostics (via Firebase Crashlytics, if enabled);
• General usage and performance diagnostics (via Firebase Analytics, if enabled).

This information is technical in nature and is used to identify, diagnose, and fix bugs, and to understand aggregate app performance and stability. It is not used to identify you personally beyond what is necessary for crash attribution and debugging.

2.5 Information You Provide Directly

Any information you voluntarily provide, such as feedback, support requests, or communications sent to us via email, is also collected and retained as necessary to respond to you.

3. SMS and Call Log Permissions

Ledger requests the following Android runtime permissions:

• READ_SMS
• RECEIVE_SMS

Ledger does not request or use any Call Log permissions.

3.1 Why These Permissions Are Required

The core, distinguishing feature of Ledger is the automatic detection of financial transactions from SMS messages sent by banks, card networks, payment processors, and digital wallets. Most financial institutions notify customers of transactions via SMS. The READ_SMS and RECEIVE_SMS permissions allow Ledger to:

• Scan incoming SMS messages in real time to detect new transaction notifications;
• Scan existing SMS messages on your device (with your permission) to import historical transactions;
• Parse the amount, merchant, date, and transaction type from qualifying messages to automatically create transaction entries, without requiring manual data entry.

3.2 What Messages Are Processed

Ledger's on-device parsing logic evaluates SMS messages to identify those that originate from, or resemble notifications from, banks, credit card issuers, payment applications, and other financial institutions. Only messages that are identified as financial transaction notifications are processed and used to create transaction records. Messages that do not match transaction patterns (such as personal messages, OTP/verification codes used for login purposes, promotional messages, or messages unrelated to financial activity) are not extracted, stored, transmitted, or used by the App.

Non-financial SMS content is not uploaded to our servers and is not retained by Ledger beyond the local, on-device evaluation necessary to determine whether a message is transaction-related.

3.3 SMS Data Is Never Sold

We do not sell, rent, or trade SMS content or SMS-derived data to any third party for any purpose, including advertising or marketing.

3.4 SMS Permissions Are Optional

Granting SMS permissions is entirely optional. If you decline or later revoke the READ_SMS and RECEIVE_SMS permissions:

• Ledger will continue to function normally for all manual features;
• You may still manually create, edit, and manage transactions, budgets, and reports;
• Automatic detection of transactions from SMS messages will be disabled until permissions are re-granted.

You may revoke SMS permissions at any time through your device's Settings > Apps > Ledger > Permissions menu.

4. Artificial Intelligence Features (Anthropic Claude)

Ledger integrates the Anthropic Claude AI model to provide optional, user-initiated features, including:

• Transaction categorization suggestions;
• Spending summaries;
• Financial insights and analysis.

4.1 AI Features Are Optional and User-Initiated

AI features are never triggered automatically or in the background. AI processing occurs only when you explicitly choose to use an AI-powered feature within the App (for example, by tapping a button to request a spending summary or categorization suggestion).

4.2 What Information Is Sent to Claude

When you invoke an AI feature, Ledger securely transmits only the information necessary to fulfill your specific request to Anthropic's Claude API. This may include:

• Transaction descriptions;
• Merchant names;
• Transaction amounts;
• Transaction dates;
• Transaction categories;
• Relevant transaction history necessary to generate the requested summary or insight.

Data is transmitted over an encrypted connection. We do not send your full account credentials, raw SMS message content, or unrelated personal data to Anthropic.

4.3 How Anthropic Uses This Data

Data sent to Anthropic's Claude API is used solely to generate the response to your specific request. We do not use your data, and Anthropic does not use data submitted via its API, to train Anthropic's underlying AI models, except as otherwise described in Anthropic's own API terms and privacy policy, which govern Anthropic's handling of API data. We encourage you to review Anthropic's privacy policy for further detail on its data handling practices as a processor of API requests.

4.4 Disabling AI Features

Because AI features are optional, you may simply choose not to use them. Declining to use AI features does not affect the App's core manual and SMS-based transaction tracking functionality.

5. How We Use Your Information

We use the information described above to:

• Create, authenticate, and maintain your Ledger account;
• Provide, operate, and maintain the core functionality of the App, including automatic SMS-based transaction detection and manual transaction management;
• Generate budgets, spending summaries, analytics, and financial insights;
• Provide optional AI-powered features at your request;
• Diagnose, troubleshoot, and fix technical issues and crashes;
• Improve the performance, stability, and usability of the App;
• Respond to your support requests and communications;
• Comply with applicable legal obligations.

6. Third-Party Services

Ledger relies on the following third-party service providers to operate. Each provider processes data only as necessary to perform its function on our behalf and is bound by its own privacy and security commitments.

6.1 Firebase Authentication (Google)

Used to authenticate users via Google Sign-In and to securely manage user identity and session information. Firebase Authentication processes your name, email address, profile photo, and Firebase User ID.

6.2 Cloud Firestore (Google Firebase)

Used as the App's primary database to securely store your transaction data, budgets, categories, and account-related information. Firestore's access-control rules ensure that each user can only access their own data; MetroPhoenixIND does not permit one user's data to be accessed by another user through the App.

6.3 Firebase Crashlytics (if enabled)

Used to collect crash reports and diagnostic logs to help us identify and fix software defects. Crash reports may include device information, app state at the time of the crash, and stack traces.

6.4 Firebase Analytics (if enabled)

Used, where enabled, to collect aggregate, non-identifying usage statistics (such as feature engagement and app performance) to help us understand how the App is used and to improve it.

6.5 Anthropic Claude AI

Used to provide optional AI-powered features such as transaction categorization, spending summaries, and financial insights, as described in Section 4 above.

We do not control the independent privacy practices of these third-party service providers beyond the data-processing relationship described above. We encourage you to review the privacy policies of Google/Firebase and Anthropic for additional information.

7. Data Sharing and Disclosure

MetroPhoenixIND does not sell, rent, or trade your personal data or financial information to any third party.

We do not share your personal data or financial information with third parties for advertising or marketing purposes.

We disclose information only in the following limited circumstances:

• Service Providers: To the third-party service providers identified in Section 6 (Firebase Authentication, Cloud Firestore, Firebase Crashlytics, Firebase Analytics, and Anthropic Claude), solely as necessary to operate the App's features.
• Legal Requirements: If required to do so by law, regulation, legal process, or governmental request, or to protect the rights, property, or safety of MetroPhoenixIND, our users, or the public.
• Business Transfers: In connection with a merger, acquisition, reorganization, or sale of assets, in which case we will take reasonable steps to ensure your information continues to be protected consistent with this Privacy Policy.
• With Your Consent: In any other circumstance, only with your explicit consent.

8. Data Security

We take reasonable, industry-standard measures designed to protect your information from unauthorized access, alteration, disclosure, or destruction, including:

• Encryption of data in transit using industry-standard protocols (e.g., TLS/HTTPS) between the App and our third-party service providers;
• Use of Firebase's secure authentication and access-control mechanisms to restrict data access to authenticated users;
• Firestore security rules that ensure users can only read and write their own data.

While we strive to use commercially reasonable means to protect your information, no method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security. You use the App at your own risk with respect to any inherent security limitations of internet-based and mobile data transmission.

9. Data Retention

We retain your account and transaction information for as long as your Ledger account remains active, or as needed to provide you with the App's services. If you delete your account or request deletion of your data, we will delete or anonymize your personal information from our active systems within a reasonable period, except where retention is required to comply with legal obligations, resolve disputes, or enforce our agreements.

10. Your Rights and Choices

You have the following rights and choices regarding your information:

• Revoke SMS Permissions: You may disable READ_SMS and RECEIVE_SMS permissions at any time via your device's Settings menu. This will disable automatic SMS-based transaction detection but will not affect manually entered data.
• Delete Transactions: You may delete individual transactions, categories, or budgets directly within the App at any time.
• Delete Your Account: You may delete your Ledger account directly within the App, or by contacting us using the information in Section 13.
• Request Deletion of Cloud Data: You may request that we delete your data stored in Cloud Firestore by contacting us. We will process such requests within a reasonable time, subject to any applicable legal retention requirements.
• Stop Using AI Features: You may choose not to use any AI-powered feature at any time; doing so will not affect the App's other functionality.
• Access and Correction: You may access and correct your account and transaction information directly within the App.
• Contact Us: You may contact us at any time with questions, concerns, or requests regarding your data, using the contact information provided in Section 13.

11. Children's Privacy

Ledger is not intended for, or directed at, children under the age of 13, and we do not knowingly collect personal information from children under 13. If we become aware that we have inadvertently collected personal information from a child under 13, we will take steps to promptly delete such information. If you believe we may have collected information from a child under 13, please contact us using the information in Section 13.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, the App's functionality, or applicable legal requirements. When we make material changes, we will:

• Update the "Last Updated" date at the top of this Privacy Policy;
• Where appropriate, provide notice within the App or through other reasonable means (such as an in-app notification or update to this page) prior to the change taking effect.

We encourage you to review this Privacy Policy periodically. Your continued use of Ledger after any changes to this Privacy Policy constitutes your acceptance of the updated terms.

13. Contact Information

If you have any questions, concerns, or requests regarding this Privacy Policy or MetroPhoenixIND's data practices in connection with Ledger, please contact us at:

Developer: MetroPhoenixIND
Website: https://ledger.matrimpathak.com
Email: support@ledger.matrimpathak.com

This Privacy Policy applies specifically to the Android application Ledger, published on Google Play by MetroPhoenixIND, and governs the collection, use, and disclosure of information through that application.