What happens if someone searches their home address or a place nearby? If it's automatically cached, it could be a data leak. Some sufficiently motivated person can correlate it with someone who connects to Mullvad servers.
(But of course, ideally they would have something in place to prevent such a leak at all, and perhaps they do somehow?)
> 3.4.1 Note Plaintext search queries in cache database
> Assured recommended hashing search terms before insertion / lookup in the cache database. Since search term cache lookups are only performed with exact matching, this should not affect functionality.
> Mullvad: We are now hashing (and salting) the search terms before they are added to Redis
[0] - https://mullvad.net/en/blog/2023/5/16/security-audit-of-our-...
Sure, If I search for "44 little poney street", then the result itself is cached at Mullvad, and someone needs to search himself/herself for "44 little poney street" by entering precisely this search string to access the cached page.
So I don't see a leak with caching... There are leaks anyway: the search term sent to Google, if someone compromises Mullvad, etc... But not one specific with caching and related to other users.