Earlier quoted context omitted.
This seems pretty reasonable to me, although perhaps they named the switch poorly. My guess is that the product manager is trying to provide a single simple "privacy fiend" setting. You apparently want fine-grained privacy controls ("save my personal locations, but not my search history"). It's reasonable to want that, but it seems awfully entitled (not you, but many others on this thread) to demand it. Especially si…
This is disingenuous and unreasonable. The setting is unnecessarily restrictive. It's simple: "Do you want us to store your data on our servers?" Answering "no" should mean you store it locally, not that you don't store it at all. If you tell Google not to save your search history on their servers, they just disable it completely, when they could just save it locally. This is nowhere near a product problem. The setti…
I think you are ridiculously underestimating the complexity and issues that would arise with two separate mechanisms for saving the same kind of data, and an option to switch between the two. Do you download account-saved locations locally when changing to local storage? What if there are conflicting pieces of data?
I bet there would be a lot more outraged people about the bugs and limitations that would arise with this system than there are today with your complaints.