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