Using the Google Maps API on a site with user login (free)

Question

I'm planning to make a web app where users can register for free. The app will contain a map, and I will most probably use OpenStreetMap data. The problem I've encountered with open libs as for example OpenLayers is that they're really slow and choppy when adding a lot of markers (which will be totally unacceptable). I think the rendering speed of the Google Maps API is superior in comparison. Now, the question is, does Google allow using the API on a site where users have to login, but can register for free? Note that I will only use the .js-lib, not the data service itself.

Yes, I have read the Google Maps API terms (I couldn't get any sane answer from that), and I have also mailed them but only got the terms in reply. It seems you have to be a lawyer to understand them, and atleast if you make an app that is a corner case.

Of course, if anyone means that OpenLayers (or any other lib) is just as smooth as the Google Maps API, then maybe I've missed something. I'm interested in getting suggestions on what to use.

Update

I forgot to mention that I will eventually charge for some services within the application, but that will be totally independent of the map. In general, every registered user will be able to use the map unless they pay for something or not.

Thanks.

Answer 1

I'm not a lawyer, but this section from the API terms seems pretty straightforward (emphasis mine):

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. Unless you have entered into a separate written agreement with Google or obtained Google's written permission, your Maps API Implementation must not:

(a) require a fee-based subscription or other fee-based restricted access; or (b) operate only behind a firewall or only on an internal network (except during the development and testing phase).