>"Whether the request uses GET or POST to send the form data to the server is irrelevant. The browser (IE is the browser, remember? IT is the one receiving, rendering, inputting, and sending the data) knows what data is part of a link with an embedded query string and which data is form data being submitted. Therefor, the browser can quite easily choose to NOT send the form data as part of the URL when submitting it to Microsoft, while still including that form data as part of the URL was submitting the request to the request host. "
Yes, it could. But as the press release made clear, it doesn't, which is why they warn you that your data /could/ under some circumstances be sent. Duh.
You've also misunderstood me. I am not referring to the method used by the browser to submit data to the MS recommendation service. I am referring to the method used by the browser to submit a form on a third-party website, which, if it is GET will end up generating a URL containing the query parameters, and if it is POST, will generate a URL that does not contain the parameters, that URL then being sent to the recommendation service as with any other URL the browser fetches. Also, your concepts are muddled in this passage:
>" ... data is part of a link with an embedded query string and which data is form data being submitted ... "
Form data being submitted can be submitted either by an embedded query string in the URL of a GET request, or by being sent as the *BODY* of a POST request. To those skilled in the art, it is entirely plain that what the FAQ was saying is that URLs are sent to the recommendation service but never body data. Attempting to spin it to sound like some kind of tricky technical/legal loophole that MS intend to exploit to steal your form data is just conspiracy mongering.