← Hide Persistent Notification

The app Hide Persistent Notification does not collect any personal information. Hiding notifications works fully offline; anonymous usage telemetry is sent when a connection is available, and it can be turned off at any time from the in-app settings.

The app does need access to the notifications on your device, but it does nothing with them except display them in the app so you can choose which ones to hide.

You can choose to log the currently visible notifications and send them to the developer to help diagnose a problem. Before anything is sent, sensitive information is removed as best as possible, and you can review the result in a text editor inside the app. Only after you are satisfied do you decide whether to send the data.

If you opt in, the app stores a small marker file in its own folder on your Google Drive to recognise a previous install. No notification content or personal information is uploaded.

A small amount of analytics is included in the app, starting with version 2.0 (earlier versions contained no analytics). No personal information (PII) is included in this telemetry. See What data is collected by TelemetryDeck SDK for apps? for the defaults. In addition, the developer records:

• Screen navigation within the app
• Notification access permission requested and granted
• A notification added to the hide list (with the package name of the app it belongs to)
• A hidden notification shown again
• Auto-snooze triggered (with the package name of the app)
• History cleared
• Logs exported
• Google Drive opt-in prompt shown, and your choice (accepted or declined)
• Google Drive marker result (success or failure, with an error description if it failed)
• Legacy entitlement granted or restored (a carried-over purchase from the previous app version, with the restore result)
• Anonymous analytics turned on or off
• Social media link opened (which link was tapped)
• Other Apps entry tapped (with the package name of the app that was tapped)
• In-app update events (update available, started, downloaded, failed) on the Google Play build
• Errors and unhandled exceptions (an internal error id, the error message, and a category such as thrown-exception, user-input, or app-state)