At launch, access to Mullvad Leta was restricted to users with a paid Mullvad VPN account, but it is now free and open to all.
Mullvad Leta has been audited by Assured.
Just a heads up, some of the details in the FAQ and Terms of Service seem a bit outdated and might not be accurate anymore.
Some relevant information from their FAQ section is as follows:
What can I do with Leta?
Leta is a search engine. You can use it to return search results from many locations. We provide text search results, currently we do not offer image, news or any other types of search result. Leta acts as a proxy to Google and Brave search results. You can select which backend search engine you wish to use from the homepage of Leta.
Can I use Leta as my default search engine?
Yes, so long as your browser supports changing default search engines.
Navigate to https://leta.mullvad.net/ in your browser and right-click on the URL bar.
From there you should see Add “Mullvad Leta“ with the Mullvad VPN logo to the left.
If you do not see this, you can attempt to add a custom search engine to your browser with:
- The name set to: Leta
- The URL set to: https://leta.mullvad.net/?q=%25s
You can select which backend engine to use as follows:
- Google: https://leta.mullvad.net/?q=%25s&engine=google
- Brave: https://leta.mullvad.net/?q=%25s&engine=brave
Did you make your own search engine from scratch?
We did not, we made a front end to the Google and Brave Search APIs.
Our search engine performs the searches on behalf of our users. This means that rather than using Google or Brave Search directly, our Leta server makes the requests.
Searching by proxy in other words.
What is the point of Leta?
Leta aims to present a reliable and trustworthy way of searching privately on the internet.
However, Leta is useless as a service if you use the perfect non-logging VPN, a privacy focussed DNS service, a web browser that resists fingerprinting, and correlation attacks from global actors. Leta is also useless if your browser blocks all cookies, tracking pixels and other tracking technologies.
For most people Leta can be useful, as the above conditions cannot ever truly be met by systems that are available today.
What is a cached search?
We store every search in a RAM based cache storage (Redis), which is removed after it reaches over 30 days in age.
Cached searches are fetched from this storage, which means we return a result that can be from 0 to 30 days old. It may be the case that no other user has searched for something during the time that you search, which means you would be shown a stale result.
What happens to everything I search for?
Your searches are performed by proxy, it is the Leta server that makes calls to the Google or Brave Search API.
Each search that has not already been cached is saved in RAM for 30 days. The idea is that the more searches performed, the larger and more substantial the cached results become, therefore aiding with privacy.
All searches will be stored hashed with a secret in a cache. When you perform a search the cache will be checked first, before determining whether a direct call to Google or Brave Search should be made. Each time the Leta application is restarted (due to an upgrade, or new version) server side, a new secret hash is generated, meaning that all previous search queries are no longer visible to Leta
What could potentially be a unique search would become something that many other users would also search for.
What is running on the server side?
We run the Leta servers on STBooted RAM only servers, the same as our VPN servers. These servers run the latest Ubuntu LTS, with our own stripped down custom Mullvad VPN kernel which we tune in-house to remove anything unnecessary for the running system.
The cached search results are stored in an in-memory Redis key / value store.
The Leta service is a NodeJS based application that proxies requests to Google or Brave Search, or returns them from cache.
We gather metrics relating to the number of cached searches, vs direct searches, solely to understand the value of our service.
Additionally we gather information about CPU usage, RAM usage and other such information to keep the service running smoothly.
Not a search engine.
Ehhh. I mean, technically yes, but a proxy for search engine requests is probably functionally equivalent to the end user.
Also, if users don’t know that such a thing exists and goes looking for a “search engine”, they likely also want this.
One of my personal pet peeves is power stations — a big lithium-ion battery pack hooked up to a charge controller and inverter and USB power supply and with points to attach solar panels — being called a “solar generator”. It’s not a generator, doesn’t use mechanical energy. But…a lot of people who think “I need electricity in an outage” just go searching for “generator”. I don’t like the practice, but I think that the aim is less to deceive users and more to try to deal with the fact that they functionally act in much the same role and people might not otherwise think of them.
I am less sympathetic to vendors who do the same with calling evaporative coolers “air conditioners”. Those have some level of overlap in use, but are substantially different devices in price and capability.
It’s like saying a passenger rail car is a freight engine
I think it’s more like a travel agent and a passenger rail
I think they just call them trains
Is it really though? To the common person, it is most important thinking about the intent rather than what the word literally means. Like what people think of as AI may really just be a LLM, or VR may really be AR, or the like.
I get what you’re saying, but in that case the google.com interface isn’t a search engine; nor the load balancers and proxies between it and the search application backend. And then, maybe those don’t count because there is some special sauce in database procedures that are the real workhorses.
Pedantry all the way down.