Since the release of iOS 27.2 beta 2, Safari has included code that can detect banners used by Google to advertise Chrome or its apps, as well as how users respond to them. Apple has not officially documented this feature, and there is no indication it will be included in the final release. This test occurs when Google suggests installing Chrome during a search, a situation that has previously been tolerated by Apple. The iOS 27.2 betas suggest that Safari may now be able to track these interactions, which could have implications for browser competition. According to 9to5Mac, Safari injects a JavaScript script into certain Google home pages and search result pages. This script looks for visible banners or other page elements that encourage users to open or install Chrome or the Google app. However, there is no guarantee that this telemetry—meaning the collection and reporting of measurement data—will be included in the final version of iOS 27.2. The code suggests that Apple is experimenting with ways to measure how often these promotions appear and how users react to them. At this stage, the feature is not mentioned in the iOS 27.2 beta 3 or in the Safari 27.2 version notes. The test takes place during a period of increased regulatory scrutiny of browsers. The reasons for this test remain unclear, but the context is significant. In the United Kingdom, Google has cited its efforts to promote Chrome among iPhone users as evidence that it continues to compete with Safari. Regulators have been examining whether the search agreement between Google and Apple reduces their incentive to compete on browsers. In the European Union, Apple is subject to the Digital Markets Act (DMA), which regulates browser choice and default settings. The European Commission has already investigated whether Safari's choice screen complies with these rules. Two possible interpretations exist: Apple might be collecting these data to strengthen its position or to document its compliance in response to regulatory pressure. For now, no definitive conclusion can be drawn. For users, no action is necessary, but the iOS 27.2 version notes may provide more clarity on whether Apple documents this feature.