SmartHisab Privacy Policy


Last Updated: October 19, 2026

SmartHisab is developed and operated by App Code Byte. This Privacy Policy explains how SmartHisab accesses, collects, uses, processes, stores, protects, and shares information when you use the SmartHisab application.

SmartHisab provides expense management, sales tracking, receipt scanning, voice-based entry, bill splitting, financial reports, and other money-management features.

By using SmartHisab and enabling optional features such as Automatic Expense Tracking or Voice-Based Entry, you acknowledge the practices described in this Privacy Policy.

1. Information We Collect

Depending on the features you use, SmartHisab may process the following categories of information.

1.1 Account Information

- Name
- Email address
- User account information
- Authentication information required to provide the service

1.2 Financial and Expense Information

SmartHisab may process information that you voluntarily enter, generate, or manage through the application, including:

- Expenses and income
- Transaction amounts
- Expense categories
- Dates and times
- Notes and descriptions
- Merchant or business names
- Payment methods
- Sales information
- Financial reports
- Budget and expense-related information
- Bill-splitting details and shared expense calculations

1.3 Receipt and Bill Information

When you use the OCR receipt or bill scanning feature, SmartHisab may process information extracted from images, such as:

- Merchant or business name
- Transaction amount
- Date
- Purchased items
- Tax information
- Other bill or invoice details

Information extracted from receipts and bills is used to help create or update expense or sales records.

1.4 Voice Input and Recognized Text

When you use the voice-based expense and sales entry feature, SmartHisab may process spoken input, recognized text, and relevant financial information to identify and organize expense or sales details.

The information processed may include:

- Spoken descriptions of expenses or sales
- Transcribed text
- Amounts and transaction descriptions
- Merchant or business names
- Categories and other relevant financial details

The information processed depends on the feature you use and how the voice-processing functionality operates.

2. Microphone Permission and Voice-Based Entry

SmartHisab offers an optional voice-based entry feature that allows users to add expenses and sales using their voice.

The feature supports English, Hindi, Hinglish, and Gujarati.

2.1 Why Microphone Permission Is Required

SmartHisab requests microphone permission to capture voice input when you choose to use voice-based entry.

Microphone access enables users to speak transaction details instead of entering them manually.

The permission is used to support voice-based functionality and is not intended to provide unrelated recording functionality.

2.2 How Voice Input Is Used

Voice input may be processed to:

- Identify expense and sales information.
- Convert spoken input into text or usable information.
- Extract transaction amounts and descriptions.
- Identify relevant categories and business details.
- Organize information into structured financial records.
- Reduce manual data entry.

The information generated from voice input is intended to help users create expense or sales records more conveniently.

2.3 Gemini AI Processing

SmartHisab uses Google's Gemini AI service to help interpret user-provided input and generate structured expense or sales information.

Depending on the implementation, information transmitted to Gemini may include recognized text, transaction descriptions, amounts, and other information necessary to process the user's request.

If audio recordings are transmitted as part of a particular voice-processing workflow, those recordings may also be processed to provide the requested functionality.

The information sent to Gemini depends on the actual processing method used by the application.

Information transmitted to Google is subject to the applicable Google service terms, privacy policies, and data-processing arrangements.

2.4 Voice Data Use

SmartHisab uses voice-related information to provide the voice-based features requested by the user.

SmartHisab does not intentionally use microphone access to record conversations unrelated to the voice-based feature.

Voice input is not intended to be used for advertising, marketing unrelated products, or tracking users across other applications.

2.5 Microphone Permission and User Control

Voice-based entry is optional.

Users may grant or deny microphone permission through Android's permission system. Users can also manage or revoke microphone permission through their device settings.

Users who do not wish to use voice-based entry can continue adding expenses and sales manually.

2.6 Voice Data Retention

Voice recordings, recognized text, and related information are handled according to the processing method and the services involved.

SmartHisab's handling of this information depends on whether it is temporarily processed, transmitted to an AI service, stored by the application, or retained by a third-party service under its applicable terms.

SmartHisab aims to process only the information necessary to provide the requested functionality.

3. SMS and Automatic Expense Tracking

SmartHisab may provide an optional Automatic Expense Tracking feature that helps users identify eligible financial transactions from SMS messages received on their Android device.

This feature is optional and is used only after the user grants the required permission and provides any applicable consent.

3.1 What SMS Information May Be Processed?

When Automatic Expense Tracking is enabled, SmartHisab may process SMS information relevant to identifying financial transactions, including:

