The important distinction is between browsing privately and checking threats promptly. Google’s documentation confirms that Incognito can use locally stored threat information instead of the online lookup used in other circumstances. The proposed work would narrow that gap.
What real-time checks would change
According to Google’s desktop documentation, Standard Protection first checks a destination against a locally stored list of known-safe sites. If a lookup is needed, Chrome can send an obfuscated portion of the address through a privacy server to check Google’s threat information. Incognito browsing and failed privacy-server requests are among the circumstances in which Chrome instead checks its locally stored unsafe-site list.
That does not mean Incognito currently has no phishing or malware protection. Google also documents security checks triggered by suspicious behavior, while noting that some protections are disabled in Incognito to avoid revealing additional information. “No real-time lookup in some situations” is not the same as “no protection.”
If the reported change ships, its practical value would be fresher threat information during private sessions. A newly identified phishing page could potentially trigger a warning before the device’s local threat data catches up. That is the expected benefit of the proposed design, not a measured result from testing.
Windows Report says Guest mode is included alongside Incognito. Google’s existing fallback documentation specifically names Incognito; it should not be read as independent confirmation of Guest mode’s current lookup behavior.
Privacy involves more than keeping data off disk
Windows Report describes one privacy safeguard in the development work: temporary security-key updates triggered during an Incognito session would stay in memory rather than being saved to disk. That is a specific implementation claim—not a guarantee that every security-related operation leaves no local trace.
There is also a separate question: what information leaves the browser?
Google says Standard Protection’s routine online checks use privacy servers to separate the user’s IP address from the destination information. Enhanced Protection shares more security information, including URLs and samples of page content, extension activity, and system information. Those are descriptions of the existing protection levels, not proof of exactly which data the proposed private-session feature would transmit.
The distinction matters. Keeping temporary information in memory addresses local persistence; it does not, by itself, explain network data handling.
Incognito and Guest still are not anonymity tools
Google defines Incognito primarily around limiting what Chrome retains on the device. After all Incognito windows close, Chrome removes the session’s site data and does not retain its browsing history. Downloaded files and saved bookmarks remain, however, and websites, employers, schools, and internet providers may still observe activity. The hat-and-glasses icon is not an invisibility cloak.
Guest mode similarly separates browsing from other Chrome profiles and deletes its browsing history, cookies, and site data when the session closes. Google nevertheless advises signing into sensitive websites only on trusted devices: the device owner or network operator may still have visibility. Better malicious-site detection would not remove those limits.
What Windows users can do now
There is no verified release milestone or activation procedure for the proposed feature. Windows Report describes an experimental flag, but its report does not establish a Chrome version in which ordinary users should expect the change.
For existing protection, Google documents this desktop settings path:
- Open Chrome’s three-dot menu and select Settings.
- Select Privacy and security, then Security.
- Under Safe Browsing, review the selected protection level.
Standard Protection is the default. Enhanced Protection adds safeguards against known and potentially new threats, with additional information sharing. Seeing the chosen level here confirms the current setting; it does not confirm access to the experimental Incognito or Guest change.
The proposal is worth watching because private browsing should not require unnecessarily stale threat intelligence. For now, though, the sensible reading is modest: Google is reportedly working toward more consistent Safe Browsing coverage, while the release timing and precise private-session implementation remain unsettled.