Privacy Policy

Notification Manager · Effective November 10, 2026

Notification Manager (“the app”) is made by WP Methods (“we”, “us”). This policy explains what the app does with your information. If something here is unclear, write to contact@wpmethods.com.

The short version

1. What stays on your phone

To work, the app asks for Android’s notification access. With it, the app can see notifications from your other apps: the app name, the title, the text, and for chat apps the sender names and messages shown in the notification. The app uses this only to:

All of this happens on your device. The history is stored in the app’s private storage for the period you choose in Settings (1, 7 or 30 days, up to 1,000 notifications). You can clear it at any time with the trash icon in the History tab, or by uninstalling the app. Notification content is never sent to our servers or to any third party.

Your rules, settings and the list of apps you picked are also stored only on your phone.

Installed apps

The app looks at the apps that appear on your home screen (name and icon) so you can pick them when making a rule. This list stays on your phone, except that the names of those apps are sent along with Assistant messages (see section 2) so the Assistant can choose the right app for a rule.

Optional: automatic taps (Accessibility)

If you turn on Automatic taps, the app uses Android’s Accessibility service. It only looks at the apps you added to the list, only looks for the button text you entered (for example “Skip”), and presses that button. It does not collect, store or send what it sees. You can turn it off any time in Android’s Accessibility settings.

Alarms and your watch

If you use the Wear OS companion app, the app name, title and text of a notification that triggers an Alarm rule are sent from your phone to your watch using Google’s Wearable Data Layer. This stays between your own two devices.

Auto-reply

If you set up an Auto-reply rule, the message you wrote is sent through the messaging app’s own reply button, as if you had typed it. That message is then handled by that app under its own privacy policy.

2. What we collect when you use the Assistant

The Assistant is part of the paid lifetime unlock. When you send it a message, the app sends the following to our server (hosted on Convex):

We keep your chat messages (and the rule changes the Assistant suggested), along with the device ID and a count of messages sent each day, so conversations can continue and so we can limit how many messages each phone sends per day. We use this information only to run the Assistant and to prevent abuse. Please don’t put sensitive personal information in chat messages.

To answer, our server passes your message and the information above to Google’s Gemini API. Google processes it under its own terms and privacy policy.

Using your own Gemini API key

You may add your own Gemini API key in Settings. It is stored in encrypted storage on your phone and sent with your Assistant messages so Google can bill the request to you. Our server uses it for that request only and does not store it. You can remove it at any time in Settings.

3. Purchases

Paying for the lifetime unlock is handled by Google Play. We never receive your card or payment details.

We use RevenueCat to confirm your purchase and to restore it if you reinstall. RevenueCat receives the app’s device ID (described in section 2), your purchase and entitlement status, and technical information such as your IP address and device type. Our server also asks RevenueCat whether a device has bought the unlock, and keeps that yes/no answer for a short time.

4. Services we use

Service What for What it receives
Convex Our server and database for the Assistant Assistant messages, rules summary, app names, device ID
Google Gemini API Writes the Assistant’s answers The same content as above, per request
RevenueCat Purchase checks and restore Device ID, purchase status, IP address, device type
Google Play Payment, app delivery, updates Handled by Google under its own policy
Google Wearable Data Layer Alarms on your watch (optional) Alarm text, device to device

These providers may process data in countries other than your own. We don’t sell your data, we don’t show ads, and the app contains no analytics or tracking tools.

5. Permissions the app asks for

6. How long we keep data

7. Your choices and rights

You can use the whole app without the Assistant, and without sending us anything. You can stop notification access, Accessibility or the Assistant at any time.

You can ask us to give you a copy of, correct, or delete the Assistant data we hold about you by emailing contact@wpmethods.com. Because the app has no accounts, please include roughly when you used the Assistant and a few words from a message so we can find your conversation. If you live in the European Economic Area, the United Kingdom, California or another place with data-protection laws, you have the rights those laws give you, such as access, deletion, objection and complaint to your data-protection authority. We will not treat you differently for using these rights.

Our legal basis for processing Assistant data (where the law asks for one) is providing the service you requested and our legitimate interest in keeping it secure and preventing abuse.

8. Security

Data sent to our server and to the services above travels over encrypted connections (HTTPS). Notification history and settings are kept in the app’s private storage, and your own API key (if you add one) in Android’s encrypted storage. No method of storage or transmission is perfectly secure, but we take reasonable care to protect your data.

9. Children

The app is not meant for children under 13 and we don’t knowingly collect information from them. If you believe a child has used the Assistant, contact us and we will delete the data.

10. Changes to this policy

If we change how the app handles data, we will update this page and the date at the top. For significant changes we will also tell you in the app.

11. Contact

WP Methods
Email: contact@wpmethods.com