What Is a Notification Log?
A notification log is a record of the notifications an Android phone has received. It keeps the app name, title, message text and time so you can review alerts after they are dismissed. Android keeps a short built-in history; a dedicated logger such as NotiLog keeps a searchable, encrypted copy that stays on the device.
How Android's built-in notification history works
Since Android 11, phones include a system notification history at Settings → Notifications → Notification history.
- It is off by default — you have to enable it.
- It keeps only a short window (roughly a day) and a limited number of entries.
- It shows minimal detail and cannot be searched or filtered by app.
- Clearing it, or the system expiring entries, removes the record permanently.
It is a convenience for "what was that alert I just dismissed", not an archive.
What a dedicated logger adds
- Continuous capture — every notification is stored as it arrives, not for a day.
- Full detail — title, body, expanded text, sub-text, app label, conversation and timestamp.
- Search — full-text across message text and app name, plus filters by app and date.
- Conversation grouping — chat apps are grouped into threads, like a messaging app.
- Favorites and pins — keep the entries you check often; they survive bulk deletes.
- Encrypted export — back up to a file you control, protected by a passphrase.
What actually gets stored
| Field | Example |
|---|---|
| App | WhatsApp, Messenger, SMS, Gmail, a delivery app |
| Title / sender | "Ana" or "Order update" |
| Text | The message body as shown in the notification |
| Expanded text | Longer body shown when the notification is expanded |
| Conversation | Chat thread identifier, where the app provides one |
| Time | When the notification was posted |
| Image | Local copy, when the notification carries one |
Content an app never puts in a notification — such as messages only rendered inside the chat screen — cannot be captured by any logger.
Local vs cloud logging
| Local (NotiLog) | Cloud logger | |
|---|---|---|
| Where data lives | On your phone only | On a vendor's server |
| Account | Not required | Usually required |
| Works offline | Yes | Partly |
| Sync across devices | No (encrypted export instead) | Yes |
| Data after uninstall | Erased | Retained by vendor |
NotiLog is local-only by design: there is no account, no server, and no analytics.
Privacy considerations
Notification Access is a broad permission — it can see every notification. Before granting it to any logger:
- Exclude sensitive apps by default. NotiLog excludes banking, 2FA, password managers and OTP apps out of the box.
- Check for encryption at rest. NotiLog uses SQLCipher (AES-256) with the key in the Android Keystore.
- Confirm backup behaviour. NotiLog sets
allowBackup="false", so history is not copied into Google's device backup. - Check what leaves the device. In NotiLog, nothing does — no account, no analytics, no crash reporting.
- Optional PIN. Protects against accidental or casual deletion.
Questions
Is Android's notification history the same as a notification log?
No. The system history is off by default and keeps roughly a day. A dedicated log captures continuously and is searchable.
Where is the log stored?
In a local database on the phone, encrypted with SQLCipher (AES-256) and the Android Keystore.
Does it drain the battery?
The listener is light — it reacts to notifications the system already delivered. Battery saver stopping the app is the real risk, so set battery usage to unrestricted.
Can it read deleted messages?
Only if the notification arrived first — see seeing deleted messages.
Does it need root?
No. Notification Access is a standard, user-granted permission.
Is it allowed?
Yes. It stores notifications your own device received, using a permission you grant. It does not read other apps' private data.