On Dec 7, 10:26 am, "inler.09" <[email protected]> wrote: > Hi! > > I work for a company that is developping and application which uses > google maps api. > > This application consists on a map where we draw some polylines and > add some markers. We pretend this application to be private, so as > only a couple of people could access to it.
The Terms of Service say this: "Your Maps API Implementation must be generally accessible to users without charge. You may require users to log in to your Maps API Implementation if you do not require users to pay a fee." That means that you can require a login, but if a login is required to access the map, you must make logins freely available to anyone who wants one. You can easily comply with the Terms by making the *map* freely available to anyone, but only allowing people with logins to see any of your *data* on it. Term 9.1 has changed: it used to say that logins had to be easily and freely available. That's no longer the case. You may now require a login, and any credentials you issue must be free; but you are under no obligation to issue logins if your map is already available without a login. [The reason for this is so that any advertising which is included on the maps is always available to anyone. So far, API maps don't include advertising, but the tiles used by Google Maps already do, so it's probably not far away] Andrew This post should not be treated as a substitute for consulting a lawyer. -- 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.
