Earlier quoted context omitted.
Why not let the user decide what their personal privacy trade-off is? That is, fundamentally, what the original post is about.
Because it adds to the software complexity. several boolean toggles for deciding what to incorporate into the localization algorithm: one toggle for GPS, another for wifi, Bluetooth, cell tower, barometer, etc. and fusing these in all the various combination, testing them, etc. and after doing all that users will mess up their config and then complain that this app sucks not knowing someone on HN had this feature req…
It cannot even be claimed to be an UX improvement since it's creating disruption for everybody that had this feature disabled.
At this point they should have added it to the terms of use and deleted the toggle directly (which I suspect they are going to do down the line, when they can prove that nobody keeps that toggle off).