Yes its true, it’s obvious, all your queries will come from the SearXNG server IP and they’ll eventually match to the the information / account / other addresses they already have on you.
I assume that SearXNG as a proxy will not show your real IP address, nor with it show which monitor resolution and which web browser you use, to the search engines that the instance will query.
You buy a VPS that has a static IP to run your private instance. Then search engines will log the VPS IP for every single search query, with a bit of time/data they’ll be able to tie that IP address to your profile. All it takes is for you to open a few websites that use google analytics with your adblocker disabled for some reason and… game over.
I assume that SearXNG as a proxy will not show your real IP address, nor with it show which monitor resolution and which web browser you use, to the search engines that the instance will query.
You buy a VPS that has a static IP to run your private instance. Then search engines will log the VPS IP for every single search query, with a bit of time/data they’ll be able to tie that IP address to your profile. All it takes is for you to open a few websites that use google analytics with your adblocker disabled for some reason and… game over.
I see your point. One solution : run Pi-hole in your local network to block analytics.
I bet google has 200 more ways to cross records and detect whenever you’re proxying your queries.