own-instance.html 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202
  1. <!DOCTYPE html>
  2. <html lang="en" data-content_root="./">
  3. <head>
  4. <meta charset="utf-8" />
  5. <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  6. <meta name="viewport" content="width=device-width, initial-scale=1">
  7. <title>Why use a private instance? &#8212; SearXNG Documentation (2025.4.30+fd33559cf)</title>
  8. <link rel="stylesheet" type="text/css" href="_static/pygments.css?v=6625fa76" />
  9. <link rel="stylesheet" type="text/css" href="_static/searxng.css?v=52e4ff28" />
  10. <script src="_static/documentation_options.js?v=b12b0e12"></script>
  11. <script src="_static/doctools.js?v=9a2dae69"></script>
  12. <script src="_static/sphinx_highlight.js?v=dc90522c"></script>
  13. <script data-project="searxng" data-version="2025.4.30+fd33559cf" src="_static/describe_version.js?v=fa7f30d0"></script>
  14. <link rel="index" title="Index" href="genindex.html" />
  15. <link rel="search" title="Search" href="search.html" />
  16. <link rel="next" title="Administrator documentation" href="admin/index.html" />
  17. <link rel="prev" title="About SearXNG" href="user/about.html" />
  18. </head><body>
  19. <div class="related" role="navigation" aria-label="Related">
  20. <h3>Navigation</h3>
  21. <ul>
  22. <li class="right" style="margin-right: 10px">
  23. <a href="genindex.html" title="General Index"
  24. accesskey="I">index</a></li>
  25. <li class="right" >
  26. <a href="py-modindex.html" title="Python Module Index"
  27. >modules</a> |</li>
  28. <li class="right" >
  29. <a href="admin/index.html" title="Administrator documentation"
  30. accesskey="N">next</a> |</li>
  31. <li class="right" >
  32. <a href="user/about.html" title="About SearXNG"
  33. accesskey="P">previous</a> |</li>
  34. <li class="nav-item nav-item-0"><a href="index.html">SearXNG Documentation (2025.4.30+fd33559cf)</a> &#187;</li>
  35. <li class="nav-item nav-item-this"><a href="">Why use a private instance?</a></li>
  36. </ul>
  37. </div>
  38. <div class="document">
  39. <div class="documentwrapper">
  40. <div class="bodywrapper">
  41. <div class="body" role="main">
  42. <section id="why-use-a-private-instance">
  43. <h1>Why use a private instance?<a class="headerlink" href="#why-use-a-private-instance" title="Link to this heading">¶</a></h1>
  44. <aside class="sidebar">
  45. <p class="sidebar-title">Is running my own instance worth it?</p>
  46. <p>...is a common question among SearXNG users. Before answering this
  47. question, see what options a SearXNG user has.</p>
  48. </aside>
  49. <nav class="contents local" id="contents">
  50. <ul class="simple">
  51. <li><p><a class="reference internal" href="#how-does-searxng-protect-privacy" id="id1">How does SearXNG protect privacy?</a></p>
  52. <ul>
  53. <li><p><a class="reference internal" href="#what-are-the-consequences-of-using-public-instances" id="id2">What are the consequences of using public instances?</a></p></li>
  54. <li><p><a class="reference internal" href="#i-see-what-about-private-instances" id="id3">I see. What about private instances?</a></p></li>
  55. </ul>
  56. </li>
  57. <li><p><a class="reference internal" href="#conclusion" id="id4">Conclusion</a></p></li>
  58. </ul>
  59. </nav>
  60. <p>Public instances are open to everyone who has access to their URL. Usually, they
  61. are operated by unknown parties (from the users’ point of view). Private
  62. instances can be used by a select group of people, such as a SearXNG instance for a
  63. group of friends, or a company which can be accessed through a VPN. Instances can also be
  64. single-user instances, which run locally on the user’s machine.</p>
  65. <p>To gain more insight on how these instances work, let’s dive into how SearXNG
  66. protects its users.</p>
  67. <section id="how-does-searxng-protect-privacy">
  68. <span id="searxng-protect-privacy"></span><h2><a class="toc-backref" href="#id1" role="doc-backlink">How does SearXNG protect privacy?</a><a class="headerlink" href="#how-does-searxng-protect-privacy" title="Link to this heading">¶</a></h2>
  69. <p>SearXNG protects the privacy of its users in multiple ways, regardless of the type
  70. of the instance (private or public). Removal of private data from search requests
  71. comes in three forms:</p>
  72. <blockquote>
  73. <div><ol class="arabic simple">
  74. <li><p>Removing private data from requests going to search services</p></li>
  75. <li><p>Not forwarding anything from third party services through search services
  76. (e.g. advertisement)</p></li>
  77. <li><p>Removing private data from requests going to the results pages</p></li>
  78. </ol>
  79. </div></blockquote>
  80. <p>Removing private data means not sending cookies to external search engines and
  81. generating a random browser profile for every request. Thus, it does not matter
  82. if a public or private instance handles the request, because it is anonymized in
  83. both cases. The IP address used will be the IP of the instance, but SearXNG can also be
  84. configured to use proxy or Tor. <a class="reference external" href="https://github.com/asciimoo/morty">Result proxy</a> is supported, too.</p>
  85. <p>SearXNG does not serve ads or tracking content, unlike most search services. Therefore,
  86. private data is not forwarded to third parties who might monetize it. Besides
  87. protecting users from search services, both the referring page and search query are
  88. hidden from the results pages being visited.</p>
  89. <section id="what-are-the-consequences-of-using-public-instances">
  90. <h3><a class="toc-backref" href="#id2" role="doc-backlink">What are the consequences of using public instances?</a><a class="headerlink" href="#what-are-the-consequences-of-using-public-instances" title="Link to this heading">¶</a></h3>
  91. <p>If someone uses a public instance, they have to trust the administrator of that
  92. instance. This means that the user of the public instance does not know whether
  93. their requests are logged, aggregated, and sent or sold to a third party.</p>
  94. <p>Also, public instances without proper protection are more vulnerable to abuse of
  95. the search service, which may cause the external service to enforce
  96. CAPTCHAs or to ban the IP address of the instance. Thus, search requests would return less
  97. results.</p>
  98. </section>
  99. <section id="i-see-what-about-private-instances">
  100. <h3><a class="toc-backref" href="#id3" role="doc-backlink">I see. What about private instances?</a><a class="headerlink" href="#i-see-what-about-private-instances" title="Link to this heading">¶</a></h3>
  101. <p>If users run their <a class="reference internal" href="admin/installation.html#installation"><span class="std std-ref">own instances</span></a>, everything is in their
  102. control: the source code, logging settings and private data. Unknown instance
  103. administrators do not have to be trusted.</p>
  104. <p>Furthermore, as the default settings of their instance are editable, there is no
  105. need to use cookies to tailor SearXNG to their needs and preferences will not
  106. reset to defaults when clearing browser cookies. As settings are stored on
  107. the user’s computer, they will not be accessible to others as long as their computer is
  108. not compromised.</p>
  109. </section>
  110. </section>
  111. <section id="conclusion">
  112. <h2><a class="toc-backref" href="#id4" role="doc-backlink">Conclusion</a><a class="headerlink" href="#conclusion" title="Link to this heading">¶</a></h2>
  113. <p>Always use an instance which is operated by people you trust. The privacy
  114. features of SearXNG are available to users no matter what kind of instance they
  115. use.</p>
  116. <p>For those on the go, or just wanting to try SearXNG for the first time, public
  117. instances are the best choice. Public instances are also making the
  118. world a better place by giving those who cannot, or do not want to, run an
  119. instance access to a privacy-respecting search service.</p>
  120. </section>
  121. </section>
  122. <div class="clearer"></div>
  123. </div>
  124. </div>
  125. </div>
  126. <span id="sidebar-top"></span>
  127. <div class="sphinxsidebar" role="navigation" aria-label="Main">
  128. <div class="sphinxsidebarwrapper">
  129. <p class="logo"><a href="index.html">
  130. <img class="logo" src="_static/searxng-wordmark.svg" alt="Logo of SearXNG"/>
  131. </a></p>
  132. <h3><a href="index.html">Table of Contents</a></h3>
  133. <ul class="current">
  134. <li class="toctree-l1"><a class="reference internal" href="user/index.html">User information</a></li>
  135. <li class="toctree-l1 current"><a class="current reference internal" href="#">Why use a private instance?</a><ul>
  136. <li class="toctree-l2"><a class="reference internal" href="#how-does-searxng-protect-privacy">How does SearXNG protect privacy?</a><ul>
  137. <li class="toctree-l3"><a class="reference internal" href="#what-are-the-consequences-of-using-public-instances">What are the consequences of using public instances?</a></li>
  138. <li class="toctree-l3"><a class="reference internal" href="#i-see-what-about-private-instances">I see. What about private instances?</a></li>
  139. </ul>
  140. </li>
  141. <li class="toctree-l2"><a class="reference internal" href="#conclusion">Conclusion</a></li>
  142. </ul>
  143. </li>
  144. <li class="toctree-l1"><a class="reference internal" href="admin/index.html">Administrator documentation</a></li>
  145. <li class="toctree-l1"><a class="reference internal" href="dev/index.html">Developer documentation</a></li>
  146. <li class="toctree-l1"><a class="reference internal" href="utils/index.html">DevOps tooling box</a></li>
  147. <li class="toctree-l1"><a class="reference internal" href="src/index.html">Source-Code</a></li>
  148. </ul>
  149. <h3>Project Links</h3>
  150. <ul>
  151. <li><a href="https://github.com/searxng/searxng/tree/master">Source</a>
  152. <li><a href="https://github.com/searxng/searxng/wiki">Wiki</a>
  153. <li><a href="https://searx.space">Public instances</a>
  154. <li><a href="https://github.com/searxng/searxng/issues">Issue Tracker</a>
  155. </ul><h3>Navigation</h3>
  156. <ul>
  157. <li><a href="index.html">Overview</a>
  158. <ul>
  159. <li>Previous: <a href="user/about.html" title="previous chapter">About SearXNG</a>
  160. <li>Next: <a href="admin/index.html" title="next chapter">Administrator documentation</a>
  161. </ul>
  162. </li>
  163. </ul>
  164. <search id="searchbox" style="display: none" role="search">
  165. <h3 id="searchlabel">Quick search</h3>
  166. <div class="searchformwrapper">
  167. <form class="search" action="search.html" method="get">
  168. <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
  169. <input type="submit" value="Go" />
  170. </form>
  171. </div>
  172. </search>
  173. <script>document.getElementById('searchbox').style.display = "block"</script>
  174. <div role="note" aria-label="source link">
  175. <h3>This Page</h3>
  176. <ul class="this-page-menu">
  177. <li><a href="_sources/own-instance.rst.txt"
  178. rel="nofollow">Show Source</a></li>
  179. </ul>
  180. </div>
  181. </div>
  182. </div>
  183. <div class="clearer"></div>
  184. </div>
  185. <div class="footer" role="contentinfo">
  186. &#169; Copyright SearXNG team.
  187. </div>
  188. </body>
  189. </html>