This Privacy Policy explains how PesaCount collects, uses, stores, and protects data. PesaCount is designed to be an offline-first tool. This means most transaction processing and storage happens locally on your device.

PesaCount is built to help users read and analyze payment SMS messages locally. The App is not a bank, mobile-money provider, accounting firm, tax advisor, lender, or financial advisor.

Pesa Count uses SMS permissions only for SMS-based money management. READ_SMS allows Pesa Count to scan existing payment SMS messages already stored on your device. RECEIVE_SMS allows Pesa Count to receive new incoming payment SMS messages in real time. This helps Pesa Count save parsed transaction SMS records locally, so income, expense, and report records remain available even if the original SMS is later deleted from the phone’s Messages app.

Pesa Count only extracts payment-related transaction details such as amount, date, time, transaction reference, sender, recipient, transaction type, till number, paybill number, account/reference text, fees, balance where present, and applicable transaction cost. Non-payment SMS messages are ignored and are not stored as transaction SMS records.

Pesa Count may improve parsing for supported payment, till, and merchant payment message formats where those formats appear in the SMS message. This is parsing support only. It does not create a separate till number mode, business-wallet mode, or agent-style payment mode unless that feature is present inside the installed App version.

Pesa Count may use locally stored transaction SMS records to provide Daily All Transactions, Daily From Hour to To Hour filtering, and Daily name search. These features run locally on the device and do not upload transaction history to secure server services.

Pesa Count may store the full original payment SMS/message content linked to a parsed transaction locally on the device so the user can view the full-message popup inside the App where that feature is available.

Pesa Count does not access call logs, does not send SMS messages, does not upload full SMS messages to our servers, and does not sell or share SMS data with third parties.

Pesa Count uses secure authentication services to identify app users. The App may create or use an app authentication account automatically, and users may also sign in or create an account using email and password where that account feature is available.

For access status, trial status, session sync, support, reporting, device identity, and app version checking, Pesa Count may send limited data to secure server services. This may include authentication user identifier or secure authentication token, install ID, hashed device fingerprint, device model, app version, installedVersionCode, session event type, access status, transaction reference where required for lawful records, and account email where used.

For update checks, Pesa Count may send the installed app version or installedVersionCode to secure server services. This is used to check whether a newer official app-store version is available.

The device fingerprint is generated from device/app identifiers and is hashed before being sent. It is used to recognize the app installation/device for access status, trial/access status, support, reporting, abuse prevention, and version/access checks. It is not used to read contacts, call logs, photos, location, microphone, camera, browsing history, or installed apps list.

Pesa Count does not send full SMS transaction history to secure server services.

Pesa Count stores parsed transaction records locally on your device. The App also stores local settings such as legal acceptance, SMS sync state, access status, App Lock status, active lock method, PIN/password hashes and salts, biometric setup confirmation, and saved account email where used.

For app versions that include full-message popup, local storage may include the full original payment SMS/message content linked to a parsed transaction so the user can view it inside the App. This full SMS/message content remains on the device and is not uploaded to secure server services as full SMS transaction history.

Daily All Transactions, Daily From Hour to To Hour filtering, and Daily name search use local storage only. These features do not require secure server transaction search and do not upload local transaction records to secure server services.

Pesa Count may allow users to protect the App using local App Lock features. In app versions with App Lock method selection, only one active unlock method can be selected at a time: fingerprint, PIN, or password.

PIN/password credentials are stored only as hashes and salts on the device. Pesa Count does not store plaintext PINs or plaintext passwords.

Biometric unlock uses the device-level biometric system. Pesa Count does not collect or store fingerprint images, face data, or biometric templates.

Fingerprint may be used locally for setup/reset where supported. PIN/password/fingerprint lock data is not sent to secure server services. App Lock data stays local. Pesa Count does not provide email recovery, cloud recovery, or server recovery for App Lock in this phase.

Pesa Count is local-first. Local app data is intended to remain on the device unless the user clears app data, uninstalls the App, or manually exports/shares information through a user-controlled action where such a feature exists.

Pesa Count does not provide a separate cloud backup or cloud recovery system for local SMS transaction records unless that feature is present inside the installed App version.

Pesa Count does not collect contacts, call logs, location, photos, videos, microphone recordings, camera data, biometric templates, browsing history, installed apps list, advertising ID, government ID documents, plain-text passwords, email content, or social media data.

Pesa Count does not send full SMS transaction history, full saved SMS popup content, PIN/password credentials, fingerprint data, biometric templates, or full App Lock credentials to secure server services.

Pesa Count does send limited authentication, device/install, access status, session, support, reporting, and app version check data to secure server services as described above.

Pesa Count does not upload local parsed transaction records to secure server services for transaction reporting.

PesaCount does not sell, rent, or share your SMS data or transaction records with third parties, including advertisers or analytics providers.

PesaCount may use service providers required to operate secure server services, secure authentication services, access control, support, reporting, and app version checks. These services are used only for the limited operational purposes described in this Policy.

Since transaction data is stored locally, you are responsible for securing your device with a screen lock and protecting access to your phone.

We use standard mobile security practices to protect local App data and secure server communication. No system is perfectly secure, and local records can be lost if the user clears app data, uninstalls the App, loses the device, or deletes required local data.

You can delete local PesaCount data by clearing the App’s data in device settings or by uninstalling the App.

Data stored on secure server services for access status, support, reporting, device identity, app version checking, or lawful business records may be retained where needed for service operation, fraud prevention, support, or legal compliance.