A notification-history app keeps a record of notifications it receives. It does not automatically read a chat application's internal message database. This distinction explains why a message can appear in the chat while being absent from the history, or remain in history after its notification has disappeared.
NotiVault preserves selected Android notification previews after setup. Its current product information describes local-first storage, selected-app capture and media preservation only when the notification exposes accessible media. The examples below help you understand those limits before relying on a capture.
The capture timeline matters
Imagine Notification Access is enabled at 10:00 and the chat application is selected. At 10:05, a new message posts a notification with a visible text preview. If NotiVault receives and stores that notification before the message is deleted at 10:06, the captured preview may remain available in the vault.
Now change the example: the message arrived at 09:50, before setup. Installing or enabling the history app at 10:00 does not retrieve that earlier message. Likewise, if the source application never posts a notification containing the text, there is no text preview for NotiVault to preserve.
| Situation | What to expect |
|---|---|
| A new selected-app notification exposes text after setup. | The text preview can be captured if access and delivery work. |
| A message was deleted before installation. | No recovery from the source chat database. |
| The notification says only “New message”. | The captured information may be only that label. |
| A photo notification exposes an accessible media URI. | A copy may be saved if that media type is enabled. |
| No accessible media is exposed. | A thumbnail, label or text-only entry may be all that is available. |
Check setup with a fresh test notification
- Enable Android Notification Access for NotiVault through the system's normal permission flow.
- Select the application whose notifications you want to capture.
- Check the selected media types and retention settings.
- Send a new test message that you control after setup. Do not use an old chat as the test.
- Confirm a notification actually appears, then check whether the vault received the same preview.
This test separates setup problems from unrealistic recovery expectations. If a new notification appears but is not captured, check that access is still enabled and that the source application is selected. If no notification appears, examine the source application's notification settings first. A history app cannot capture a notification that the source application did not deliver.
Investigate missing content in order
First ask whether the content arrived after setup. Then ask what the notification actually exposed. Some notifications group messages or hide previews; the captured record is constrained by that available information. A conversation visible inside the source application is not proof that the same text was posted in a notification.
For missing media, check the media type setting and whether an accessible notification URI was provided. A notification may show a photo-like preview without exposing a full image that another app can copy. Do not interpret every missing attachment as a broken capture.
Next check retention. A record captured successfully may later be removed under the selected retention period or by clearing app data. Keep the test small and current so these possibilities are easier to distinguish. If the problem persists, send a support description of the device, app versions, approximate test time and the observed behavior. Avoid sending private chat content just to demonstrate the issue.
Keep a useful history with a small scope
Select only the applications you need to capture. Notifications can contain private messages, addresses or account information; a larger vault is not necessarily more useful. Choose a retention period appropriate to the purpose and review it occasionally.
The current app describes captured text and media as remaining in its private storage on the device, with no cloud sync or advertising SDK. Local storage also means device loss, clearing data or uninstalling can affect the history. Check current product guidance before assuming records can be restored onto another device.
Notification history is best understood as a record of previews received after setup. It can help find a missed alert or preserve an accessible preview, but it cannot promise complete chat recovery. Read the NotiVault FAQ and privacy policy for the app's current behavior and controls.