← Back to PayGhanti PayGhanti · Android App

Privacy Policy

Effective Date: April 29, 2026  ·  Last Updated: October 20, 2026

Trei ("we", "us", "the developer") built PayGhanti: UPI Sound Box App (formerly AlertBox) as an Android application that reads payment notifications aloud using text-to-speech, designed for accessibility and for shopkeepers. This privacy policy explains how the app handles your data.

This policy describes PayGhanti version 2026.09.19 (build 105), the version on Google Play on 15 October 2026, and the update currently in testing. The data the app sends, described below, is the same in both.

The short version: PayGhanti uses the Android Notification Listener service to detect payment notifications from your banking, UPI, and default messaging apps, then reads the amount aloud on your device. Sender details, message text and your saved payment list are never sent to us. To enforce the Free daily voice allowance across reinstalls, PayGhanti sends our quota service hashed quota identifiers, count metadata and the amount of the payment it is about to announce – payments under ₹100 do not spend your allowance, so the amount is checked against that floor and discarded rather than kept. The app also reports once a day that it announced a payment. PayGhanti has no sign-in and no account, so we never receive your name, email address or an account identifier. Separately, Android's own backup feature can copy PayGhanti's saved app data to your Google account – that copy is in your account, not ours. If you choose to answer a question the app asks you, that answer is sent to us. The app also uses ad and subscription SDKs (see below), which collect device-level data under their own policies.

Data Collection by the App Itself

PayGhanti does not transmit notification content, sender, message, or transaction history to any server we operate. Here is what the app does send us. Apart from the amount of a payment being announced on the Free tier, described in the first item below, nothing on this list carries a payer or a message. Answers you choose to send are covered in the next section, and the ad and subscription SDKs under Third-Party Services below.

  • Hashed quota identifiers, a count, and the payment's amount. For each payment the app announces on the Free tier, PayGhanti sends our quota service two one-way SHA-256 hashes - one for your device, and one for the event, worked out from the device hash, the transaction reference and its time. Neither can be turned back into a payment. Travelling with them are the amount of that payment in paise and the number of extra announcements you have earned that day from watching an ad. The amount is sent for one reason: a payment under ₹100 does not spend your daily allowance, so the quota service compares the amount with that floor and discards it. It is never written to our records, and no sender, message or transaction reference goes with it. Up to ten are sent a day, along with a daily count so the allowance resets correctly.
  • No sign-in, and no account. PayGhanti has no sign-in screen and ships without any sign-in SDK, so your name, email address and any account identifier never reach us. Your daily allowance is tied to the one-way device hash above and to nothing else.
  • A once-a-day signal that the app is working. On any day PayGhanti announces a payment, it sends our analytics endpoint the app's name and a device identifier, so we can tell working installs from dead ones. It carries no payment details.
  • Error reports. If the app hits an internal error, it sends the error type, message, stack trace, app version and package name to our error-reporting endpoint and to Firebase Crashlytics. These are not meant to carry payment details, and sensitive text is scrubbed when they arrive.
  • How long we keep it. Quota records and event records are deleted automatically after 3 days. The once-a-day working signal is not covered by that 3-day deletion and is kept for longer, because it answers questions about how many installs stay in use over months.

No account is required. Notification and SMS parsing is performed entirely on-device, and your transaction history is kept on your phone rather than on our servers.

Answers You Choose to Send

PayGhanti may show a short question on the home screen, for example to ask what you expected the app to do. Answering is optional, and you can close the question without answering. Information is sent only when you tap an answer or press Send.

  • What is sent: the answer you picked, any text you typed, the app version, and your phone's make and model.
  • WhatsApp number: if a question offers a field for it and you fill it in, your WhatsApp number is sent too. It is optional and is used only to reply to you about that answer.
  • What is never sent with it: payment notifications, amounts, senders, or transaction history.
  • How we use it: to understand problems and improve PayGhanti. We do not sell it or use it for advertising.
  • Our server's own record: as with every request it receives, our server records the internet (IP) address the answer arrived from, to keep out abuse. We do not use it to work out where you are.
  • Deleting it: email us at the address under Contact and we will delete the answers and number you sent.

Data Stored on Your Device

  • Parsed transaction history - amount, sender, and timestamp extracted from matching payment notifications.
  • Per-sender rules and preferences - TTS voice, muted senders, volume overrides.
  • App settings - theme, language, notification preferences.

All of this is removed from your phone when you uninstall the app. If Android's backup is switched on, a copy may remain in your Google account - see Android's Own Backup below.

Android's Own Backup

Android has a backup and device-transfer feature of its own, switched on by default on most phones. While it is on, Android can copy an app's saved data from your phone to your Google account and put it back on a new phone. For PayGhanti that includes the payment list the app keeps on your phone.

That copy goes to your own Google account, not to us. We never see it, and it is covered by Google's privacy policy rather than this one. You can switch the backup off, or delete what is already backed up, from your phone's settings under Settings → Google → Backup.

Permissions and Why We Need Them

Notification Access Disclosure (BIND_NOTIFICATION_LISTENER_SERVICE) PayGhanti reads notifications from banking apps, UPI apps (GPay, PhonePe, Paytm, BHIM, etc.), and your default messaging app solely to detect and announce payment-related transactions. Notification text is filtered against a list of known payment-sender headers (HDFC, SBI, ICICI, etc.) and parsed locally on the device. Notifications that do not match payment senders, OTP / verification messages, and personal messages are ignored and never processed. PayGhanti does not send notification content to our servers, and does not share it with advertisers or anyone else. You can revoke Notification Access at any time from Android system settings (Settings → Notifications → Special access → Notification access); the app will continue to work for other features but will no longer read payment alerts.
  • BIND_NOTIFICATION_LISTENER_SERVICE - Read notifications from banking, UPI, and default messaging apps to detect payment alerts. See disclosure above.
  • RECEIVE_SMS - Direct incoming bank-SMS capture when Android or the device maker redacts payment notification text. Matching messages are parsed locally; PayGhanti does not read stored SMS or transmit SMS content.
  • POST_NOTIFICATIONS - Show in-app status notifications.
  • INTERNET / ACCESS_NETWORK_STATE - Serve ads, verify subscription status, synchronize the daily voice quota, report once a day that the app is working, and send error reports.
  • VIBRATE - Optional haptic feedback on alert.

PayGhanti declares RECEIVE_SMS only for the direct incoming bank-SMS fallback described above. It does not request, declare, or use READ_SMS, SEND_SMS, call-log, location, contacts, microphone, or camera permissions.

Third-Party Services

PayGhanti integrates the following third-party SDKs, each subject to their own privacy policies:

Children's Privacy

PayGhanti is not directed at children under 13. We do not knowingly collect data from children.

Data Security

Your payment list and settings sit in PayGhanti's private storage, protected by Android's app sandbox. PayGhanti does not send notification content, senders or message text to our servers; the one payment detail that does leave the phone is the amount the quota service checks against the ₹100 floor, described above. Everything the app sends travels over HTTPS. Android's own backup is the one route by which saved app data can leave the phone - see Android's Own Backup above.

Changes to This Policy

We may update this policy when new features are added. Any changes will be posted here with an updated "Last Updated" date.

Contact

Trei
Email: contact@trei.dev
Phone: +91 85500 77767
Website: trei.dev  ·  Contact form