What does Microsoft want with their users’ complete browsing history? Users unknowingly helping to crowd‐source better search for Microsoft by using feature intended to speed up browsing.
What is flip‐ahead browsing and prerendering?
Given good network conditions, Internet Explorer will look for the next page the user is likely to visit. The page deemed to be the next relevant page will be automatically downloaded in the background. The user can then click‐through to it using normal links, the Back and Forward buttons, or with a three‐finger swiping touch‐gesture to navigate to it without having to wait for loading.
The next and previous pages are determined by browser history (the previously visited page) with some additional hints provided by the page. Browsers looks for
<link rel="next" href="this-comes-next.html"> and
<link rel="prerender" href="this-comes-next.html"> to determine what to preload.  Note the use of the non‐standard “prerender” relation instead of the standardized “prefetch” which has a slightly different meaning.
Unique to Internet Explorer, patterns for what the next page is likely to be can also be found through hints in the Compatibility View Lists that are periodically downloaded. Other browsers only rely on the information from the websites themselves.
Flip‐ahead is enabled by default with “Express Setup” (default) or pre‐checked with “Custom Setup”. In other words, it is enabled for almost all of Internet Explorer’s users.
Users of the Opera browser based on the Presto engine may recognize how Flip‐ahead browsing works from Opera’s now discontinued Fast‐Forward and Rewind features.
Hidden cost of the feature
There most frequently criticized part of preloading is the potentially wasted bandwidth and resources on both the client and server‐side. Users may not always want to see the next page. Putting that aside, there is another cost of preloading in Internet Explorer that users of other browsers do not have to pay.
Your entire browsing history will periodically be sent to Microsoft. The data sent includes all addresses you visit and when you visited them (derived from that is also how long you spent on each page), and the address of the page that referred you to each page. Each addresses is filtered to remove query parameters, which is to say anything after a question mark in the address. However, this measurement has little effect in terms of privacy. Microsoft can still see that the user spent 20 minutes reading the Wikipedia article on genital herpes after spending hours the previous day on a promiscuous dating site. This metadata tells the entire story even without the query parameters.
Building a better search engine not a better browser
The flip‐ahead feature does not exist on Internet Explorer Mobile (part of Windows Phone). Instead, there is a unambiguous option to submit all browsing history to Microsoft. Internet Explorer Mobile 10 stated explicitly that as part of this data, it would collect the full browsing history and use it to improve the Bing service. For Internet Explorer Mobile 11, this language has been changed to say the collected data will be used to improve Microsoft products and services without mentioning Bing specifically. Regardless of the generalized lingo, it is pretty clear which Microsoft service will benefit the most from data about what pages its users spend the most time on and find the most popular.
I do not mind the approach Microsoft have taken for Internet Explorer Mobile. It is clear what the option does and it is not tied in with another desirable feature. I am a bit less happy about how they have done it by trying to hide it behind an innocent looking option in the desktop version.
I mostly take issue with Microsoft’s decision to turn these privacy‐invading options on by default on both platforms. It is nothing less than consumers should expect these days with everyone’s rush to get into “big‐data” and justification from tyranny of the default. I understand that Microsoft need the data to expand and catch up to its competitors’ enormous head‐start in the search business. However, I still believe these should be opt‐in rather than opt‐out.
-  ’Features that use Microsoft online services: Flip‐ahead with page prediction’ in the Internet Explorer 11 privacy statement
-  MSDN documentation for implementing Prerender and prefetch support
-  MSDN documentation for implementing Flip ahead browsing
-  ‘Web browsing features that store data: Compatibility List Updates’ in the Internet Explorer 11 privacy statement
-  ‘Favorites and Browsing History’ in the Windows Phone 8 Privacy Statement
-  ‘Favorites and browsing history’ in the Windows Phone 8.1 Privacy Statement