Hisab Privacy Policy
Effective date: 7 October 2026
This policy explains how Hisab handles information when you record transactions, view your ledger, and share an export. Hisab is a personal ledger app. You can use its local ledger features without creating an account.
Information you enter
Hisab stores the transaction information you provide, including amounts, credit or debit type, dates, and remarks, together with an entry identifier generated by the app. Remarks may contain personal information if you choose to include it.
This information is used to save and display your entries, calculate balances and totals, search and filter your ledger, and create exports you request. Chat-style transaction entry is processed on your device using local rules; it is not sent to an AI service.
Hisab does not request access to your contacts, location, microphone, camera, or bank accounts to provide these features.
Local storage
Ledger entries are stored in the app’s local storage on your device. Hisab does not operate a developer-hosted server to receive or store your ledger. Local ledger use does not automatically upload transactions to the developer.
Your device or operating system may include app data in backups, depending on your settings. Such backups are handled by the relevant device or backup provider.
Sharing your ledger
When you choose Share ledger, Hisab creates a CSV file containing all saved entries, including entry identifiers, dates, credit or debit type, amounts, and remarks. This includes entries outside any active search or filter.
The file is prepared in temporary app storage and passed to your device’s share menu. You choose the receiving app and recipient. On supported web builds, the file may be downloaded if native sharing is unavailable.
Sharing sends information to the destination you select. Receiving apps, recipients, and storage services handle that copy according to their own practices. Deleting an entry from Hisab does not remove previously shared or downloaded copies. Temporary export files may remain in the app’s cache until removed by the app or operating system; shared copies remain wherever you save or send them.
Google Sheets integration
The Google Sheets option is currently hidden from the app’s drawer. Entering an email address alone does not authorize Google access or upload entries.
Where a Google Sheets connection has been explicitly enabled and authorized, Hisab uses Google sign-in to connect the selected account and create an app-managed sheet. It saves the connected email address, sheet identifier, and last successful sync time locally. Google’s sign-in SDK manages authorization; Hisab does not ask for your Google password or store access tokens in its ledger preferences.
For an authorized connection, entry identifiers, dates, credit or debit type, amounts, and remarks are sent directly to Google Sheets over HTTPS. Sync occurs when you connect, when the app opens, after ledger additions or deletions, and when you request a sync. The connected sheet is a one-way copy of the local ledger. No Google Sheets upload occurs without an authorized connection.
Disconnecting stops future syncing and keeps your local ledger and the Google sheet. You can manage or delete the sheet in Google Drive and revoke access through your Google Account. Clearing local app data removes the stored connection information but does not delete the sheet or revoke the account’s Google authorization.
Google’s handling of account and sheet data is described in the Google Privacy Policy.
Advertising and analytics
Hisab does not include advertising, behavioral analytics, or an analytics tracking SDK. Hisab does not sell your ledger information or use it for targeted advertising.
Operating systems, app stores, and third-party services you choose to use may process information under their own privacy policies.
Retention and deletion
Local entries remain on your device until you delete them or remove the app’s local data. You can delete individual entries from the ledger. Where your operating system provides a clear-app-data option, it can remove the app’s stored ledger and connection metadata. Removing the app ordinarily removes its local data, although backups or restored data may remain with your backup provider.
Deleting an entry will also update an authorized connected Google sheet when the next sync succeeds. If syncing fails or is disconnected, the remote copy remains until it is updated or deleted separately. Deletion does not erase previously shared CSV files, copies held by recipients, or copies retained by backup and third-party providers.
Security
Hisab relies on the device’s app storage protections for locally saved data. It does not add a separate app password or encrypt ledger entries with an app-managed encryption key. Google Sheets requests, where enabled and authorized, use HTTPS.
You can protect access to your ledger by securing your device and controlling access to backups and exported files. No storage or transmission method can guarantee absolute security.
Changes to this policy
This policy may be updated as Hisab’s features or data handling change. The effective date above will be updated when the policy changes.
Contact
For privacy questions, contact the developer of Hisab:
Privacy contact email: [Add developer support email before publishing]