Correct. They just have to be able to see the map (and your
implementation which uses it.) Your personal stuff does not need to be
part of that. I don't know what is in the mind of Google, but I think
the "spirit" of that section is to make it so a) you don't use their
service to drive your internal operations without paying, and b) other
people can further innovate from your work.
Fact of the matter is, you can even put the app behind a login
requirement, as long as ***anybody*** can get a username/password (and
therefore access to your map), regardless of location, nationality, or
financial contribution to your cause.
Still not a lawyer. :)
-G
On Mar 17, 2010, at 2:47 PM, Jonathan Bender wrote:
Thanks for your quick response!
To really be on the sure side, again in short: If a random user
without a password can see the Google Maps, further sites (with e.g.
vacation pictures, without Google Maps) do not have to be public,
correct?
On 17 Mrz., 20:39, Gregory Short <[email protected]> wrote:
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
athttp://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
.
--
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.
