Hi everyone, Google Product Manager for Maps APIs here. We are not revoking Routebuilder’s access to the Maps API. Unfortunately, we mistakenly sent a letter to Routebuilder saying that they were in violation of the Google Maps API terms of service. This was an error. Once the developer contacted us about this issue, we replied apologizing for the misunderstanding and confirming that we would not be revoking his access to the Maps API. (He contacted us on Friday, we replied on Monday, the blog post was published on the weekend.)
We’re really glad he let us know so we could fix the issue and we encourage any developers that have issues in future to reach out to us so we can help. Developers who want to contact the Google Maps APIs team: Stack Overflow and our issue tracker forum (https://code.google.com/p/gmaps-api-issues/) are both monitored by the Google Maps team weekly.
Hahaha. We have been through this with AdSense. Without the negative PR Google would have never replied. This is also a good lesson for the aspiring Play Store Android developers.
Hi everyone, Google Product Manager for Maps APIs here. We are not revoking Routebuilder’s access to the Maps API. Unfortunately, we mistakenly sent a letter to Routebuilder saying that they were in violation of the Google Maps API terms of service. This was an error. Once the developer contacted us about this issue, we replied apologizing for the misunderstanding and confirming that we would not be revoking his access to the Maps API. (He contacted us on Friday, we replied on Monday, the blog post was published on the weekend.)
We’re really glad he let us know so we could fix the issue and we encourage any developers that have issues in future to reach out to us so we can help. Developers who want to contact the Google Maps APIs team: Stack Overflow and our issue tracker forum (https://code.google.com/p/gmaps-api-issues/) are both monitored by the Google Maps team weekly.