DuckDuckGo prevents search leakage by default.Instead, when you click on a link on our site, we route (redirect) that request in such a way so that it does not send your search terms to other sites. The other siteswillstill know thatyou visited them, but they will not know what search you entered beforehand.
At some other search engines (including us), you can also use an encrypted version (HTTPS), which as a byproduct doesn’t usually send your search terms to sites. However, it is slower to connect to these versions and if you click on a site that also uses HTTPS then yoursearchissent. Nevertheless, the encrypted version does protect your search from being leaked onto the computersittravelson between you and us.
At DuckDuckGo, encrypted version goes even further and automatically changes links from a number of major Web sites to point to the encrypted versions of those sites. It is modeled after (and uses code from) the HTTPS Everywhere FireFox add-on. These sitesinclude Wikipedia, Facebook, Twitter, and Amazon to name a few.
Another way to prevent search leakage is by using something called a POST request, which has the effectof not showing your search in your browser, and, as a consequence, does not send it to othersites.You can turn on POST requests on our settings page, but it has itsown issues. POST requests usually break browser back buttons, and they make it impossible for you to easily share your search by copying and pasting it out ofyourWeb browser’s address bar.