To help ensure your application's success as well as to promote a healthy community, we require that all Google+ API developers follow these guidelines.
- Put the user first
- Build something that Google+ users will love.
- Encourage useful sharing and give users meaningful choices about who they share with.
- Be transparent
- Be honest about the intention of your application.
- Show users what you will do on their behalf and get their explicit permission before you do it.
- Be clear about what is being sold via your application and post your terms of sale.
- Respect user data
- Use any data you collect to improve users' experience.
The below policies apply to all applications (including websites for the purposes of these policies) that call the Google+ API (called “API Clients” in our Google+ Platform Terms of Service) and specifically address:
- General rules
- Personal information from the Google+ APIs
- What you can't do in your application
- Related policies
A. General Rules
- Comply with the EU user consent policy.
Information you may not collect, store, or share
- Don't collect, store, or share sensitive personal information such as credit card, bank account, driver's license, or social security numbers, except as necessary to collect payment.
B. Personal information from the Google+ APIs
This section applies to users’ personal information (including lists of people from users' circles) your application gets by calling the Google+ API.
Using and sharing data from the API
- Don't use users' personal information for purposes beyond the limited and express purpose of your application (including as it may reasonably evolve due to ongoing development), or for purposes other than improving their experience in your application, without getting specific opt-in consent from the user.
- Don't sell, rent, make visible, or otherwise provide a user's personal information to any third party, including other users, without getting specific opt-in consent from the user. Opt-in consent isn't required to provide users' personal information to third parties, like infrastructure providers or customer service contractors, whose services are reasonably necessary to help you build or run your applications. You're responsible for how those third parties handle this information, and you must contractually require them to keep it confidential.
- Don’t use stale data. You can cache or store data you’ve obtained through the Google+ API, but to the extent reasonably possible within the context of your application, use fresh data recently fetched from the API. If the fresh data reveals that content is gone (for instance, because a user deleted it), delete it and don’t use your stale copy. For clarity, if you comply with these requirements, you may cache data longer than specified by the cache header.
Give users a reasonably convenient way to delete any of their
personal information you’ve obtained from the API.
- Don't show the user that their data has been deleted without actually deleting the data within a reasonable period of time.
- If you created an account for the user associated with their identity on Google+ (including internal accounts not explicitly exposed to the user) you must give the user a reasonably convenient way to delete that association.
- If a user deletes their account on your system, deletes the association between that account and their account on Google (“disconnects”), or deletes their Google account, you must delete all personal information you obtained from the Google API relating to them.
As the only exceptions to the above, you may keep the following
- Information you're required by applicable law to retain.
- Information you're required to retain by a separate agreement with Google.
- Aggregated information that does not include any of the user's personally identifying information, and would not allow that information to be inferred.
- Information (e.g. email address) that you obtained from other Google APIs, as long you comply with their terms.
- The user's Google user ID.
- Give users a reasonably convenient way to delete any of their personal information you’ve obtained from the API.
Please also note the Data Portability requirement in our Google+ Platform Terms of Service requiring you to allow users to export data equivalent to what you access via the API.
C. What you can't do in your application
Application listing and purpose
If you list your application on Google+, we give you the ability to describe your application.
- Don't be dishonest or incomplete about the application's purpose or type in your description.
- Don't trick users into installing something that's significantly different from what your description leads them to expect.
- Don't include repetitive text, irrelevant keywords, or misleading formatting in your description.
- Don't list your application more than once or create multiple listings that all point to an application with essentially the same functionality.
- Don’t mislead your users about what your application does, or trick them into using it.
- Not all relationships are created equal—two users can have each other in circles, or a user can simply follow someone. Your application should respect that distinction, and not suggest a reciprocal relationship that doesn’t exist.
- Don't include functionality that proxies, requests, or collects usernames, passwords, or other personal authentication information for Google accounts.
- Don't mimic functionality or warnings on the user's computer system or on Google.
- Don't induce users to violate Google's terms of service or other applicable Google policies.
- Don't allow unlawful gambling. You may include simulated gambling, but if you do, you must prevent your users from converting their simulated winnings into something of value outside your application, such as transferable virtual goods, virtual currency, or money.
Posts to the stream and notifications initiated by your
- Don’t mislead your users about what buttons or links included in posts or notifications will do, or trick users into clicking them.
Don't do any of the following without the user taking an explicit
action each time to initiate it:
- Post an update to the user's stream or send a notification (including invite).
- Modify the user's circles in any way.
- Share the user's location information.
Don't send any posts on behalf of the user without:
- Showing an accurate preview of what's about to be posted and making sure the user is aware of what will cause the share action.
- Allowing users to append their own text.
- Letting users pick the individuals or circles with whom they want to share.
- Indicating that your application is the source of the post or notification.
- Don't circumvent a user's Google+ privacy settings, including the user's circles or other permission settings.
- Don't circumvent technical limitations on your use of Google-provided APIs, such as limits on the number or frequency of stream posts. Don't screen scrape or use any non-documented APIs.
- Don't circumvent any Google+ user interfaces that ensure the user is aware of and agrees to stream posts or the like made on their behalf.
- Don’t circumvent any Google+ user interfaces or settings that limit the visibility of information, such as stream posts, from others.
- Don't share with any third party any personal authentication mechanism granted by Google or by any user to you, including your personal certificate or a user's authorization token.
- Don't override the default sharing option to be “Your circles,” “Extended circles,” or “Public.”
- Don't encourage, facilitate or incentivize repetitive or spammy posts.
- Don't mislead users about requirements to access any functionality in your application.
- Don't require your users to post to the stream or issue a notification (including invites) in order to access application functionality. Posts to the stream and notifications should always be optional.
We take security very seriously: we can suspend your application without notice if it appears to have a security or stability issue that could affect Google or its users.
- If you experience a security breach or misuse of information, you must notify Google.
- If you experience a breach exposing private user information, you must also notify your users.
Additional rules for the Google+ canvas
Where content from your application appears while the user is on the Google+ canvas, a few extra rules apply.
- Provide meaningful functionality. Don't just provide a link to a webpage, a piece of static content, or a pointer to install an application off of Google+. (It's OK to provide a link to install a native mobile application that uses the Google+ APIs.)
- Don't generate pop-ups or pop-unders in a new window.
- Don't employ distractions from the primary purpose of the application, like long-running animations, auto-playing video or audio, or strobing/flashing backgrounds.
- Don't use your application to promote or advertise alcohol, tobacco, ammunition and firearms, or other content not suitable for users under the relevant age of majority (whether in an on-canvas application, via stream posts, or other content that appears on Google+).
- Only use Google's in-app payments for in-app purchases in applications located on the Google+ canvas.
- Clearly and honestly describe the products or services that you are selling. Conspicuously post your terms of sale (including any refund and return policies).
- Make it clear that you, not Google, are the seller of your products and services.
- Don't require users to pay to obtain basic application functionality without explaining in your application's description that payment will be required.
- Please also note the requirements in our Google+ Platform Additional Terms regarding user data and third-party advertising.
- User experience
Writing app activity to Google
If you write activities to Google via the moments API the following additional rules apply:
- You must use reasonable efforts to make users aware of the activities that you write to Google.
- Unless you obtain the user’s explicit consent, you must:
- Only write activities based on a user’s direct action in your application.
- Only write activities at the time of that user action, or as close as technically reasonable.
- If your application handles information covered by the Video Privacy Protection Act ("VPPA") then you must comply with the VPPA. You confirm that any disclosure to Google of information covered by the VPPA will not be incidental to the ordinary course of your business.
- Additional rules when Google+ Sign-In is used
- When your application displays a login screen to a user, an option for Google+ Sign-In should be presented at least as prominently as other third party login options.
- Your application must make it reasonably easy for users to:
- Know if they are connected to a Google account, and if so to which account.
- Disconnect the application from their Google account(s).
- Sign out of your application.
These policies may be revised from time to time without notice. Please check back here for any updates.
Last revised August 7, 2015