This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<liclass="nav-item nav-item-this"><ahref="">Why use a private instance?</a></li>
</ul>
</div>
<divclass="document">
<divclass="documentwrapper">
<divclass="bodywrapper">
<divclass="body"role="main">
<sectionid="why-use-a-private-instance">
<h1>Why use a private instance?<aclass="headerlink"href="#why-use-a-private-instance"title="Link to this heading">¶</a></h1>
<asideclass="sidebar">
<pclass="sidebar-title">Is running my own instance worth it?</p>
<p>...is a common question among SearXNG users. Before answering this
question, see what options a SearXNG user has.</p>
</aside>
<navclass="contents local"id="contents">
<ulclass="simple">
<li><p><aclass="reference internal"href="#how-does-searxng-protect-privacy"id="id1">How does SearXNG protect privacy?</a></p>
<ul>
<li><p><aclass="reference internal"href="#what-are-the-consequences-of-using-public-instances"id="id2">What are the consequences of using public instances?</a></p></li>
<li><p><aclass="reference internal"href="#i-see-what-about-private-instances"id="id3">I see. What about private instances?</a></p></li>
<p>Public instances are open to everyone who has access to their URL. Usually, they
are operated by unknown parties (from the users’ point of view). Private
instances can be used by a select group of people, such as a SearXNG instance for a
group of friends, or a company which can be accessed through a VPN. Instances can also be
single-user instances, which run locally on the user’s machine.</p>
<p>To gain more insight on how these instances work, let’s dive into how SearXNG
protects its users.</p>
<sectionid="how-does-searxng-protect-privacy">
<spanid="searxng-protect-privacy"></span><h2><aclass="toc-backref"href="#id1"role="doc-backlink">How does SearXNG protect privacy?</a><aclass="headerlink"href="#how-does-searxng-protect-privacy"title="Link to this heading">¶</a></h2>
<p>SearXNG protects the privacy of its users in multiple ways, regardless of the type
of the instance (private or public). Removal of private data from search requests
comes in three forms:</p>
<blockquote>
<div><olclass="arabic simple">
<li><p>Removing private data from requests going to search services</p></li>
<li><p>Not forwarding anything from third party services through search services
(e.g. advertisement)</p></li>
<li><p>Removing private data from requests going to the results pages</p></li>
</ol>
</div></blockquote>
<p>Removing private data means not sending cookies to external search engines and
generating a random browser profile for every request. Thus, it does not matter
if a public or private instance handles the request, because it is anonymized in
both cases. The IP address used will be the IP of the instance, but SearXNG can also be
configured to use proxy or Tor. <aclass="reference external"href="https://github.com/asciimoo/morty">Result proxy</a> is supported, too.</p>
<p>SearXNG does not serve ads or tracking content, unlike most search services. Therefore,
private data is not forwarded to third parties who might monetize it. Besides
protecting users from search services, both the referring page and search query are
<h3><aclass="toc-backref"href="#id2"role="doc-backlink">What are the consequences of using public instances?</a><aclass="headerlink"href="#what-are-the-consequences-of-using-public-instances"title="Link to this heading">¶</a></h3>
<p>If someone uses a public instance, they have to trust the administrator of that
instance. This means that the user of the public instance does not know whether
their requests are logged, aggregated, and sent or sold to a third party.</p>
<p>Also, public instances without proper protection are more vulnerable to abuse of
the search service, which may cause the external service to enforce
CAPTCHAs or to ban the IP address of the instance. Thus, search requests would return less
results.</p>
</section>
<sectionid="i-see-what-about-private-instances">
<h3><aclass="toc-backref"href="#id3"role="doc-backlink">I see. What about private instances?</a><aclass="headerlink"href="#i-see-what-about-private-instances"title="Link to this heading">¶</a></h3>
<p>If users run their <aclass="reference internal"href="admin/installation.html#installation"><spanclass="std std-ref">own instances</span></a>, everything is in their
control: the source code, logging settings and private data. Unknown instance
administrators do not have to be trusted.</p>
<p>Furthermore, as the default settings of their instance are editable, there is no
need to use cookies to tailor SearXNG to their needs and preferences will not
reset to defaults when clearing browser cookies. As settings are stored on
the user’s computer, they will not be accessible to others as long as their computer is
not compromised.</p>
</section>
</section>
<sectionid="conclusion">
<h2><aclass="toc-backref"href="#id4"role="doc-backlink">Conclusion</a><aclass="headerlink"href="#conclusion"title="Link to this heading">¶</a></h2>
<p>Always use an instance which is operated by people you trust. The privacy
features of SearXNG are available to users no matter what kind of instance they
use.</p>
<p>For those on the go, or just wanting to try SearXNG for the first time, public
instances are the best choice. Public instances are also making the
world a better place by giving those who cannot, or do not want to, run an
instance access to a privacy-respecting search service.</p>
<liclass="toctree-l1 current"><aclass="current reference internal"href="#">Why use a private instance?</a><ul>
<liclass="toctree-l2"><aclass="reference internal"href="#how-does-searxng-protect-privacy">How does SearXNG protect privacy?</a><ul>
<liclass="toctree-l3"><aclass="reference internal"href="#what-are-the-consequences-of-using-public-instances">What are the consequences of using public instances?</a></li>
<liclass="toctree-l3"><aclass="reference internal"href="#i-see-what-about-private-instances">I see. What about private instances?</a></li>