Effective date: October 30, 2026
NotificationRuleZ: Advanced Notification Manager ("NotificationRuleZ," "we," "us," or "our") is provided by Mobirova. This policy describes the data practices reported for the live product. Subscription billing is not currently integrated, and this policy will be updated if its data practices or integrations change.
Notification access and on-device processing
NotificationRuleZ can read notification details only after you enable Android Notification Access. The app uses details made available by Android, such as the source app, notification text, and sender details where provided, to evaluate your rules and perform the actions you choose.
Notification details used for rule matching and notification history are processed on your device and are not uploaded to the NotificationRuleZ API. Android and the source app control which notification details are available. Some notifications cannot be dismissed, and the app does not override Do Not Disturb or silence the original app sound.
Information stored on your device
- Rules and profiles: Your rules, profiles, schedules, cooldowns, and action choices are stored locally until you remove them or clear the app data.
- Selected sender details: Names or phone numbers you choose to use in rules are stored locally for matching.
- Sounds and notification history: Sound selections and matched notification history are stored locally. History previews are off by default. Free history is retained for 24 hours; planned Pro history is retained for up to 30 days.
- Exported rules: If you export rules, the file is saved to the destination you select and is handled according to that destination’s settings.
Advertising
The Google Mobile Ads SDK may collect and share your IP address (which may indicate approximate location), ad or app interactions, diagnostic information, and device identifiers for advertising, measurement, analytics, and fraud prevention. Google and relevant advertising partners may process this data under their own policies. Consent is handled through Google’s User Messaging Platform (UMP) where required.
See Google’s Android advertising data disclosure for more information.
- Google Mobile Ads data disclosure: Information about data handled by the Google Mobile Ads SDK. Google AdMob Android data disclosure
Contact and account/data deletion requests
If you submit the in-app contact form, the selected topic, reply email, message, pending status, and submission time are sent to and stored in the NotificationRuleZ API database. Mobirova reviews requests and responds using the email address you provide. A deletion request is recorded for manual handling; the API does not delete an account automatically. Do not include passwords or Google Play purchase tokens in your message.
In-app contact requests are automatically deleted after 365 days. If you use the Mobirova website contact form instead, that form stores submissions separately under the Mobirova website privacy practices.
Planned subscription verification
Subscriptions are not currently integrated. If the planned Pro subscription is enabled, the app will send a Google Play purchase token to the NotificationRuleZ API for verification with Google Play. The API is planned to store an anonymous account ID, a hash of the API session token, a hash of the purchase token, product ID, subscription status, expiry, and verification timestamps. The raw purchase token will not be stored in the database. Google Play processes payment; the app does not receive card details.
The API does not yet automatically delete subscription or account records and has no account-deletion endpoint. Subscription records would remain until manually removed. We intend to establish and implement retention and deletion controls before enabling this integration for a public release, and will update this notice to describe the actual service before then.
Sharing and retention
Notification details, rules, profiles, selected sender details, sound selections, and local history are not uploaded to the NotificationRuleZ API. Advertising data may be shared with Google and relevant advertising partners as described above. If subscription verification is enabled, the purchase token will be sent to Google Play and the described verification data will be processed by the API.
On-device rules and profiles remain until you remove them or clear the app data. History follows the free or Pro period described above. Google and advertising partners determine their own retention periods for advertising data; Mobirova does not set those periods.
Your choices and security
You control whether to grant Android Notification Access and can revoke it in Android settings. You can remove rules and profiles in the app or clear the app’s data in Android settings. You can choose whether to export a rules file and where it is saved. Consent choices for advertising are presented through UMP where required.
The app is designed to process notification details locally for matching. No method of storage or transmission can be guaranteed completely secure.
Changes and contact
We will update this policy when material data practices or integrations change.
For privacy questions, contact Mobirova at admin@mobirova.com.