Licensing for Embedded Google Apps (using Google Apps API's)

I've searched high and low but cannot find any clear explanation from anywhere on the internet regarding this situation. Google's pages go around in circles without ever leading to a full explanation. The situation:

Our web app displays a Google Spreadsheet in a sub-panel (iframe) and utilizes various Google API's (such as the Spread API) to access the data in the spreadsheet. Our value-added includes specialized spreadsheet macros, javascript functions, and custom-developed graphing tools. These tools provide customers with ways to analyze and improve business processes (through the use of statistical tools and other techniques developed by us).

My question: As just described, does Google permit us to sell licenses of our web application without incurring royalties to Google?

Everything about Google says "yes, yes, use our stuff. It's there for you.". Most of Google's web pages have a footer area stating that the page content is under the "Creative Commons Attribution 3.0 License" and/or the "Apache 2.0 License". But in that context, they are talking about that given page's content . . . not about reuse or inclusion of their software within another 3rd part application.

Amending my initial post: This URL comes as close as anything I've found regarding my original question. In fact, it opens up more questions. For instance, Google says,

"You will not sublicense an API for use by a third party. Consequently, you will not create an API Client that functions substantially the same as the APIs and offer it for use by third parties."

My interpretation, according to our situation, is that we wouldn't be sublicensing Google's API in any way. We would be licensing ("selling") only the value-added or in-house-developed code that we wrote which happens to work in conjunction with Google products. But they way they've worded things: so much is subject to interpretation.

I *think* that you can't create an api that does the same thing using their services and resell it. What you can do is create an application that embeds/frames google apps and utilizes the api's.

I have tried to find ways to avoid using google in anything I created because they have a tendency to remove services or change the rules.

I would word my contract that the service you provide utilizes google's application and your service may not work without that integration. Include any fees (per the google console) that may be charged for the api's. Also note that it is not your fault if google chooses to change or cancel the service that you have utilized.

Here is a summarizing of how I interpret Google's API licensing with respect to embedding various Google API's (such as the Spreadsheet API) inside our application. As I am not an IP lawyer, this is just my best guess and may contain errors. In that case, please, someone at Google clear this up for the world . . . what you've published on these issues is very obscure.

Any use of Google API code (such as Google Spreadsheets API) within our program is acceptable to Google because:

Individiual users, by creating their own Google User Account, will be directly licensing those API's from Google.

It's OK for us to extend the functionality of a Google Spreadsheet by using API scripts and other means that Google has provided to customize the functionality, look, and feel of a Google Spreadsheet.

Credit will be given to Google in our license stating that underlying engine components are Google-owned, and that the user is obtaining license to Google products by virtue of estabslishing a Google User Account.

Our application can't appear to be a mere clone of Google's product with no value-added features having beend added on our part.

We retain ownership of value-added features and code writen by us (code that extends functionality of Google products) and Google does not make any claim on that code.

Our program must comply with various ethical, design, and other statements as publshed by Google.

Much of the above is my interpretation of information located here, along with the input of those who have commented on this question.

Featured Post

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.