Notification Previews and Your Lock Screen
A notification preview shows text the app composed, on a screen anyone standing near your phone can read, without unlocking anything. For a companion app that means a message written in a persona’s voice can appear on a table in a meeting room. The app chooses the words; your phone chooses whether they are visible while locked; and those are two separate settings in two separate places.
Getting this right is mostly about the second one, because you cannot control the first.
The app writes the text, the phone decides the audience
Every notification has a title, a body, and optionally a grouping label. The app supplies all three. Some apps deliberately write neutral notification text — “New message” — and put the content behind the unlock. Many do not, because a preview containing actual content is far more effective at pulling you back in.
You cannot make an app write discreet notifications. What you can do is stop your phone from displaying the body until the device is unlocked. Both major platforms have this control, usually phrased as showing previews always, only when unlocked, or never. Setting it to unlocked-only is the single change that matters here, and it applies whether the app cooperates or not.
There is a per-app version of the same control on at least one platform, which is more useful than the global one: you can leave previews on for a maps app and off for a chat app. If your phone offers per-app preview settings, that is the level to work at.
Delivery is not the same as display
A notification arrives whether or not it is displayed. That sounds obvious and it has a consequence people miss: turning previews off does not reduce what the app knows or when it contacts you. The message still reached your device.
Notification permission is a display permission, not a data permission. Declining it does not stop the app from operating and does not reduce collection. It only stops the interruption. Conversely, allowing notifications does not grant any access to your device beyond the ability to put text on your screen and a badge on the icon.
This matters when reasoning about what an app can reach on a device generally, which is the subject of what a permission prompt actually grants. Notifications sit in the permission list next to microphone and contacts, and they are a categorically different kind of thing.
Timing is a product decision
Companion apps commonly send messages you did not ask for: a check-in after silence, a follow-up in the evening, a nudge after an app update. The timing of those is chosen by the operator, and the choice is normally informed by when you have previously responded.
Nothing about that is exotic, and nothing about it is accidental. Re-engagement notifications are standard mobile product practice across every category. What makes them worth noticing in a companion app is that the notification is written in a persona’s voice, so an operator’s retention decision arrives looking like someone thinking of you. Reading it as a scheduled message rather than a spontaneous one is more accurate and generally more comfortable.
If the pattern changes suddenly — quieter, chattier, different times of day — that is usually an app update rather than anything about you. See what an app update can change without asking.
The settings worth actually changing
There is a short list, and it is the same list on both platforms with different names.
Previews only when unlocked, ideally set per app rather than globally.
Notification grouping and summaries, which batch messages into a digest delivered at chosen times. This changes the rhythm more than muting does, because you still get the messages, just not the interruption.
Focus or Do Not Disturb schedules that exclude the app during work hours or overnight. These are more effective than in-app quiet-hours settings, because they are enforced by the operating system rather than by the app’s own scheduler.
Badges off if the unread count is the part that pulls at you. The badge is a separate toggle from previews and from sounds, and turning off only the badge is a real option.
Lock-screen widgets and Live Activities, where supported, are a third surface again. An app can occupy persistent lock-screen space without sending a single notification. Check whether the app has one enabled.
The screen is a shared surface
A locked phone face-up on a desk is readable by everyone at the desk, and a phone handed to someone to show them a photo is a phone that may buzz. This is the same class of problem as what a shared device exposes, and previews are the most common way private content becomes visible without anyone doing anything wrong.
The cheapest mitigation is unrelated to the app: turn off raise-to-wake, or turn on the setting that requires attention before showing previews on platforms that offer it. A phone that does not light up on its own when someone walks past the table solves a surprising share of this.
What this does not tell you
Preview settings control one screen. They do not affect what the app stores, what it sends, or how long it keeps anything, and they do not make a conversation private in any deeper sense — a screenshot of a chat leaves the app entirely and is governed by nothing, as covered in what a screenshot becomes after you take it.
They also cannot be relied on across accessory devices. A paired watch or headphones may read a notification aloud or display it under its own separate settings, and those settings are not inherited from the phone. If you use accessories, check them independently, because the phone’s careful configuration stops at the phone.