5 ms·
Is the terrible privacy offender you're referring to Brave, or Cliqz? I'm aware of some somewhat questionable things that Brave has done but I've never heard of
by jordemort 5y ago
Is the terrible privacy offender you're referring to Brave, or Cliqz? I'm aware of some somewhat questionable things that Brave has done but I've never heard of Cliqz before this.
- weinzierl 5y agoCliqz. Regardless of what their marketing copy made you believe they collected the full clickstream of all their browsers users.
- TedDoesntTalk 5y agoThat's not true at all. I worked with Cliqz behind the scenes and know you are incorrect. Think what you want. Everyone at Cliqz was of high integrity and wanted a product that they themselves would be proud to use, as individuals with privacy at the center of their worlds.
- MikusR 5y agoSo Mozilla wasn't sending browsing history to Cliqz?
- gentleman11 5y agoCliqz had a lot of docs at the time about ways to preserve privacy with client side systems that clearly took a lot of developer effort to research. Their reputation is undeserved unless new information came out
- weinzierl 5y agoDo you have a reference to documentation that shows that it was intended that these measures were to taken on the client side? Do you have proof that it was implemented on the client side. I have proof that the users clickstream ended up at Cliqz backend. What happened there is out of my knowledge and I don't care. If you respect my privacy you don't send the data that you claim you don't collect to your backend in the first place.
- gentleman11 5y agoCould you share the proof?
- weinzierl 5y agoSee this old thread: https://news.ycombinator.com/item?id=21677853 https://news.ycombinator.com/item?id=21677853 ...and no, I don't buy the "this ends up at servers we have no shared ownership with" someone wrote in the answers. As I said in other answers here, there are the client binaries out there (and I have them archived). Try them, dump the traffic. Maybe the backend servers don't exist anymore but I'm sure you can work around that.
- jordemort 5y agoThis is not quite the same as sending the whole clickstream, is it? Sending what you type into the URL off somewhere to autocomplete is what pretty much all browsers do out of the box, and it’s been the norm for many years. I’m not saying it’s a good norm, or that Cliqz is good, but this doesn’t seem to be an indicator of them being uniquely bad.
- TedDoesntTalk 5y agoClickstream data was not sent. He's probably referring to telemetry, all of which was sent to proxy servers run by FoxyProxy then forwarded to Cliqz servers (this removed ip addresses of the source).
- weinzierl 5y agoI have archived the old client binaries and I have the pcaps of the traffic they send to backend servers. It is full clickstream data. I stand by my point that Cliqz collected the clickstream of their browsers users. Sue me if I'm wrong.
- postreceipts 5y agoIf you have evidence, post it. Let's see the pcaps.
- wizzwizz4 5y agoDo you have any evidence for this accusation?
- weinzierl 5y agoI have network traffic dumps from the Cliqz browser to their backend servers. They contain the full clickstream.
- wizzwizz4 5y agoOh, the Cliqz browser; thought you meant the search engine. Yeah, that's no secret (https://cliqz.com/en/privacy-browser https://cliqz.com/en/privacy-browser, scroll down to “1) Telemetry”) and you can turn it off in the settings.