A monthly browser review should separate three different things: permission behavior that a user can inspect, a version update that does not by itself establish a privacy-setting change, and a technical fix that is not a new privacy toggle. This guide is designed as a practical review template for an SME or IT administrator. It keeps the browser names, release terms, and technical identifiers used by the supplied vendor sources.
Quick answer
In Edge 152, the browser automatically stops a notification source from sending further notifications when those notifications lead to a page blocked by Microsoft Defender SmartScreen as a scam, phishing, or malware page. Users can review these sites and restore their permissions at edge://settings/privacy/sitePermissions/allPermissions/notifications. Source: Microsoft Edge release notes for the Stable Channel
This is a controlled feature rollout; if it is not visible, check again as the rollout continues. Source: Microsoft Edge release notes for the Stable Channel
Google announced Chrome Stable 152.0.7977.75/.76 for Windows and Mac and 152.0.7977.75 for Linux on September 1, 2026, with rollout over the coming days or weeks. Record this as a version and rollout watch item, not as immediate availability on every device. Source: Google Stable Channel Update for Desktop
The Chrome stable-channel announcement summary does not identify a new privacy toggle. That does not establish a privacy-setting change. Record it only as a release and rollout item. Source: Google Stable Channel Update for Desktop
WebKit documents that Safari 26.6 fixed an issue where partitioned cookies could not be deleted using WKHTTPCookieStore. Record this as a technical fix rather than a new privacy toggle. Source: WebKit Features for Safari 26.6
What to check in Edge 152
Start by recording the Edge version on the devices in scope. Then review notification permissions and record notification sources that Edge stopped or whose permissions were restored after a Microsoft Defender SmartScreen block. This wording describes a specific browser behavior; it does not mean that the user literally changed a subscription state. The documented behavior is that Edge stops the source from sending further notifications when its notifications lead to a page blocked by Microsoft Defender SmartScreen as a scam, phishing, or malware page. Source: Microsoft Edge release notes for the Stable Channel
For a manual review, open the notification-permission path listed above and record the site name, the permission status shown, and whether the source is stopped or its permission was restored. These fields are this article’s editorial review template, not fields required by the source. Do not infer a final outcome from a source being absent; record only what the device shows.
The feature may not appear on every device immediately because it is a controlled rollout. Therefore, one check that does not show it is not enough to record that the feature is permanently absent. That is a recommended review method in this article; the controlled-rollout description comes from Microsoft’s notes. Source: Microsoft Edge release notes for the Stable Channel
How to track Chrome 152
Record the version numbers by operating system: Windows and Mac use 152.0.7977.75/.76, while Linux uses 152.0.7977.75, according to Google’s announcement dated September 1, 2026. The announcement also says that rollout will continue over the coming days or weeks. Source: Google Stable Channel Update for Desktop
As a practical template, use two separate fields: “Is the version present on the device?” and “Is there a documented privacy change?” The first tracks rollout. The second prevents a Chrome Stable update from being confused with a privacy toggle. This separation is an editorial recommendation in this article. The source-backed facts are the version numbers, the announcement date, and the rollout period; the announcement summary does not identify a new privacy toggle. Source: Google Stable Channel Update for Desktop
Do not record a new baseline or a reset of settings merely because the version arrived. That is a documentation safeguard recommended here, not a result established by the Chrome announcement.
How to classify Safari 26.6
For the target Apple devices, verify Safari 26.6 and record that the WKHTTPCookieStore change is a technical fix rather than a new privacy toggle. The documented issue concerns deleting partitioned cookies through WKHTTPCookieStore. Source: WebKit Features for Safari 26.6
Do not turn this item into a claim about a user-facing privacy preference. The appropriate review label is “technical fix.” The wording “rather than a new privacy toggle” follows the supplied source-backed classification of the item. Source: WebKit Features for Safari 26.6
A shared monthly review record
| Browser | Record | Do not infer |
|---|---|---|
| Edge 152 | The browser version, plus notification sources Edge stopped or whose permissions were restored after a Microsoft Defender SmartScreen block. | Do not record this as a literal change in the user’s subscription state. Source |
| Chrome 152 | Version availability by operating system and rollout progress over the coming days or weeks. | Do not record it as a new privacy toggle or as immediate availability on every device. Source |
| Safari 26.6 | Presence on target Apple devices and the WKHTTPCookieStore fix. |
Do not describe it as a new privacy toggle. Source |
A writing rule for the log
Use three fields for each entry: “What happened?”, “What is the evidence?”, and “What does the evidence not establish?” For Edge, document notification-source behavior and the permission path. For Chrome, separate the version number and rollout period from any privacy-setting claim. For Safari, use the technical-fix classification. This structure is a practical recommendation from this article. It helps keep the record within the evidence instead of turning a release note into an unsupported promise or conclusion.