> If you ask it for directions, are you going to build your own mapping engine or just use google maps or another third party solution?
(In the following, "server" means computer owned by an outside entity, such as Google or Amazon, and "local" means on a computer owned by you, even if that computer of yours is acting as a server for your other devices)
It doesn't have to be all or nothing.
The maximum privacy leaking method would be to have every direction query handled entirely on the server end, which means you are telling the server the source and destination of every trip you ask directions for.
The maximum practical privacy preserving method would be to download map data for a wide geographical region, and then do all direction calculations locally.
A middle ground would be that when you ask for directions, download map data from the server for the city or county regions necessary for that trip, and do the directions calculations locally, and save the downloaded map data. For subsequent trips, use the saved data, occasionally checking with the server to see if there are updates. Someone snooping at the server will know the first time you ask for directions involving a given city or county, but won't find out where specifically you are going. Depending on how the update checks work, they may also subsequently get an idea of when you make other trips in that area, but again will not get specific origin and destination.
> If you ask for the latest basketball news, are you going to search google or are you going to build your own web crawler?
A couple possibilities to do this.
One is to pull a comprehensive news feed from the server, and then locally filter and sort it.
Another is to use Google to search for sources of basketball news, and then subsequently you get your basketball news directly from those sites.