So I think the problem they have with this is that it makes Path look duplicitous.
On the one hand, you've indicated to Path that you're not interested in them making your location public. Maybe from an API standpoint maybe that just means location data off your phone, but from the user's standpoint, in a "use case" sense, it means your location, in any form.
And then Path adheres to that-- because they have too in an API sense-- but then goes right ahead and works out your location differently and uses that.
It reminds me of Airlines who advertise unreasonably cheap tickets and then have a bunch of extra fees and forced insurance which makes the total you have to pay right back up with everyone else. They aren't lying, in a vacuum their tickets are cheaper, but in the real world they aren't.
Path aren't lying either: they are not using your phone's location data off your phone, just like you asked. In the real world though, they're still doing it.
On the one hand, you've indicated to Path that you're not interested in them making your location public. Maybe from an API standpoint maybe that just means location data off your phone, but from the user's standpoint, in a "use case" sense, it means your location, in any form.
And then Path adheres to that-- because they have too in an API sense-- but then goes right ahead and works out your location differently and uses that.
It reminds me of Airlines who advertise unreasonably cheap tickets and then have a bunch of extra fees and forced insurance which makes the total you have to pay right back up with everyone else. They aren't lying, in a vacuum their tickets are cheaper, but in the real world they aren't.
Path aren't lying either: they are not using your phone's location data off your phone, just like you asked. In the real world though, they're still doing it.