Notification Rules

Privacy Policy

Notification Rules is designed to work primarily on your device. This page explains what data the app processes, what is stored locally, when Android or Google Play may be involved, and what control you have.

Last updatedApril 21, 2026
DeveloperJH Apps Studio
Core modelLocal-first processing
Ads / analyticsNone in the app code
Backend requiredNo

Developer information

Google Play developer name: JH Apps Studio

Organisation: JH-tuonti

Contact person: Jari Heikkilä

Address: Valssikuja 1A 11, 40520 Jyväskylä, Finland

Email: jari@jh-tuonti.net

Phone: +358407063410

1. What this app does

Notification Rules lets you create rules that react to Android notifications from apps you choose. Depending on the rule, the app can dismiss a notification, wait before dismissing it, try an available notification action button, or create a log entry.

Dismiss notifications Delay actions Notification logs Local test notifications Import / export rules One-time premium unlock

2. Information the app processes

  • Notification data: app package name, notification title, text, subtext, notification key, clearable status, and available action button labels when Android exposes them.
  • Rules you create: app selection, match words, exclusions, delays, cooldowns, time windows, weekday filters, action settings, rule names, and optional notes.
  • Logs: timestamps, target app, matched rule, action attempted, success or failure, reason messages, and may include notification title or text snippets.
  • App settings: onboarding completion, selected app language, cached premium state, and the last premium refresh timestamp.
  • Installed app list: the app queries locally available launchable apps so you can choose which app a rule should apply to.
  • User-selected files: if you export or import rules, the app reads or writes only the JSON file that you explicitly choose.

3. How the app uses this information

  • To match incoming notifications against your rules.
  • To run the action you selected for a matching notification.
  • To show readable logs and troubleshooting details inside the app.
  • To let you choose a target app from apps installed on your device.
  • To remember your language choice, onboarding state, and cached premium entitlement.
  • To export and import your rules when you ask the app to do so.

4. Permissions and special access

  • Notification access: required for the app to read Android notifications, match your rules, dismiss notifications, and inspect or trigger notification action buttons when Android makes those actions available.
  • Post notifications: optional on newer Android versions and used for the app's own local test notifications.
  • Google Play Billing: used only for the one-time premium purchase flow.

The app does not request a broad package visibility permission. It queries launchable apps locally using standard Android APIs so you can choose a target app.

5. Where data is stored

Notification Rules stores its main app data locally on your device. That includes your rules, logs, and app settings. The app's core functionality does not require your own account and does not require the developer to operate a backend server for rule processing.

Because notification logs may include notification titles or text snippets from other apps, your locally stored app data can contain information that you may consider personal or sensitive.

6. Sharing and third parties

The app does not use advertising SDKs or in-app analytics SDKs in the current codebase, and it does not send your rules or notification logs to a developer-operated backend.

  • Google Play Billing: if you buy premium, Google Play handles payment processing. The app uses Google Play purchase status and product information needed to unlock premium. The app does not receive your full payment card details.
  • Android / device backup and transfer: if backup or device transfer is enabled on your device, Android or your device provider may include app data in those features. That processing is handled by the operating system or platform provider, not by the app developer.

7. Backups and device transfer

Depending on your Android version, device settings, and platform account settings, app data stored locally on your device may be included in device backup or transfer features. That can include rule data and logs stored in the app database.

8. Your choices and controls

  • You can use the app without enabling notification access, but automation features will not work.
  • You can delete rules, disable rules, clear logs, and uninstall the app at any time.
  • You can export your rules to a JSON file that you control.
  • You can choose whether to grant the optional notification posting permission for test notifications.
  • You can change the app language inside the app settings.

9. Data retention

Rules, logs, and settings remain on your device until you change them, clear them, uninstall the app, or your device removes them. Imported or exported rule files are retained according to the location you choose and how you manage those files.

10. Changes to this policy

This Privacy Policy may be updated if the app changes materially, including if future versions add online services, support features, or new data handling. The latest published version should always include the effective date shown at the top of this page.

11. Contact

For privacy questions, support requests, or requests related to your data, contact JH Apps Studio at jari@jh-tuonti.net.