4 ms·

I think you're confusing accessing a public version of their data with accessing their API, which this thread is about. When you use maps.google.com you are NOT

I think you're confusing accessing a public version of their data with accessing their API, which this thread is about. When you use maps.google.com you are NOT agreeing to any terms, because they don't really require any to use their data on their site, but when you use the API, you're required to agree to their terms before being able to use it.

nostrademons 13y ago
FWIW, there's a "Terms" link at the bottom of maps.google.com which links to the additional ToS for Google Maps/Earth: https://www.google.com/intl/en_us/help/terms_maps.html https://www.google.com/intl/en_us/help/terms_maps.html and the first link there is the Google Universal Terms of Service that you also agree to bind yourself to: http://www.google.com/intl/en/policies/terms/ http://www.google.com/intl/en/policies/terms/
- _delirium 13y ago
  In what sense did I "agree to bind [myself]" to those terms? I just loaded a public website that has map tiles on it. You are arguing that I have agreed, thereby, to something written on a different website (two clicks away), which I was neither presented, nor asked to agree to, nor signed an agreement to? It seems very similar in the sense to which Google "agreed" to pay me money if they spider my page more than N times/day, which is what my own website's terms say in the footer. Yet I've never received a check. Is Google playing dumb and claiming they never read the terms, so can't be held liable?
drdaeman 13y ago
Aren't the same exact APIs are serving as backend to that "public version"? If so, looking at whatever data's on your wire (browsers are subclass of user-agents for a reason), and then doing similar requests by example does not make you sign some agreement with Google, right?
- Killswitch 13y ago
  Just because their app consumes their API doesn't mean that the app and it's endusers are subject to the same terms as the API.
- enneff 13y ago
  > Aren't the same exact APIs are serving as backend to that "public version"? Nope.

nostrademons 13y ago

FWIW, there's a "Terms" link at the bottom of maps.google.com which links to the additional ToS for Google Maps/Earth: https://www.google.com/intl/en_us/help/terms_maps.html https://www.google.com/intl/en_us/help/terms_maps.html and the first link there is the Google Universal Terms of Service that you also agree to bind yourself to: http://www.google.com/intl/en/policies/terms/ http://www.google.com/intl/en/policies/terms/

_delirium 13y ago
In what sense did I "agree to bind [myself]" to those terms? I just loaded a public website that has map tiles on it. You are arguing that I have agreed, thereby, to something written on a different website (two clicks away), which I was neither presented, nor asked to agree to, nor signed an agreement to? It seems very similar in the sense to which Google "agreed" to pay me money if they spider my page more than N times/day, which is what my own website's terms say in the footer. Yet I've never received a check. Is Google playing dumb and claiming they never read the terms, so can't be held liable?

drdaeman 13y ago

Aren't the same exact APIs are serving as backend to that "public version"? If so, looking at whatever data's on your wire (browsers are subclass of user-agents for a reason), and then doing similar requests by example does not make you sign some agreement with Google, right?

Killswitch 13y ago
Just because their app consumes their API doesn't mean that the app and it's endusers are subject to the same terms as the API.
enneff 13y ago
> Aren't the same exact APIs are serving as backend to that "public version"? Nope.