A reader who treats the per-email unsubscribe link as the master switch and never opens the account's own preference centre, so the marketing returns under a different category.
How to Stop Amazon Marketing Emails and Notifications
The marketing channel and the transactional channel are different objects from the same sender — you can close one without closing the other, and the most common loss is nuking both and losing the security alert or the delivery notice. Here is the transactional-is-not-marketing reframe, the keep-versus-close split, the channel-by-channel audit, the notification anatomy, and the phishing-shaped-like-transactional tell. The page sorts the channels rather than silencing them; the goal is a quiet inbox without losing the alerts the account-security and missing-package guides rely on, and the discipline is to keep the transactional carve-out open, audit each channel separately, and verify a suspicious message at the source rather than unsubscribing from it.
General information only — not a device-specific menu path, not a statement of any universal preference-centre layout, and not a reason to disable security or transactional messages. This page explains the shape of sorting outbound messages — the transactional-is-not-marketing reframe, the keep-versus-close split, the channel-by-channel audit, the notification anatomy, and the phishing-shaped-like-transactional tell — in broad terms. The names and locations of the communication-preference controls, the categories offered, the behaviour of the per-email unsubscribe link, the device-level push permission, the SMS stop keyword, the in-app badge, and which messages are classed as transactional versus marketing vary by platform version, device, operating system, region, and account, and they change over time; they belong to the platform's local Help, your account's communication-preference centre, and your device's notification settings — not a guide page. And the load-bearing limits: the marketing channel and the transactional channel are different objects from the same sender, so the goal is to close the marketing without closing the transactional carve-out — the order confirmations, delivery notices, security and login alerts, refund notices, and recovery codes that the account-security and missing-package guides rely on; the per-email unsubscribe link is not the master switch and is not the same as the account's preference centre; you must audit each channel separately (email, push, SMS, in-app) because closing one does not close the others; and a suspicious message — especially one shaped like a transactional 'delivery problem' — is verified at the source, not unsubscribed, because clicking unsubscribe on a phishing email can confirm your address is live. The page sorts the channels; it does not tell you to silence the alerts that keep you safe.
Two Channels, One Sender
The Most Common Loss Is Not the Spam — It Is the Security Alert You Disabled Along With the Promotions
The mental image of stopping marketing is a single switch: unsubscribe, mute, done. The image is tidy and it is exactly what fails, because the same sender runs *two channels* — a *marketing* channel (promotions, deals, recommendations, newsletters, "we miss you") and a *transactional* channel (order confirmations, shipping and delivery notices, security and login alerts, refund and return notices, account-recovery codes). The reader who nukes the sender to silence the promotions also silences the carve-out, and the carve-out is precisely what the account-security guide and the missing-package guide rely on: the login alert that warns of a new-device sign-in, the delivery notice that starts the convergence check, the refund notice that confirms the return landed. The most common loss is not the spam. It is the security alert you disabled along with the promotions, so that a compromise arrives into a muted inbox and a missing package arrives into a silenced notification. And the second loss is subtler: a *fake* delivery-problem email is *shaped* like a transactional message, so the reader who cannot tell the two channels apart is also the reader who falls for the phishing email — and who, by clicking unsubscribe on it, confirms the address is live.
This page is the channel half of the Amazon subscription-channel-incident trio; its companions, the Prime-benefits guide and the unauthorised-purchase guide, deal with the bundle and the incident. The transactional-is-not-marketing reframe below is the verify-at-the-source discipline our account-security guide built, applied *in reverse* to the outbound channel: 111 taught you to verify a message at the source rather than act on its link; 117 teaches you to *sort* the message into marketing or transactional before you decide whether to close it — and the distinctive payload is the **transactional carve-out** (the green keep-these list the security and tracking surfaces depend on) and the **phishing-shaped-like-transactional tell** (the fake delivery email that looks like the carve-out, so the skill is sorting, not silencing). And it ends where 111 did not have to: with the **channel-by-channel audit**, because the unsubscribe link is not the master switch and closing the email preference does not close the push notification, the SMS, or the in-app badge — four separate surfaces the reader must walk separately.
The transactional-is-not-marketing reframe — the marketing channel and the transactional channel are different objects from the same sender, and you can close one without closing the other. The promotions are noise, so I will unsubscribe from everything this sender sends and be done with it. The same sender runs a marketing channel and a transactional channel. Closing the marketing categories is fine; closing the transactional carve-out — order confirmations, delivery notices, security and login alerts, refund notices, recovery codes — is a security and convenience regression, because those are the alerts the account-security and missing-package guides rely on. The discipline is to sort, not to silence. This is the reframe the page exists to make, and it is the most carefully hedged line in the batch, because the naive version — "unsubscribe from all" — leads a reader to mute the very alerts that warn of a compromise or start a delivery investigation.
The honest position is neither spam-tolerance nor total silence: a quiet inbox is a legitimate goal, and the marketing categories are genuinely closable. But the carve-out is not marketing, and the reader who achieves total silence by disabling everything has disabled the login alert (111) and the delivery notice (113) — which is worse than promotions. The discipline is to close the marketing categories and keep the carve-out, and to audit each channel separately, because the unsubscribe link is not the master switch. The page teaches the sort; it does not assert a universal preference-centre path, because the controls are device- and region-specific.
The transactional carve-out — the messages you should keep on, because the security and tracking surfaces depend on them. These are not marketing; they are the early-warning and evidence channel, and closing them is a regression, not a win.
- Order confirmations — the record that the order exists, the first exhibit in a missing-package claim (113)
- Shipping and delivery notices — the scan events that start the convergence check (112, 113)
- Security and login alerts — the new-device sign-in warning the account-security guide relies on (111)
- Refund and return notices — the confirmation that a return landed and a refund processed (114)
- Account-recovery codes and password-change notices — the route back into a locked account (111)
- Official service and policy notices — the platform's own account and compliance messages
The carve-out is the green line in the sorter: keep that slot fed, close the other. A reader who mutes the carve-out to quiet the inbox has traded a security alert for an absence of promotions — and the login alert that warns of a compromise, the delivery notice that starts an investigation, and the recovery code that unlocks the account all live in the slot you must not empty. The exact category names and which messages the platform classes as transactional are local and device-specific; read your own preference centre and the local Help rather than assuming a universal list.
Keep — the transactional channel
- Order confirmations — the existence record, the first exhibit
- Shipping / delivery notices — the scan events that start the convergence check
- Security / login alerts — the new-device warning (111 depends on this)
- Refund / return notices — the confirmation a return landed (114 depends on this)
- Recovery codes / password-change notices — the route back in
- Official service / policy notices — the platform's own account messages
The dividing line is the origin: a *transactional* message is about a transaction or a state change you initiated or that affects your account (an order, a delivery, a login, a refund, a recovery); a *marketing* message is a promotion you did not initiate (a deal, a recommendation, a newsletter, a "we miss you"). The skill is sorting by origin, not silencing by sender — and the hard case is the *fake* transactional message, the phishing email shaped like a delivery notice, which you verify at the source rather than unsubscribe from. The most common loss is emptying both slots; the second is treating the phishing-shaped-like-transactional email as ordinary marketing and clicking its unsubscribe link.
Close — the marketing channel
- Promotions and deals — the members-only offers and price nudges
- Recommendations — the "because you bought" and "you might like" lists
- Newsletters and editorial — the curated content sends
- Re-engagement — the "we miss you" and "your list is waiting" messages
- Cross-sell — the other-domain promos bundled into the same sender
- Third-party or partner marketing — where the platform offers it, the partner sends
The two bands and the divider are the page's entire method compressed into one distinction, and its power is that it converts a reflex (unsubscribe from all) into a sort (close by origin, keep the carve-out). The failure mode the split prevents is the well-meaning one: a reader who, annoyed by deal emails, hits "unsubscribe" on every message from the sender, including the login alert and the delivery notice, and then wonders why a compromise went unwarned and a missing package went unnoticed. The discipline is to sort by origin and to keep the carve-out fed. And the honest limit is stated in the same breath: the hard case is the *fake* transactional message, and the skill that sorts marketing from transactional is the *same* skill that sorts transactional from phishing — so the page that teaches the sort also teaches the verify-at-the-source rule, and the unsubscribe link is for legitimate marketing only.
The channel-by-channel preference audit — four surfaces, walked separately, because closing one does not close the others
1
Email — the account's communication-preference centre, not the unsubscribe linkOpen the account's own communication-preference or email-settings surface and close the *marketing* categories while leaving the *transactional* carve-out on. The preference centre acts across categories; the per-email unsubscribe link usually acts on one list. Start at the centre, not the footer.
The 102 check-your-own-page method applied to notifications: the authoritative surface is your account's preference centre, reached while signed in, not a link in a message.
2
Push — the device-level notification permission, a separate surface againClosing the email preference does not close the push notification. Push is governed by the device's own notification permission for the app (and per-category, where the OS supports it), which is a different surface from the account centre. Audit it separately, and keep the security and delivery categories if the OS allows per-category control.
The 107 sync discipline applied to notifications: an account setting is not a device setting, and the push permission lives at the OS level, not the account level.
3
SMS — the text stop keyword, a third channelWhere the platform sends marketing by text, the stop route is often a keyword reply or a separate text-preference setting, not the email centre. Audit it separately, and keep any transactional texts (delivery codes, security one-time codes) if the channel carries them.
The channel-by-channel rule: email, push, and SMS are three independent taps; closing one leaves the others running.
4
In-app — the badge, the inbox tab, and the home-screen promotionsMarketing also lives *inside* the app — the notification badge, the promotions tab, the home-screen carousels. These are governed by in-app settings and the account centre, not by the email or push channels. Audit the in-app surfaces separately.
The fourth tap: the badge and the in-app inbox are a channel of their own, and muting email does not mute the home-screen deal carousel.
5
Verify the carve-out survived the sort, and test a security alert if the surface allowsAfter closing the marketing categories across all four channels, confirm the transactional carve-out is still on — the order confirmation, the delivery notice, the login alert, the refund notice, the recovery code. Where the platform offers a test or a recent-activity view, use it, because a carve-out silently disabled during the sort is the loss this page exists to prevent.
The 111 dependency check: the login alert and the delivery notice are the carve-out's two load-bearing messages; confirm they still reach you after the sort.
6
Apply the phishing-shaped-like-transactional rule to anything that asks you to actAny message — marketing or apparently transactional — that asks you to click a link, approve a login, update a payment, or resolve a 'delivery problem' is verified at the source: open the app or site directly and check the order or account state there. Do not click unsubscribe on a suspicious message, because it can confirm the address is live; report it through the platform's tools instead.
The load-bearing guardrail of the page: the sort that separates marketing from transactional is the same skill that separates transactional from phishing, and the unsubscribe link is for legitimate marketing only.
The sequence's logic is the channel-by-channel audit, walked separately and verified at the end: email centre → push permission → SMS stop → in-app surfaces → confirm the carve-out survived → apply the phishing rule to anything that asks you to act — because the most common failure is a reader who closed the email marketing categories, assumed that silenced everything, and left the push badge and the SMS running, or who closed the carve-out with the marketing and lost the login alert. The discipline is to treat the four channels as four independent taps, to keep the carve-out fed, and to end the audit by verifying that the security and delivery messages still arrive. And the honest limit is that the menu paths and the per-category controls are device- and region-specific; the page teaches the audit, not the layout of any one preference centre.
The notification anatomy — the surface, what it controls, and the limit
The preference centre (categories)
The vector
The check
Start at the account's communication-preference centre, which acts across categories, and close the marketing categories while leaving the transactional carve-out on. The footer link is a shortcut for one list, not the master.
The per-email unsubscribe link
The vector
A reader who clicks unsubscribe on a *suspicious* message, confirming the address is live to a phishing sender, or who relies on the footer link to stop all marketing from a sender.
The tell
The unsubscribe link is for legitimate marketing from a sender you actually use. A suspicious message is verified at the source and reported, not unsubscribed. And the footer link acts on one list, not the sender's whole output.
The device push permission
The vector
A reader who mutes email and assumes the lock-screen notifications stopped too, because both come from "the app."
The check
Push is governed by the device's own notification permission for the app, a separate surface from the account centre. Audit it separately, and keep the security and delivery categories where the OS allows per-category control.
The SMS stop keyword
The vector
A reader who closes email and push and still gets marketing texts, because the SMS channel is independent again.
The tell
Where the platform texts, the stop route is a keyword reply or a separate text preference, not the email centre. Keep any transactional texts (delivery codes, security one-time codes) if the channel carries them.
The in-app badge and carousels
The vector
A reader who quiets the inbox and the lock screen and still sees the deal carousel and the red badge inside the app.
The check
The in-app surfaces are a fourth channel, governed by in-app settings and the account centre, not by email or push. Audit them separately; the home-screen promotions are marketing even when the email is silent.
The transactional carve-out
The vector
A reader who, in the rush to silence marketing, disables the order, delivery, security, refund, and recovery messages — the very carve-out 111, 113, and 114 depend on.
The tell
The carve-out is not marketing. Confirm it survived the sort, because a login alert or a delivery notice silently disabled during the audit is the loss this page exists to prevent. The exact category names are local; read your own centre.
The phishing-shaped-like-transactional message
The vector
A reader who cannot tell marketing from transactional, and so also cannot tell transactional from phishing — and who treats a fake delivery email as either spam to unsubscribe from or a real notice to act on.
The check
The sort skill is the same skill as the phishing discrimination. Verify any message that asks you to act at the source — open the app or site directly — and report a suspicious one rather than unsubscribing. The unsubscribe link is for legitimate marketing only.
| Surface | What it controls | The limit | What to check |
|---|---|---|---|
| Preference centre | Marketing vs transactional categories | Not reached by the footer link | Start here, signed in; keep the carve-out |
| Unsubscribe link | One list, usually | Live-address confirm on phishing | Legitimate marketing only; verify suspicious first |
| Push permission | Lock-screen / banner alerts | Independent of email centre | Audit separately; keep security/delivery categories |
| SMS stop | Text marketing | Independent channel again | Keyword or text pref; keep transactional texts |
| In-app surfaces | Badge, inbox tab, carousels | Fourth channel, not email/push | Audit separately; deals are marketing in-app too |
| Carve-out | Order/delivery/security/refund/recovery | Disabled by over-eager sort | Confirm it survived; 111/113/114 depend on it |
| Phishing shape | Fake transactional messages | Looks like the carve-out | Verify at source; report, do not unsubscribe |
The anatomy is the same claims-vs-mechanism habit the payslip, bill, and account-security guides taught, applied to a notification surface where the claim is "I stopped the emails" and the mechanism is the four channels plus the carve-out plus the phishing shape. A footer unsubscribe is not the master switch. A muted email is not a muted push. A quiet inbox is not a safe account if the carve-out is disabled. A deal carousel is not "not marketing" just because it lives in the app. A fake delivery email is not ordinary spam. The discipline is the anatomy: walk the four channels, keep the carve-out, and apply the sort skill to the phishing shape — because the most common loss is the security alert disabled along with the promotions, and the second is the phishing email unsubscribed from, confirming the address live.
The phishing-shaped-like-transactional tells — when a message looks like the carve-out but is not
a 'delivery problem' link you did not initiate
a 'payment declined — update card' request
a 'confirm your login' approval prompt
a sender domain that looks right but is not
urgency around a delivery you are expecting
a request to share a one-time code
an unsubscribe link on a message you never received from the real sender
a 'package held — pay a small fee' text
The tells are the fake-transactional forms that wear the carve-out's clothing, and the discipline is to read them as the phishing-at-the-doorstep vector the account-security guide names, not as marketing to unsubscribe from. The sort that separates marketing from transactional is the *same* skill that separates transactional from phishing — so the reader who learns to keep the carve-out and close the marketing also learns to verify a message that asks them to act. The guardrail is load-bearing: the unsubscribe link is for *legitimate* marketing from a sender you actually use; a suspicious message is verified at the source (open the app or site directly, check the order or account state) and reported, never unsubscribed, because clicking unsubscribe on a phishing email can confirm your address is live. And the reciprocal limit: do not let the phishing fear push you to disable the *real* carve-out — the login alert and the delivery notice are the messages you must keep, and the way to tell them from the fakes is the source check, not the mute.
A worked example: the two readers, and the one who sorted the channels
Concretely, the transactional-is-not-marketing reframe, the carve-out, the keep-versus-close split, the channel-by-channel audit, the notification anatomy, and the phishing-shaped-like-transactional tells meeting two readers who are both tired of deal emails from the same sender.
Reader one silences the box and loses the carve-out. Annoyed by the promotions, reader one hits "unsubscribe" on every message from the sender, including a login alert and a delivery notice, and then mutes the app's notifications at the device level to be sure. The inbox is quiet. Two weeks later, a new-device sign-in goes unwarned because the login alert was unsubscribed, and a package marked delivered goes unnoticed because the delivery notice was muted — and when a *fake* "delivery problem" email arrives, reader one, unable to tell it from the real carve-out they disabled, clicks its unsubscribe link, confirming the address live to a phishing sender. The loss is not the spam; it is the security alert and the delivery notice disabled along with the promotions, and the phishing email treated as marketing. The sort was never learned; only the silence.
Reader two sorts the channels and keeps the carve-out. The same deal emails, the same annoyance — but reader two opens the account's communication-preference centre and closes the *marketing* categories (promotions, recommendations, newsletters, re-engagement) while leaving the *transactional* carve-out on (order, delivery, security, refund, recovery). They then audit the other three channels separately — the device push permission (keeping the security and delivery categories where the OS allows), the SMS stop keyword (keeping transactional texts), and the in-app badge and carousels — because closing email does not close push. They confirm the carve-out survived by checking a recent order's confirmation and a login-alert setting. When a "delivery problem" email arrives, reader two verifies at the source — opens the app directly, sees no problem on the order page — recognises the phishing shape, reports it, and does not click unsubscribe. The inbox is quiet *and* the login alert still arrives *and* the phishing email found no live address to confirm. The sort was learned; the silence was selective.
The lesson is the whole page. Both readers had the same deal emails and the same sender; the difference was not the platform but the sort. Reader one silenced the box and lost the carve-out, then fell for the phishing email shaped like the carve-out they had disabled. Reader two sorted by origin, kept the carve-out fed across all four channels, verified the sort, and applied the same discrimination to the phishing shape. The transactional-is-not-marketing reframe is what prevented the silence-with-loss — the same sender runs two channels, and the goal is a quiet inbox *without* muting the alerts that keep you safe — and the honest limit is that the page cannot assert your preference-centre layout or your device's per-category controls, because those are local and device-specific. The most common loss is the security alert disabled along with the promotions, and the discipline is to sort the channels, keep the carve-out, and verify a message that asks you to act at the source.
The Check
A Sensible Default
- Hold the reframe: the marketing channel and the transactional channel are different objects from the same sender — close one without closing the other; the goal is a quiet inbox *without* losing the alerts.
- Keep the transactional carve-out on: order confirmations, delivery notices, security and login alerts, refund notices, recovery codes, official service notices — the surfaces 111, 113, and 114 depend on.
- Run the channel-by-channel audit separately: email preference centre → device push permission → SMS stop keyword → in-app badge and carousels — because closing one channel does not close the others, and the footer unsubscribe link is not the master switch.
- Read the notification anatomy: the preference centre, the unsubscribe link, the push permission, the SMS stop, the in-app surfaces, the carve-out, the phishing shape — each a surface with a limit.
- Sort by origin, not by sender: a transactional message is about a transaction or state change you initiated or that affects your account; a marketing message is a promotion you did not. The skill that sorts them is the same skill that sorts transactional from phishing.
- Apply the phishing-shaped-like-transactional rule: verify any message that asks you to act at the source (open the app or site directly), report a suspicious one, and never click unsubscribe on a message you did not initiate from the real sender — it can confirm the address live.
- Confirm the carve-out survived the sort: after closing the marketing categories, check that a login alert and a delivery notice still reach you, because a carve-out silently disabled during the audit is the loss this page exists to prevent.
- Route the specifics out: preference-centre layout, category names, per-category push control, SMS stop route, and which messages are classed transactional belong to the platform's local Help, your account's preference centre, and your device's notification settings — not a guide page.
The honest takeaway is that stopping marketing is a sort rather than a silence, and the discipline that gives you a quiet inbox *and* a safe account is keeping the transactional carve-out fed while closing the marketing categories across all four channels — email, push, SMS, in-app — and applying the same origin-sort to the phishing email that wears the carve-out's clothing. For the verify-at-the-source rule this page applies in reverse, see our account-security guide; for the login alert and the delivery notice that live in the carve-out, see our account-security and missing-package guides; for the refund notice the carve-out carries, see our returns guide; for the memory-and-recommendation surface that is *different* from the outbound channel (clearing history does not stop email), see our clear-watch-history and manage-search-history guides; for the extraction decoder the phishing shape imports, see our recognition-and-resistance cluster; and for the actual preference-centre layout, category names, per-category push control, and SMS stop route, see the platform's local Help, your account's communication-preference centre, and your device's notification settings — the authorities this page keeps routing you to, because the shape of the sort is durable, the specifics are not ours to assert, and the security alert you disabled along with the promotions is the loss.
Common Questions
Frequently Asked Questions
How do I stop marketing emails without losing order and security messages?
By sorting the channels rather than silencing them. The marketing messages (promotions, deals, recommendations, newsletters) and the transactional messages (order confirmations, shipping and delivery notices, security and login alerts, refund and return notices, account-recovery codes) are different objects from the same sender, and the account's communication preferences usually let you close the marketing categories while leaving the transactional ones on. The discipline is to keep the transactional carve-out open, because the security alert the account-security guide depends on and the delivery notice the missing-package guide depends on both live in that carve-out.
Is the unsubscribe link at the bottom of an email the same as the account settings?
No, and the difference is the most common confusion. The unsubscribe link in a marketing email usually acts on that one category or list, while the account's communication-preference centre acts on categories across channels; and the device-level push permission, the SMS stop keyword, and the in-app badge are separate surfaces again. The discipline is to audit each channel separately — email, push, SMS, in-app — because closing the email preference does not close the push notification, and the unsubscribe link is not the master switch.
I got a 'delivery problem' email. Should I unsubscribe from it?
No — verify it at the source first, and do not click unsubscribe on a suspicious message. A fake delivery-problem email is shaped like a transactional message, and clicking an unsubscribe link on a phishing email can confirm to the sender that your address is live. The discipline is the same verify-at-the-source rule the account-security guide applies: open the platform's own app or site directly and check the order there; if the order page shows no problem, the message was the phishing-shaped-like-transactional tell, and you report it rather than unsubscribing.
Will muting notifications make my account less secure?
It can, if you mute the transactional carve-out along with the marketing. The login and security alerts, the delivery notices, and the refund notices are the early-warning and evidence surfaces the account-security and missing-package guides rely on; silencing them for inbox peace is a security and convenience regression, not a win. The discipline is to mute the marketing categories and keep the carve-out, and to remember that a quiet inbox and a safe account are two different goals that the same preference centre serves.
I closed the email marketing but still get push notifications and texts. Why?
Because the channels are independent, and this is the channel-by-channel audit in action. The email preference centre, the device push permission, the SMS stop keyword, and the in-app badge are four separate surfaces; closing the email marketing categories does not close the push notification (governed by the device's own notification permission for the app), the marketing text (governed by a keyword reply or a separate text preference), or the in-app deal carousel (governed by in-app settings). The discipline is to walk all four taps, keeping the transactional carve-out on each channel where the surface allows, rather than assuming one closure silenced the sender everywhere.
Does clearing my watch or search history stop the marketing emails?
No, and the two surfaces are different jobs. Clearing or pausing history (the watch-history and search-history guides) manages what the platform *remembers and recommends*; the communication-preference centre manages what it *sends you*. A reader who clears history may still receive marketing email, because the outbound channel is a separate surface from the memory; and a reader who mutes email may still see personalised recommendations inside the app, because the recommendation engine is a separate surface from the notification channel. The discipline is to treat the quiet inbox and the quiet profile as two audits, not one, and to walk the communication-preference centre for the former and the history/recommendation controls for the latter.
The platform classes some messages as 'transactional' that feel like marketing. Which do I keep?
Keep the ones that are about a transaction or a state change you initiated or that affects your account — the order, the delivery, the login, the refund, the recovery code, the official service notice — and close the ones that are promotions you did not initiate, whatever the sender labels them. The label is not always the origin: a 'recommendation' framed as a service update is marketing, and a 'your package is out for delivery' is transactional even if it carries a small promo. The discipline is to sort by origin rather than by the sender's category name, to keep the carve-out's six message types fed, and to read your own preference centre for the actual category names, because the classification is local and the page does not assert a universal list.
Ask our AI. Sorting a channel or keeping the carve-out? Tap the chat icon and tell us which channels are noisy (email, push, SMS, in-app), which messages you rely on (order, delivery, security, refund, recovery), and whether a suspicious message is in play, and it can walk the channel-by-channel audit, name the carve-out, and flag the phishing-shaped-like-transactional rule — and it will never tell you to disable the security or delivery alerts, or to unsubscribe from a suspicious message. It will route the preference-centre layout and per-category controls to the platform's local Help, your account's preference centre, and your device's notification settings.
More commerce & privacy guides like this
We treat stopping marketing as a sort rather than a silence — so the discipline is keeping the transactional carve-out fed while closing the marketing categories across all four channels (email, push, SMS, in-app), and applying the same origin-sort to the phishing email that wears the carve-out's clothing, because the security alert you disabled along with the promotions is the loss.
Explore All GuidesKeep Reading
Sources:
Other Projects
More from the creator
Explore two other projects from the same creator.