git.iko.soy/searx
on master help sign in
searx/docs/user/own-instance.rst
79 lines 3.6 kB history raw
1===========================
2Why use a private instance?
3===========================
5 *"Is it worth to run my own instance?"*
7\.\. is a common question among searx users. Before answering this question,
8see what options a searx user has.
10Public instances are open to everyone who has access to its URL. Usually, these
11are operated by unknown parties (from the users' point of view). Private
12instances can be used by a select group of people. It is for example a searx of
13group of friends or a company which can be accessed through VPN. Also it can be
14single user one which runs on the user's laptop.
16To gain more insight on how these instances work let's dive into how searx
17protects its users.
19How does searx protect privacy?
20===============================
22Searx protects the privacy of its users in multiple ways regardless of the type
23of the instance (private, public). Removal of private data from search requests
24comes in three forms:
26 1. removal of private data from requests going to search services
27 2. not forwarding anything from a third party services through search services
28 (e.g. advertisement)
29 3. removal of private data from requests going to the result pages
31Removing private data means not sending cookies to external search engines and
32generating a random browser profile for every request. Thus, it does not matter
33if a public or private instance handles the request, because it is anonymized in
34both cases. IP addresses will be the IP of the instance. But searx can be
35configured to use proxy or Tor. `Result proxy
36<https://github.com/asciimoo/morty>`__ is supported, too.
38Searx does not serve ads or tracking content unlike most search services. So
39private data is not forwarded to third parties who might monetize it. Besides
40protecting users from search services, both referring page and search query are
41hidden from visited result pages.
44What are the consequences of using public instances?
45----------------------------------------------------
47If someone uses a public instance, they have to trust the administrator of that
48instance. This means that the user of the public instance does not know whether
49their requests are logged, aggregated and sent or sold to a third party.
51Also, public instances without proper protection are more vulnerable to abusing
52the search service, In this case the external service in exchange returns
53CAPTCHAs or bans the IP of the instance. Thus, search requests return less
54results.
56I see. What about private instances?
57------------------------------------
59If users run their :ref:`own instances <installation>`, everything is in their
60control: the source code, logging settings and private data. Unknown instance
61administrators do not have to be trusted.
63Furthermore, as the default settings of their instance is editable, there is no
64need to use cookies to tailor searx to their needs. So preferences will not be
65reset to defaults when clearing browser cookies. As settings are stored on
66their computer, it will not be accessible to others as long as their computer is
67not compromised.
69Conclusion
70==========
72Always use an instance which is operated by people you trust. The privacy
73features of searx are available to users no matter what kind of instance they
74use.
76If someone is on the go or just wants to try searx for the first time public
77instances are the best choices. Additionally, public instance are making a
78world a better place, because those who cannot or do not want to run an
79instance, have access to a privacy respecting search service.