|
|
|
|
|
by tschakkaMarc
2392 days ago
|
|
Yes, I’m defending it, because again: We took drastic steps to never send anything private (like checking within the browser whether the URL is unique or different if logged in or out and then never sending it, not to mention that there of course was no identifier and we made record linkage impossible, so no click profile, and much more). If in doubt we drop and don’t send. And again – there were tons of (pen) tests and scrutiny to make sure no private data point ever leaves your browser. It is built with the mindset “if it reaches our server, we should technically not be able to identify any single person or any surf pattern or any private URL” – this was and is also tested by many (privacy) researchers before and after the experiment. And again, all this was and is open source. This is way more than any industry standard, and I simply don’t know of any company that works with data that has a higher standard. Be our guest to validate it yourself. And please read our blog post Tuesday: we will explain how this is done. But if you simply oppose this (and similar methods from people who really care about privacy), you basically accept the status-quo of the worst data collectors, because no one else then will ever emerge (because you do need this kind of data to build a search). [EDIT]: Just to clarify and not have anyone create the wrong idea - I defend my earlier point. But your question is loaded. Here's why: We do not collect browser history, which by definition implies being able to piece visited urls back to a profile in our servers. That is impossible - to us, each single URL comes as a detached datapoint - devoid of any information that can be used to aggregate them back to a user profile. |
|
>That is impossible - to us, each single URL comes as a detached datapoint
IPs could be used to aggregate those datapoints, and you obviously cannot avoid receiving these. It is only promises that you or your proxy provider doesn't store them. (though maybe it is possible to implement P2P mangling network? encrypt UDP data packet, send to randomly selected peer discovered from DHT, peer delivers it to your server. Or directly send UDP packet with spoofed source address, but this is not possible for browser sitting behind NAT)