Notification digest
Half of unchosen phone use is not you reaching for the phone. It is the phone reaching for you. A digest decides when that is allowed to happen.
Push and pull are two different problems
Most tools in this category deal only with pull — you reaching for the phone. That leaves the other half untouched. A notification is an interruption you did not schedule, arriving on a timetable set by whoever wants your attention, and it arrives with the same urgency whether it is a message from a person or a marketing push about a sale.
The damage is not really the seconds spent reading it. It is that an interruption converts into a session. You look at the alert, you are already in the app, and twenty minutes later you are somewhere else entirely. The notification was the pretext, not the event.
A digest changes who sets the timetable. Non-urgent notifications from apps you choose are held and delivered together, at times you set. Nothing is lost. What changes is that the arrival of a piece of information no longer determines the moment you attend to it.
Setting up a digest
- 1
Grant Notification Access
The digest is the only feature that uses this permission, and it is optional — everything else in Sanctuary works without it. It allows Sanctuary to hold selected notifications until a delivery time.
- 2
Sort your apps into two piles
The question is not how important the app is but whether a delay of a few hours would cost you anything. Calls, messages from people, calendar alerts, deliveries, and two-factor codes generally fail that test and should stay immediate. Social apps, newsletters, promotions, and app-update nudges generally pass it.
- 3
Choose delivery times that suit your day
Two or three a day is enough for most people. Midday and early evening works well. Avoid putting one immediately before bed, which reintroduces the exact interruption the evening was meant to be free of.
- 4
Leave it alone for a fortnight
The first few days feel strange, mostly because you discover how many notifications you were receiving that turned out not to matter. If something genuinely urgent ends up in the digest, move that app back to immediate — one app at a time, rather than abandoning the whole arrangement.
What Android will not let any app fix
Android delivers a notification to the screen a few milliseconds before a notification listener is able to process and dismiss it. This means that on some devices you may see an alert flash briefly before Sanctuary moves it into your digest. This is an architectural constraint of the platform rather than a bug in Sanctuary, and no notification-management app on Android can fully avoid it. If you have seen this behaviour in other tools, it has the same cause.
How the digest handles your data
- What is stored
- Notification titles and previews, on the device only.
- For how long
- Until the scheduled delivery, then cleared.
- What is transmitted
- Nothing. There is no server to transmit to.
- Permission
- Notification Access, optional, used only for this feature.
- Scope
- Per app. You choose which sources wait and which stay immediate.
- Availability
- The notification digest is part of Sanctuary Pro.
Straight answers.
- What is a notification digest?
- A digest holds non-urgent notifications from apps you choose and delivers them together at times you set, instead of interrupting you the moment each one arrives. Nothing is discarded — the notifications still reach you, just on your schedule rather than the sender’s. The point is that an interruption is what usually converts into an unplanned twenty-minute session, and removing the interruption removes the pretext.
- Which notifications should I batch?
- Ask whether a delay of a few hours would cost you anything. Calls, direct messages from people, calendar alerts, delivery updates, and two-factor codes generally would, and should stay immediate. Social app activity, newsletters, promotions, app-update nudges, and re-engagement pushes generally would not, and are good candidates for a digest. Sanctuary applies this per app, so you decide each case rather than accepting a blanket setting.
- Why does a notification sometimes flash before it disappears?
- Because of the order in which Android does two things. The system posts a notification to the screen first, and only then hands it to registered notification listeners, which is the category any digest app belongs to. That leaves a window of a few milliseconds in which the alert is already visible and Sanctuary has not yet been told about it, so on some devices you will see a brief flash before it is moved into your digest. Nothing can close that window from inside an app — it is a property of the platform, not a defect in a particular tool, and every notification-management app on Android behaves this way.
- Can Sanctuary read my notification contents?
- The digest needs to hold notification titles and previews in order to deliver them to you later, and these are stored on your device only and cleared once delivered. Nothing is transmitted, because Sanctuary has no account, no analytics, and no developer-operated server to transmit to. The Notification Access permission is optional and is used for no other purpose; every other feature works without it.
Related guides
Focus modes
Four modes that change what your phone offers, and why putting them on a schedule matters more than the modes themselves.
Screen timeReduce screen time on Android
Why total minutes is the wrong target, and a five-step setup that reduces the unchosen part of your day.
Core featureApp time limits
How daily budgets work, how to pick a number you will keep, and what happens when the budget is spent.
Mindful useMindful phone use
The gap between impulse and action, why intention beats restriction, and four practices that fit into a normal day.
Decide when you are interrupted.
The notification digest is part of Sanctuary Pro. Calls and messages stay immediate — only the apps you choose ever wait.
Get Sanctuary for Android