UPIAwaaz ("UPIAwaaz", "we", "our", or "us") respects your privacy and is committed to protecting the information processed through the UPIAwaaz Android application.
UPIAwaaz is a mobile application designed to help merchants use their Android phone as a pocket UPI SoundBox. The application detects supported payment notifications, processes relevant payment information on the device, stores transaction information locally, and announces eligible payment notifications using text-to-speech.
This Privacy Policy explains what information UPIAwaaz accesses, how it is processed, where it is stored, and how you can control the application's access.
1. INFORMATION UPIAwaaz ACCESSES
1.1 Notification Information
UPIAwaaz requires Android Notification Access to perform its core payment-alert functionality.
When Notification Access is enabled, UPIAwaaz can receive notification events generated by applications on your Android device.
UPIAwaaz uses a package whitelist and payment-processing rules to identify notifications from supported payment and banking applications.
Depending on the notification generated by the supported application, information processed by UPIAwaaz may include:
- Notification title
- Notification text
- Notification body or expanded notification text
- Application/package name
- Notification time
- Payment amount
- Payment status
- Sender or payer name, when provided
- Transaction/reference information, when provided
- Payment provider or bank name, when available
UPIAwaaz uses this information to determine whether a notification represents a genuine incoming payment and, where appropriate, announce the payment through the phone's speaker.
1.2 Transaction Information
When a supported payment notification is identified as a transaction, UPIAwaaz may store information such as:
- Transaction amount
- Sender name, when available
- Payment source/provider
- Transaction timestamp
- Transaction/reference information, where available
- Relevant notification text used by the application for transaction processing
This information is used for:
- Voice payment announcements
- Transaction history
- Duplicate transaction detection
- Transaction summaries
- Local analytics
2. HOW NOTIFICATION DATA IS PROCESSED
UPIAwaaz processes supported payment notifications through an on-device processing pipeline.
The general process is:
The application uses validation and confidence checks to reduce the risk of incorrectly announcing non-payment notifications, such as balance information, account summaries, scheduled credits, or other banking messages.
UPIAwaaz is designed to prefer not announcing an uncertain notification rather than incorrectly announcing it as a received payment.
3. LOCAL PROCESSING
UPIAwaaz is designed as a local/on-device application.
Based on the current application architecture:
- Payment notification information is processed on the Android device.
- Transaction information is stored in the application's private local database.
- Analytics are calculated locally.
- Text-to-speech announcements are generated locally through the device's available TTS functionality.
- UPIAwaaz does not currently operate a cloud database for transaction information.
- UPIAwaaz does not currently transmit notification or transaction information to a UPIAwaaz server.
The current release architecture does not include an Internet-based transaction-processing backend.
4. INFORMATION WE DO NOT REQUEST
UPIAwaaz does not require access to:
- UPI PIN
- ATM PIN
- Debit or credit card PIN
- Bank password
- UPI password
- Banking login credentials
- OTP for making payments
- Your bank account login
UPIAwaaz does not initiate or authorize UPI payments.
The application is intended to detect relevant payment notifications generated by supported applications on your device.
5. SMS ACCESS
UPIAwaaz does not request or use SMS permissions.
The application does not require:
READ_SMSRECEIVE_SMS
SMS messages are not used as a payment-detection source by the current version of UPIAwaaz.
6. NOTIFICATION ACCESS PERMISSION
Notification Access is a special Android permission and is required for UPIAwaaz's core functionality.
Before enabling Notification Access, UPIAwaaz explains why the permission is needed.
You can enable or disable Notification Access through Android's system settings.
If Notification Access is disabled, UPIAwaaz will not be able to detect supported payment notifications and therefore cannot provide automatic payment voice announcements.
UPIAwaaz does not use Notification Access to make payments or control your banking applications.
7. LOCAL STORAGE
UPIAwaaz stores application and transaction information locally on your Android device.
The application uses local storage mechanisms, including a private SQLite database, for transaction history and application functionality.
Transaction records may include information such as:
- Amount
- Sender
- Payment source
- Timestamp
- Relevant notification text
The application also stores certain local settings, such as:
- Shop name
- Voice preferences
- Language preference
- Announcement preferences
- Sound preferences
The application does not currently synchronize this information with a cloud account.
8. DATA RETENTION AND DELETION
Transaction information is retained locally until it is deleted by the user through available application functionality or the application and its private storage are removed from the device.
UPIAwaaz does not currently maintain a cloud copy of your local transaction history.
Because transaction information is stored locally, uninstalling the application generally removes the application's private local data according to Android's application storage behavior.
Users should review their device's Android backup and restore settings separately. UPIAwaaz's current application configuration disables application cloud backup through:
android:allowBackup="false"
9. DATA SHARING
UPIAwaaz does not sell, rent, or otherwise commercially share your notification or transaction information.
The current application architecture does not transmit payment notification information or transaction history to external servers.
UPIAwaaz does not currently integrate advertising networks, third-party analytics platforms, or cloud transaction databases into the application.
If this architecture changes in the future, this Privacy Policy will be updated where required.
10. THIRD-PARTY APPLICATIONS
UPIAwaaz may process notifications generated by supported third-party UPI, payment, wallet, and banking applications when you have enabled Notification Access.
Those applications are independent services and have their own privacy policies and terms.
UPIAwaaz does not control how those applications generate, display, or otherwise process their notifications.
UPIAwaaz only processes information made available through Android's notification system for the purposes described in this Privacy Policy.
11. TEXT-TO-SPEECH AND AUDIO
UPIAwaaz uses the Android device's text-to-speech functionality to announce eligible payment notifications.
For example, when a genuine supported payment notification is identified, the application may announce an amount such as:
"₹500 received."
The purpose of the audio announcement is to allow merchants to hear payment notifications without continuously checking their phone screen.
12. DEVICE PERMISSIONS
The current release architecture uses Android system functionality required for its operation.
The primary special access required is:
Notification Access
Used to receive relevant notification events from supported applications and detect payment notifications.
The current release manifest also contains the normal Android:
WAKE_LOCK
This is used to help the device CPU remain active when required for processing and completing payment voice announcements.
UPIAwaaz does not request SMS permissions, battery-optimization exemption permissions, or foreground-service permissions in the current release architecture.
13. SECURITY
UPIAwaaz is designed to minimize unnecessary transmission of sensitive transaction information.
The current architecture:
- Processes payment notification information locally.
- Stores transaction information in the application's private local storage.
- Does not transmit transaction information to a UPIAwaaz server.
- Does not require banking credentials.
- Disables application cloud backup through the application's backup configuration.
However, no software or electronic storage system can be guaranteed to be completely secure. Users should also protect their Android device using appropriate device security measures such as a screen lock and current operating-system security updates.
14. CHILDREN'S PRIVACY
UPIAwaaz is intended primarily for merchants and business users.
The application is not directed toward children.
We do not knowingly collect personal information from children through the UPIAwaaz service where such collection is prohibited by applicable law.
15. YOUR CONTROLS
You can control UPIAwaaz's access through your Android device settings.
You may:
- Disable Notification Access.
- Stop using the application.
- Delete transaction records using available application controls.
- Uninstall UPIAwaaz.
Disabling Notification Access will prevent the application from detecting supported payment notifications.
16. CHANGES TO THIS PRIVACY POLICY
We may update this Privacy Policy when the application's functionality, data practices, legal requirements, or services change.
When we update this Privacy Policy, we will revise the Last Updated date at the top of this page.
We encourage users to review this Privacy Policy periodically.
17. CONTACT US
If you have questions about this Privacy Policy, the information processed by UPIAwaaz, or your privacy rights, please contact us.
UPIAwaaz
Developer: UPIAwaaz
Email: himanta820@gmail.com
UPIAwaaz — Aapka Pocket SoundBox