- Transaction amount
- Transaction date and time
- Debit or credit status
- Merchant or recipient name
- Bank or financial institution information contained in the transaction message
- UPI transaction or reference number, where available
- Payment method, where identifiable
- Limited account information, such as masked account or card details, where included in the transaction message

3.2 Why Do We Use SMS Information?

SMS information is used to provide automatic expense-management functionality, including:

- Detecting eligible financial transactions
- Identifying potential expenses or income
- Extracting transaction details
- Categorizing transactions
- Reducing manual expense entry
- Displaying detected transactions for user review
- Creating or updating expense records

3.3 What We Do Not Use SMS Data For

SmartHisab does not use SMS data for:

- Advertising or personalized advertising
- Selling user information
- Marketing unrelated products or services
- Contact discovery
- Building social profiles
- Tracking users across other applications
- Sharing personal or unrelated SMS history with advertisers

SMS information is processed for the disclosed SmartHisab expense-management functionality.

4. SMS Processing and Privacy

SMS and financial information may contain sensitive personal information. SmartHisab is designed to minimize the amount of SMS information processed for Automatic Expense Tracking.

Where technically possible, transaction detection and parsing may be performed locally on the user's device.

SmartHisab does not intentionally collect or upload unrelated personal SMS conversations for automatic expense tracking.

If transaction information needs to be synchronized with the user's SmartHisab account or cloud services, information necessary to provide the requested functionality may be transmitted.

Information transmitted over networks is protected using appropriate security measures, including encrypted communication such as HTTPS where applicable.

5. User Control and Consent

Automatic Expense Tracking is an optional feature.

Before SmartHisab accesses SMS information required for this feature, users should be informed about:

- Why SMS access is required
- What information may be processed
- How the information will be used
- How the user can control the feature

The user must grant the required Android permission and provide applicable consent before SmartHisab accesses SMS information for this feature.

Users may disable Automatic Expense Tracking through the available application settings. When the feature is disabled, SmartHisab will stop accessing SMS for automatic expense detection, subject to Android platform requirements and any processing already initiated.

6. Detected Transactions

A transaction detected from an SMS may initially be treated as a potential transaction.

SmartHisab may use transaction detection and validation rules to reduce incorrect expense entries.

Depending on the user's settings, detected transactions may be:

- Shown for review before being added
- Added after user confirmation
- Automatically added when the user has explicitly enabled automatic tracking and the transaction meets the application's detection criteria

Users can review, edit, categorize, or remove expense records created through the automatic tracking feature.

SmartHisab does not guarantee that every automatically detected transaction will be identified or categorized correctly. Users should review their financial records for accuracy.

7. SMS Data Retention

SmartHisab does not intentionally retain unrelated personal SMS messages for the purpose of providing expense tracking.

When transaction information is extracted from an SMS, information necessary to provide the SmartHisab feature may be retained according to the user's account, synchronization, and application settings.

Users may request deletion of their SmartHisab account and associated data through the available account-deletion mechanism or by contacting us.

Some information may be retained where required by law or where retention is otherwise permitted for legitimate purposes, such as preventing fraud or resolving disputes.

8. How We Use Information

Depending on the features you use, SmartHisab may process information to:

- Create and manage expense records
- Record income and sales
- Calculate balances and financial summaries
- Split bills and calculate shared expenses
- Scan receipts, bills, and invoices
- Provide voice-based expense and sales entry
- Interpret user input using AI-powered functionality
- Detect eligible transactions through optional SMS-based tracking
- Generate financial reports and analytics
- Provide PDF, CSV, or Excel exports where available
- Synchronize information across supported account services
- Authenticate users and maintain account functionality
- Send relevant service notifications
- Improve application reliability and performance
- Identify and resolve technical issues
- Protect the application and its users against misuse

SmartHisab processes information for purposes relevant to providing and maintaining its functionality.

9. Information Sharing

SmartHisab does not sell personal or sensitive user information.

We do not share SMS content or personal SMS history with advertisers or marketing companies for advertising purposes.

SmartHisab may transmit or disclose information in the following circumstances:

9.1 Service Providers

SmartHisab may use trusted service providers to operate application features, including cloud hosting, authentication, database services, analytics, crash reporting, and other infrastructure services.

These providers may process information as necessary to provide their services, subject to applicable terms and data-processing arrangements.

9.2 Gemini AI

When users use AI-powered voice or financial-entry features, relevant input may be transmitted to Google's Gemini AI service for processing.

The information transmitted depends on the feature and its implementation.

Users should avoid submitting information that is not necessary for the requested functionality.

9.3 Legal Requirements

