That's ... honestly a bit disappointing. While I personally believe that the leaking of military location data is almost entirely the military's problem/fault,

That's ... honestly a bit disappointing. While I personally believe that the leaking of military location data is almost entirely the military's problem/fault, I feel that this could have been avoided with a minimal bit of forethought by the Strava team. It's not their job to protect military secrets or keep track if some of the data that's sent to them may be connected to a military secret or not. They are, however, responsible for the individual privacy of their own users/customers. I am reminded of the Dutch "first name database". It's a neat little website showing data (collected by the government/administrative/statistics dept). You can look up any first name in the Netherlands (17M ppl, FYI) and see how many people share this name. You can also see historical data how usage of the first name tracks through time. AND, this is the crucial bit, you can also see a nice heat map of the geographical distribution for this first name, per municipality. HOWEVER, and this is where it gets relevant to Strava. They simply won't show the geographical distribution heat map for names that are very rare. If a first name is not nationally rare, but it is in a certain municipality, they will also round it down to zero. Finally, if there's only 5 or less people in NL with that name they won't even show the full total (regardless of location). Strava could, and IMHO should have done that for regions where only a single (or just a few) individual accounts run a track.