As long as the map implementation is publicly available, you should be
good. You are not required to, say, make the target at the other end
of a link in an info window publicly available.
Just ask yourself this: can I, random person on the internet, see your
map and the code that drives it?
It doesn't even have to be the same data. You can use one DB for the
public and another DB for the private people, as long as the app
itself is available to all.
Not a lawyer. :)
-G
On Mar 17, 2010, at 1:15 PM, Jonathan Bender wrote:
Hallo,
I've read the Terms of Service, but could not derive a definite answer
to my (simple) question from it, so here it is:
My private, publicly accessible website contains a subsite called
"vacation pictures", which is just an overview / list of all vacation
locations. Each vacation location should get its Google Map.
Until now, everything is public. A click on a vacation location link
brings the user to the appropriate subsite, which then is password
protected, i.e. the actual vacation pictures are not public but
password protected.
=> Are there any legal problems with this type of use?
Any help is highly appreciated!
--
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
.
--
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.
