Notice Keeper — Privacy Policy
Last updated: 2026-10-08
This privacy policy applies to the mobile app "Notice Keeper" for Android:
- Google Play: package com.moon.notifhistory, developer "janey-moon"
The app is developed and operated by Heekyung Moon (Google Play developer name: janey-moon).
Contact: ansgml2100@gmail.com
OVERVIEW
Notice Keeper does not require an account, and we do not sell personal information. With your permission, it saves a history of the notifications that other apps show on your phone, so you can search them, see how a notification changed, and see when it was removed. The history is kept in a database in the app's private storage on your device. The app also uses Google services for analytics, crash reporting, remote configuration, and advertising. The app does not include notification content in analytics events or ad requests, and does not upload it to Firestore.
NOTIFICATION ACCESS (SENSITIVE DATA)
Notice Keeper uses Android's notification access (a notification listener service), which lets the app read the notifications that other apps post. Notifications can contain personal and sensitive information, including messages and names from other people.
Before the app sends you to the Android notification access setting, it shows a full-screen explanation of what is read and saved, and asks you to choose "Agree and continue" or "Not now". The app opens the Android setting only after you agree, and it saves notifications only after you have agreed and turned on access in Android Settings. Notifications shown before that are not saved and cannot be recovered. If you choose "Not now", the app does not open the setting; while access is off, nothing is captured and the rest of the app can still be opened. You can turn notification access off at any time in Android Settings; capture then stops, and the history already saved stays until you delete it.
While access is on, the listener runs in the background, including when the app is closed. For each notification it saves, the app records: the posting app's package name and app name, the notification channel and category, the title, text, expanded text, and sub-text that Android exposes, the time the notification was posted and its own time value, whether it was an ongoing notification, the time the app received it, Android's identifier for the notification, and a version number. When the same notification is updated, each changed version is saved. When a notification is removed, the app records the removal time and whether it was dismissed by you, cleared with others, cancelled by the app, or removed for another reason. The app also saves a small copy of the posting app's icon in its cache. The app does not save notification images, attachments, or action buttons, and content that Android or the posting app does not make available to notification listeners is not captured.
The app does not save notifications from Notice Keeper itself (except its own test notification, below) or from Android System UI by default. Ongoing media playback notifications are excluded by default; you can change this on the Apps tab. On the Apps tab you can also exclude any app by switching it off or entering its package name. Excluding an app affects future notifications only; its existing history stays until you delete it.
Search works on the saved titles and text using an index stored in the same database. Your search words are used only to run the search in the app and are not saved.
OTHER PERMISSIONS AND FEATURES
Notifications: on Android 13 and later, the app asks for notification permission only when you tap "Send test" on the Health tab after agreeing to the explanation above. The test posts one notification from the app to check that capture is working. The result of the latest test is kept in the app's settings, and the database entry made for each test is removed by a later cleanup once it is about 7 days old. If you decline, the test reports that permission was denied; capturing other apps' notifications does not depend on this permission.
Vibration: the app uses vibration, a permission Android grants without asking, for short haptic feedback when you tap.
The Health tab reads your device maker's name to show battery tips and a link to that maker's support page, which opens in your browser if you tap it. It can also open Android's battery and app settings. The app does not request camera, microphone, location, contacts, photos and media, or storage access.
EXPORTS AND RESTORE
On the Health tab you can export the history as a backup (.sqlite), a readable file (.json), or a table (.csv). Exports contain the saved notification content. The .sqlite backup also contains your capture settings (retention, excluded apps, media exclusion, Hide screen content) and the identifiers of deleted notifications; the .json file contains the identifiers of deleted notifications. Export files are written to the app's cache and are not encrypted. "Share or save file" passes the file to the Android share sheet, and the app or person you choose receives it. The app normally deletes completed export files when you delete history, when automatic retention removes history, or when you restore a backup, and when the app starts it normally deletes export files older than about a day.
"Restore history backup" opens the system file picker, which needs no storage permission, and accepts a .sqlite backup. The file is copied into a temporary file in the app's storage, merged with your history, and the temporary copies are then deleted; if the app is closed during a restore, leftover temporary files are normally deleted the next time it starts. Notifications deleted in either place stay deleted, and any capture settings in the backup replace your current settings.
INFORMATION STORED ON YOUR DEVICE
The notification history, search index, test records, identifiers of deleted notifications, and capture settings are stored in the app's database and preferences. The app keeps history for 30 days by default; under "Keep history" on the Health tab you can choose 7, 30, 90, or 365 days or "Until I delete it". Older history is deleted by a cleanup that runs when the capture service connects, when the app starts, about once a day in the background, and when you change settings or export; battery saving can delay it. The app sets no limit on the number of saved notifications, and restoring a backup does not apply a count limit either.
The app may also store basic operating information such as an app-use count, whether the review prompt was requested, the times full-screen ads were last shown, whether you agreed to the notification access explanation, the last capture time and test result, and cached advertising settings and More Apps list.
The developer does not run a server that receives your notification history. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not write to Firestore or upload your notification history or exports. The More Apps list loads app icons from internet addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, a splash screen view, sessions, an app-use count, review prompt events, whether a launch ad was shown, ad revenue events (ad format, value, currency, and precision), app version, device type, and app-instance identifiers. No event parameter carries notification content, app names from your history, search words, or other values you enter.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob: an app-open ad when the app starts or when you return to it, an interstitial ad that may appear after you tap Done on the export screen (from the second export while the app is open), a banner ad on the Timeline tab, and a native ad in the exit dialog. Google may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location. The app does not start a full-screen ad (app-open or interstitial) while a notification's details, the menu, the exit dialog, the notification access explanation, or the export screen is open, or while the app is carrying out an action such as an export, restore, or deletion.
ADVERTISING CHOICES
At launch, before ads are requested, Google's consent message (UMP) is checked and shown where required (for example in the EEA and UK). If that step completes and Google reports that ads cannot be requested, the app does not request ads. Personalized ads are requested only when consent is not required or your choice allows personalized advertising; otherwise ads are non-personalized. If the consent step fails (the consent information cannot be updated, the consent message cannot be loaded, or your saved choice cannot be read), the app requests non-personalized ads only.
Where Google requires it, the app menu shows "Advertising privacy choices", which reopens the consent message so you can change your advertising choice. If that message cannot be opened or your new choice cannot be read, the app stops requesting ads until it is closed and started again.
STORAGE AND YOUR CONTROL
On a notification's detail screen, Delete removes that notification and all its saved versions from the history. On the Health tab, "Delete all history" removes every saved notification. For a short time after a deletion (the Undo button is shown for about 25 seconds) you can tap Undo; the app keeps a copy of the deleted notifications in its database for about 30 seconds for this purpose, and that copy is removed at a later cleanup. The app keeps the identifiers and deletion times of deleted notifications, including those removed by the retention cleanup (not their content), so that restoring an older backup does not bring them back; "Delete all history" does not remove these identifiers. A cached app icon is normally removed at a later cleanup once no saved history from that app remains.
You can also exclude apps, change how long history is kept, and turn off notification access as described above. Clearing the app's storage in Android Settings or uninstalling the app removes the history and the other data in the app's storage. Exports you shared are controlled by the app or person that received them, or by the place where you saved them.
The app is configured to turn off Android system backup for its data, and to exclude its database, preferences, and files from cloud backup and device-to-device transfer.
Because we do not receive your notification history, we cannot delete it for you; the controls above remove it from the app. For questions about data processed by Google, or to ask us for help with a privacy request, contact us at the address below.
We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy. Data processed by Google is retained according to its service settings and policies:
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
SECURITY
The notification history is kept in the app's private storage, which the operating system protects from other apps; it is not separately encrypted by the app, so protect your device with a screen lock. The "Hide screen content" option on the Health tab blocks screenshots and hides the app's preview in the recent apps screen; it is not an app lock. Export files are not encrypted, so anyone who receives one can read the notifications in it. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app handles to what is described in this policy.
IMPORTANT NOTICE
Notice Keeper saves only what Android makes available to it while notification access is on and the capture service is running. Battery restrictions, device settings, or the posting app can prevent or delay capture, and a passed test does not guarantee that every later notification will be saved. The history shows notifications as they were displayed, not the original messages, and should not be relied on as a complete or verified record. Notifications may contain other people's information; use the history and any exports responsibly.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Heekyung Moon (Google Play developer: janey-moon)
Email: ansgml2100@gmail.com