Google Maps End User License Agreement

The Google licenses mentioned above are subject to the following requirements: 9.1 Free public access to the implementation of your API card. 9.1.1 General Rules. Free access (no fees). Subject to Section 9.1.2 (Exceptions), your Maps API implementation must be available free of charge to the general public and should not require a paid subscription or other limited paid access. This rule applies to your content and all other content in your Maps API implementation, whether your content or other content is present or added later. Public access (no firewall). Your Maps API implementation should not be run (i) only behind a firewall. or (ii) in a single internal network (except during the development and testing phase); or (iii) in a gated community (z.B. by simple access to the invitation).

9.1.2 Exceptions. Enterprise agreement with Google. Section 9.1.1 (Free Access, Public Access) rules do not apply if you have a separate written agreement with Google (for example. B a Google Maps agreement) or if you have obtained written permission from Google. Mobile apps. The Section 9.1.1 (a) (Free Access) rule does not apply when your card API implementation is used in a mobile app that is sold for a surcharge via an online store and can be downloaded to a mobile device that can access the online store. The Section 9.1.1 (b) (Public Access) rule does not apply if your map API implementation is an Android app that uses the Google Maps Android API. (However, the rule in section 9.1.1 (b) (Public Access) continues to apply when your card API implementation is an Android application using other map APIs, unless the Maps API implementation qualifies for Clause 9.1.2 (a) (Enterprise Agreement with Google).) 9.1.3 Examples. You can require users to log in to your Maps API implementation if you don`t charge users. You can calculate a fee for implementing your Maps API if it`s an Android app that can be downloaded to mobile devices from the Google Play Store. If you are a consultant who creates or hosts card API implementations for third-party customers, you can charge those customers a fee for your consulting or hosting services (but not for the card API implementations themselves, unless authorized by Section 9.1.2 (Exceptions). 9.2 Reports.

You must implement the reporting mechanisms required by Google (as they are updated from time to time under these conditions and in the documentation of card APIs). 9.3 Terms of Final Use and Privacy Statement. If you are developing an Maps API implementation for other users, you should show users of the map API implementation the link to Google`s terms of use, as displayed via the service or described in map API documentation. Expressly specify in the Terms of Use of your Maps API app that your users agree to be bound by the additional terms of use of Google Maps/Google Earth with the implementation of Maps API. protect the privacy and legal rights of these users. Your privacy policy. You must make a corresponding privacy policy available to the public in your card API implementation and comply with it. In particular, if your Maps API implementation allows you or a party to access information about map API (s) users, including personal data (for example. B usernames) or non-identifiable usage information (for example. B location), your privacy policy should describe your use and retention of this information.

Posted in Uncategorized