Privacy Policy

Last updated: September 2026

Introduction

Hisab ("we", "our", or "the app") is an open-source group expense splitting application. This Privacy Policy explains how we collect, use, and protect your information when you use our app. We are committed to transparency and respecting your privacy.

App Permissions

The app may request the following permissions. All are optional and requested only when you use the related feature. • Camera — To scan receipts when you choose the scan flow while adding an expense (tap the camera button). We do not record or store video; images are used only for this scan flow and are processed on your device or via optional AI services you configure. • Photos / Photo library — To let you choose expense images from your gallery when adding an expense (tap the gallery option). We only access images you explicitly select. • Notifications — To send you push notifications when group members add or edit expenses (Online mode only). You can disable this at any time in Settings > Privacy > Push Notifications. If you deny or disable notifications, the app works fully; you simply won't receive push alerts. • Notification access (Android, Transaction Scanner) — Only if you enable Transaction Scanner in Settings. The app may read notification text from apps you allow to detect bank or payment transactions, process them on your device, keep a local history of added and ignored messages, and show drafts for your approval before they become expenses. After setup, an empty app list captures nothing. You can turn the scanner off or revoke Notification access in Android system settings at any time. Draft and history text stays on your device and is not synced. Optional cloud AI, if you turn it on, sends that text to the AI provider you configured.

Data We Collect

In Offline mode, all data stays on your device. No data is sent to any server. In Online mode, we collect: - Email address (for authentication) - Display name and avatar (optional, set by you) - Group names, participant names, and expense data you create - Payment destination details only when you choose to save them in your cloud account (bank transfer, wallet, or HTTPS payment link) - Anonymous usage telemetry (if enabled in Settings)

How Data Is Stored

Offline mode: Data is stored locally on your device using SQLite. Nothing leaves your device. Online mode: Data is stored on cloud servers powered by Supabase (PostgreSQL). Connections use HTTPS/TLS, and the cloud provider's database and backup encryption controls protect data at rest. Hisab does not provide application-layer end-to-end encryption, so the service can process synced data. Payment destinations are not included in generic user exports; cloud sync restores them. Do not store card numbers, PINs, passwords, or banking login credentials.

How We Use Your Data

Your data is used solely to provide app functionality: - Syncing expenses across your devices - Managing group memberships and invites - Calculating balances and settlements - Showing payment instructions that you explicitly share with current members of selected groups; Hisab does not initiate, verify, or reconcile external payments We do not sell, rent, or trade your personal data to any third party. We do not use your data for advertising or profiling.

Third-Party Services

The app may use the following third-party services: - Supabase: Cloud database and authentication (when using Online mode) - Google OAuth / GitHub OAuth: Sign-in authentication (optional) - Hisab cloud AI: Optional receipt and notification extraction when you enable External AI and are signed in. Images or notification text are sent to Hisab; Hisab may call a third-party model on the server. You do not supply an API key. - Gemini Nano (Android AI Core): Optional on-device receipt AI when you enable it and your device supports it - PostHog (EU): Opt-in product analytics, crash reports, and masked session recordings when telemetry is enabled These services have their own privacy policies. We encourage you to review them.

Data Sharing

We do not share your data with third parties except as required to operate the services listed above. Group data is shared only with members of the same group. A payment destination is visible to current members only when its owner explicitly shares it with that group; inactive or unshared destinations are not shown. Unlinked participants and former members cannot access destination rows. We may disclose data if required by law.

Data Security

We use HTTPS/TLS in transit, strict row-level security for cloud access, provider-managed encryption at rest, and encrypted disaster-recovery backups. Payment destinations are limited to bank/wallet instructions or HTTPS links; we do not ask for card numbers, PINs, passwords, or banking login credentials. Online data is not application-layer end-to-end encrypted. No security measure is absolute.

Your Rights

You have the right to: - Export all your data at any time (Settings > Data & Backup > Export) - Delete local data from this device (Settings > Advanced > Delete local data) - Delete your data from the server (Settings > Advanced > Delete cloud data) - Deactivate or permanently delete your payment destinations in Profile > Payment destinations - Request full account deletion (account deletion page, or open an issue on our GitHub repository or contact the developer via the app's About section) - Disable telemetry at any time (Settings > Privacy) - Use the app entirely offline with no data collection

Data Retention

Your live data is retained until you delete it. Deactivating or deleting a payment destination removes it from new settlements; old settlement records retain only a safe snapshot (destination type, label, provider, and masked identifier). Full account/data deletion removes live destinations, shares, and payment destination IDs/snapshots from historical transfers while retaining the settlement amount, participants, and date where the group remains. Disaster-recovery backups may retain residual copies for the provider's configured retention period; those copies are restricted to recovery operations and expire according to that schedule.

Children's Privacy

This app is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal data, please contact us so we can delete it.

Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be reflected in app updates. We encourage you to review this policy periodically. Continued use of the app after changes constitutes acceptance of the updated policy.

Contact Us

If you have questions or concerns about this Privacy Policy, please open an issue on our GitHub repository or contact the developer through the app's About section.