On Oct 12, 8:56 am, Pavel Janíček <[email protected]> wrote: > Hi, > your assumption seems correct to me, but also leads to conclusion i > think that they are against ToS > > I will try to rephrase what i THINK "freely accessible" means to me
Actually 10.4 of the Terms seems quite explicit: You must not... 10.4 charge users or any other third party any fee for the use of the Maps API Implementation, the Service, or the Content... Note: there must be no charge for the **use** of the Maps API implementation. So it's not acceptable for anyone to have to pay a fee to get a login to use the map. However, the terms do not say that access to *your* data needs to be free (your data is not "Content", that's Google's map tiles and search result data); nor that access to facilities like being able to save data needs to be free. That's access to your services, not Google's, and it costs you money to maintain a database. Consequently a "Save this place" option in an infoWindow might return a 403 Forbidden error to the client if an authentication cookie wasn't present in the request. If that authentication was successful, the response could be 200 OK because the data has been saved. The client code needs to handle what is returned from the server, and the same client code needs to be available to everyone. This post represents my opinion and nothing here should be construed as definitive legal advice. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
