Using Pingwright
Pingwright helps you automate Android notifications. You can use it without creating an account. Notification matching, automations, and saved history are processed and stored on your device.
Notification access and recent samples
When you grant notification access, Pingwright can read eligible notifications supplied by Android while the app is open or in the background. It reads the source app name and package, notification title and message, time, and available notification actions so it can match automations and show useful samples.
The recent-notification picker keeps the latest 40 eligible samples on your device, including notifications from apps that do not match an automation. Pingwright excludes its own notifications and Android group-summary cards from these samples. Android may withhold some notifications or their content.
The app picker uses the installed apps Android makes available to Pingwright. This information helps you choose which app an automation should match.
Automations, Activity, Important Events, and Vault
Saved automations contain your app filters, matching text, schedules, actions, and settings. Activity receipts can include notification content and the results of actions. Important Events keep a notification snapshot and acknowledgement, reminder, and escalation state. Archive saves a notification to Vault before asking Android to dismiss the original card.
These records use app-private local storage. Pingwright does not automatically upload its Activity, Vault, or technical diagnostics to a support service.
Optional actions that pass data elsewhere
A webhook is optional and runs only when you configure it in an automation or escalation stage. It sends an automatically built payload to the HTTPS URL you enter: the notification app package, title, message, timestamps, delivery identifier, and automation identity. An escalation webhook also includes the related Important Event and stage information.
Webhook payloads are stored locally while delivery is queued or retrying. The receiving server controls what happens to data after delivery; its privacy practices apply. Clearing local history does not delete a copy already received by that server.
Copy passes the configured text to the Android clipboard and marks it sensitive when Android supports that flag. Speak passes text to the device text-to-speech engine, whose settings and data practices apply. Reply and notification-button actions pass the action or response to the original app. Notifications, speech, and alarms can make configured information visible or audible to people nearby.
Retention limits
Retention uses item counts, not a fixed number of days. The recent picker keeps 40 samples, Activity keeps 100 automation receipts and 100 webhook delivery records, and Vault keeps 250 archived notifications. New entries replace older history when a store is full.
Important Events keep up to 250 records, including at most 100 open events. Open events are protected while older acknowledged history is removed. The webhook queue holds up to 100 pending jobs and protects pending work; if an active-work limit is reached, new work reports a failure instead of replacing existing active work.
Each webhook delivery retains up to 12 attempt records. Native execution, debug, technical-failure, and listener-reliability logs each keep up to 100 entries. The setup and reliability history in the app keeps up to 50 entries.
Your controls and deletion
You can edit, disable, or delete automations. Revoke notification access in Android settings to stop new notification monitoring. Revoking permission or disabling an automation does not by itself erase history already saved on the device.
Clearing recent samples removes the samples currently saved. New eligible notifications can add samples while notification access remains enabled.
Clear recent samples in Settings, clear Activity or acknowledged Important Event history in Activity, and delete individual Vault items or clear Vault. Technical failure diagnostics have a separate clear control in Diagnostics. Clearing completed history keeps open Important Events and queued or retrying webhook work.
Acknowledge an Important Event to stop its future repeat reminders and unexecuted escalation stages. A webhook already queued or sent can still finish. To remove all app-local data, use Android app storage settings to clear Pingwright data or uninstall the app. This also removes saved automations; it does not erase data already passed to another app or server.
Policy updates
This policy describes the data handling in this version of Pingwright. If that handling changes, the policy and the relevant in-app explanations will be updated.
Privacy and support contact
Pingwright
goodheartedmen@proton.me