On Oct 12, 6:52 pm, Jasper <[email protected]> wrote: > > Andrew you said: > > > Actually 10.4 of the Terms seems quite explicit > > First off, 10.4 is not relevant to this situation. I am not taking any > fees from anyone: I am just giving out account to my team and not to > others. > The rule that is relevant is 9.1. > So basically what you say is that the crux is the code that uses the > API - if that is the same for every user, you can change pther factors > for a select group of users. Is this a correct rewording of what you > said?
That's my interpretation of it. Everyone on the internet has to be able to get at your application -- you can force everyone to login if credentials are free and easy to get -- but not everyone has to be able to get at your back-end functionality. You may even be able to get away with charging for access to your back-end stuff provided that the front-end is the same for everyone. "Your maps implementation must not *require* a fee-based subscription or other fee-based restricted access" (my emphasis) For what it's worth, Gregory has said much the same thing, except that I reckon that the front-end code should be the same for everyone, so the panel containing the checkboxes should be built using AJAX from the back-end database. That's possibly a moot point though. 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 -~----------~----~----~----~------~----~------~--~---
