← Back to PayGhanti PayGhanti · Android App

Privacy Policy

Effective Date: April 29, 2026  ·  Last Updated: October 3, 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.

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 locally on your device. Notification content, parsed amounts, sender details, messages, and transaction history never leave your device. To enforce the Free daily voice allowance across reinstalls, PayGhanti sends hashed quota identifiers and count metadata. 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, amount, sender, message, or transaction history to any server we operate. It sends one-way hashed event/device identifiers, an optional signed-in Firebase user identifier, and daily quota count metadata solely to prevent duplicate counting and reset abuse.

  • No account is required; users who sign in use their Firebase identifier for cross-device quota continuity.
  • Notification parsing is performed entirely on-device.
  • Transaction history (if enabled) is stored locally only.
  • Daily quota records expire automatically; identifier links are retained only to preserve quota continuity across app-data clearing and sign-in changes.

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.
  • 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 local data is deleted when you uninstall the app.

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. The app does not transmit, upload, or share notification content with any server. 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, and synchronize privacy-safe daily voice quota metadata.
  • 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

All local data is protected by Android's app sandboxing. No notification content is transmitted off-device by PayGhanti.

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