Chrome and OS defenses against notification abuse
Browser rules that quiet, throttle and auto-revoke abusive notification sites.
In one line
Can't keep sending spam if you block it; Chrome quiets and removes abusers
Browser rules that quiet, throttle and auto-revoke abusive notification sites.
Shows how the browser limits what an ignored or abusive site can do: a quiet prompt chip, auto-revocation, server-side throttling at FCM. A site that is ignored keeps no permission and sends nothing.
What it can and can't do
What the user does: You ignore the prompt, tap Block, or tap Unsubscribe on a notification
It can
- Show a quiet chip instead of a loud pop up for sites people rarely allow
- Remove permission for sites you have not used in a while
- Let you review removed sites in Safety Hub, or unsubscribe with one tap on Android
It cannot
- Send anything after you block it or it is auto removed
- Send notifications from a site you never allowed
- Use a big pop up on every visit for a site that you ignored
- Skip these checks in Chrome, Edge or Firefox
How it differs between platforms: Chrome, Edge and Firefox have these protections. Safari and iPhone browsers use different rules.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 80 | 2020-02-04 | Quiet UI 80, auto-revocation 2024 to 2026 |
| Edge | Supported | 80 | 2020-02-07 | None |
| Firefox | Supported | 72 | 2020-01-07 | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 80 | 2020-02-04 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | n/a (browser policy, Safety Hub, FCM throttling) |
| Permission name | notifications |
| How access is granted | settings |
| What the user sees | Quiet prompt chip, Notifications blocked message in the address bar, Safety Hub revocation list, Android one-tap unsubscribe. |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Revoked permissions can be re-granted from Safety Hub |
| How to take it back | Safety Hub, Site settings, notification Unsubscribe action |
| Inside an iframe | Not applicable |
Typical flow
- Site asks for permission
- Chrome decides to show quiet UI based on past allow rate and abuse signals
- Chrome revokes after low engagement or repeated warnings
- FCM throttles domains above 1,000 messages per minute and returns HTTP 429
Data you get
What comes back: Policy outcomes
Shape: none
How often: ongoing
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
FCM throttle | integer | messages per minute | 1,000 | per domain |
Chrome dismissals before block | integer | count | 3 consecutive dismissals | then 7 day embargo (not primary verified) |
Auto-revoke escalation | days | days | 1 then 7 then 14 | back to normal after about 42 days (secondary source) |
Technical limits
- Cannot be opted out of by the site
- Installed PWAs keep access in Chrome
- Numbers other than the FCM limit come from secondary sources
The story
What it is
Browser rules that quiet, limit and switch off notification permissions from sites that spam you.
For you
You may see a small quiet icon instead of a big prompt. Chrome may also remove permissions from sites you never use. You get fewer pop ups and fewer spam alerts.
For makers
Makers must earn permission by asking at the right moment and sending useful alerts. Spammy sites lose permission automatically. Browsers use this to keep notifications trusted.
Where you see it
| Type | Example | Apps |
|---|---|---|
| news | A news site that asks for permission on first page load gets quiet prompts, so it waits to ask after a reader reads two articles. | None named |
| shopping | A store that sends too many promos sees low opt in and users turning alerts off. | None named |
| security | Fake virus warning sites that abused alerts for scams lose permission and show fewer pop ups. | None named |
| games | A browser game portal sends one useful alert for a turn ready, instead of daily nags that cause blocks. | None named |
| social | A social site tests asking after a user follows an account, not at once, to keep its permission rate high. | None named |
| ads | A push ad network sees reduced reach as browsers block spam and remove stale permissions. | None named |
| enterprise | A company dashboard sends few, high value alerts to keep permission across staff browsers. | None named |
Risks
- Hidden prompts
- Real alerts can be missed
What the platform says
- Google Chrome: Quieter notification permissions. Chrome shows a quieter prompt and can auto remove permissions from sites that send unwanted alerts.
Good uses and abuse
Legitimate uses
- Reducing spam for users
Known abuse
- Spammy sites lose access
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2020-02, Chrome 80: Quieter notification permission UI
- 2025, Chrome: Auto-revocation for sites not recently engaged begins rolling out (exact version unconfirmed)
- 2026, Chrome: Chrome Security blog: FCM throttling at 1,000 messages per minute (exact version unconfirmed)
Related capabilities
Related
- Notifications. Can show messages on your screen outside the browser tab, once you tap Allow
- Push API (Web Push). Can send you notifications after you leave, once you allow them
Sources
How well checked: Inferred from related behavior.