Information may be disclosed when required by applicable law, a valid legal process, or a lawful governmental request.

9.4 Protection and Security

Information may be processed or disclosed where reasonably necessary to investigate fraud, prevent abuse, protect application security, or address legitimate legal claims, subject to applicable law.

10. Third-Party Services

SmartHisab may use third-party services to provide application functionality, such as:

- Firebase Authentication
- Firebase Cloud Firestore
- Firebase Cloud Messaging
- Firebase Analytics, where enabled
- Crash reporting and application-performance services
- Google Gemini AI
- Cloud hosting and infrastructure services required to operate SmartHisab

These services may process information according to their respective privacy policies, service terms, and applicable data-processing arrangements.

For more information, users can review the relevant service providers' privacy documentation:

- Google Privacy Policy: https://policies.google.com/privacy
- Firebase Privacy and Security: https://firebase.google.com/support/privacy

SmartHisab does not intentionally authorize third-party services to use SMS data for advertising or purposes unrelated to the disclosed functionality.

11. OCR and Images

When you use SmartHisab's OCR scanning functionality, you may provide images of receipts, bills, invoices, or other financial documents.

Information extracted from these images may include merchant names, transaction amounts, dates, purchased items, taxes, and other financial details.

This information may be used to create expense or sales records.

Depending on the implementation, images or extracted information may be processed locally or transmitted to services required to provide the feature.

Users should avoid uploading documents containing information that is not necessary for the intended SmartHisab functionality.

12. Data Storage and Synchronization

SmartHisab may store or synchronize information using local device storage and cloud services, depending on the feature and the user's account settings.

Information stored or synchronized may include account information, expense records, income, sales, categories, reports, and other data required to provide the application's functionality.

Where cloud synchronization is enabled, relevant information may be transmitted to the services used by SmartHisab.

Appropriate security measures are used to protect information during transmission and storage, as supported by the relevant systems.

13. Data Security

SmartHisab takes reasonable technical and organizational measures to protect user information against unauthorized access, alteration, disclosure, or destruction.

These measures may include:

- Encrypted network communication
- Authentication mechanisms
- Access controls
- Secure cloud infrastructure
- Restricted access to sensitive information
- Local processing where appropriate
- Security measures provided by third-party infrastructure services

However, no electronic storage or transmission system can be guaranteed to be completely secure.

Users should protect their devices and account credentials and avoid sharing confidential information unnecessarily.

14. Data Retention

SmartHisab retains information for as long as reasonably necessary to provide the requested functionality, maintain user accounts, comply with applicable legal obligations, resolve disputes, and protect the service.

Retention periods may differ depending on the type of information, the feature used, and the service involved.

Voice recordings, recognized text, SMS-derived transaction information, receipts, and other financial records may be handled differently depending on how each feature is implemented.

Information that is no longer required may be deleted or otherwise handled in accordance with applicable retention practices and legal requirements.

15. Data Deletion and Account Deletion

Users may request deletion of their SmartHisab account and associated personal information.

If available, users can initiate account deletion through the account-deletion option provided within SmartHisab. Users may also contact us using the email address provided below.

Upon receiving a valid deletion request, SmartHisab will delete applicable personal information associated with the account, subject to information that must be retained or may otherwise be retained under applicable law.

Users should understand that deleting the application from their device may not automatically delete information previously synchronized with cloud services.

Where applicable, users should use the account-deletion process to request deletion of associated account data.

16. Children's Privacy

SmartHisab is not intended to knowingly collect personal information from children in violation of applicable laws.

If you believe a child has provided personal information to SmartHisab without appropriate authorization, please contact us so that we can investigate and take appropriate action.

17. User Responsibilities

Users are responsible for ensuring that information entered into SmartHisab is accurate and that they have the right to provide any information submitted through the application.

Users should avoid submitting confidential information that is not necessary for the intended functionality.

Voice-based entry, AI-generated financial details, OCR extraction, and automatic transaction detection may produce inaccurate results. Users should review the resulting records before relying on them for financial decisions.

18. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in SmartHisab's features, services, legal requirements, or privacy practices.

When significant changes are made, we may provide appropriate notice through the application or other available communication channels.

The updated Privacy Policy will include a revised "Last Updated" date.

Continued use of SmartHisab after an updated policy becomes effective is subject to the applicable policy and legal requirements.

19. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or the handling of your information, please contact us:

Developer: App Code Byte
Application: SmartHisab – Expense Tracker
Contact Email: kirtikumarsx@gmail.com

SmartHisab – Expense Tracker
Developed by App Code Byte

0 Comments