> - See how people get to the privacy page from where they enter the site. You don't need a 3rd party to learn the order of pages you served to any given clien

> - See how people get to the privacy page from where they enter the site. You don't need a 3rd party to learn the order of pages you served to any given client. That one is so simple you only need 'grep' and the server log. (aggregation into whatever statistics you want to learn is a trivial exercise left for the reader) > - See how long people are staying on this page. The entire point is that you do not have a right to that information, other than what you can infer from the client later loading another page. Applying technical methods to gain access to private information like this simply makes you the the spy invading people's privacy. Worse, as most people do not understand these technical details, you are a eavesdropper who is preying on ignorance. > so that users come away with a better understanding of privacy. ...while you simultaneously violate the same user's privacy. Do you seriously not understand that you're making the "We had to destroy the village in order to save it" style of ends-justify-the means argument that ignores how you've started to act like that which you are supposedly fighting against. > hovering over Again, the entire point is that you don't get to know that information. That is a perfect example of the type of data the privacy-focused people are trying to protect. We really don't give a damn if that information is useful; if you're recording anything beyond the HTTP requests you receive (the explicit request from the client), then you are the spy and therefore the enemy. If you want to understand how effective your pages are, find another way to deduce that information. This is why traditional businesses pay people to participate in focus groups, to name one example.