browser-core

Thank you for taking the time to read the article and sharing your feedback. Noise is added for what is called plausible deniability. Note that messages themselves do not contain any user-identifier. We take extra measures to strip request headers not needed by the server to avoid extra information that could be used for implicitly linking messages[1]. Possibility of linking messages based on network fingerprinting (ex: IP - which we do not log) still exists and is an open concern which we will solve in the next version. This at most makes it possible for us to learn that these 3 domains are visited by the same person, again - given that the list of domains are from shortlisted top-news domains, it is safe to assume that they do not contain any PII. That said, it is not the strongest model we apply -- due to resource-constrains we have no

Hi, Disclaimer: I work for Cliqz. Thank you the questions, we are always looking for constructive feedback on and off HN. 1. These random values are used for grouping partial queries together, and they reset when you press enter or start a new query. Source code on how it's generated: https://github.com/cliqz-oss/browser-core/blob/master/module... We actually take one additional precaution of using crypto random and not plain Math.random(), which could potentially be used to link multiple sessions together. 2. There is no feature to disable auto-suggest. But I will pass your feedback to the team. 3. No there is no shared ownership, we don't have access to their servers. We also do additional encryption with bucketing on the payload sizes that we route through foxyProxy, so that the proxy provider cannot learn anything about the content of

Sorry you feel that way. In the Cliqz browser you search as you type. To search and serve results we need to know the query. We will have an article on exactly this product in a week or so. We will also be sharing more details on the process on data collection in the blog posts scheduled in the next 3 days. Of course, you don't need to trust what we say, all the code used for collecting data is open-source for transparency and auditing: https://github.com/cliqz-oss/browser-core Lastly, privacy policies are legally binding documents, and we take the law very seriously. We are located in Germany, where privacy laws are as tough as they get (e.g. GDPR was loosely just a re-wording of the existing data protection directive in Germany).

Hi Aorth, Disclaimer: I work for Cliqz. We are aware of this and it's unfortunate, although the lists are not the main ones from community like Easylist, uBlock Origin etc. Cliqz does need to collect data to build it's search engine and other features. Even though we do with by privacy-by-design in mind and without collecting any PII (we will be sharing more details on the process on data collection in the blogposts scheduled for Monday, Tuesday and Wednesday),still we do end up getting on such lists. Of course, you don't need to trust what we say, all the code used for collecting data is open-source for transparency and auditing. Additionally, also happy to help setup network debugging incase you want check what exactly goes out. - https://github.com/cliqz-oss/browser-core We are also willing to discuss with the maintainers of the list a