Thank you for your patience and we are sorry for the delay in responding to your inquiry. We have been receiving a high volume of requests and have experienced an unexpected technical issue that has since been resolved. We apologize for any inconvenience this may have caused.

Your app needs to follow some additional requirements to continue with the verification process:

Privacy Policy Requirements

Under the Google API Service: User Data Policy, your privacy policy and in-product privacy notifications must clearly describe the way your application accesses, uses, stores, or shares Google user data. The way you use Google user data should be limited to what you've described in your privacy policy.

Your privacy policy must also be:

  • Hosted on the verified domain of your website.
  • Visible to users.
  • Linked on the app home page.
  • Linked to the OAuth consent screen on the Google Cloud Console

Note: The privacy policy URL linked to the OAuth consent screen on the Google Cloud Console must match the privacy policy link on your app homepage. 

Limited Use Requirements 

Any use of Google user data obtained from Restricted and Sensitive Scopes must comply with the Limited Use Policy, and we suggest you disclose this to your users as described below. 

Next Steps

We recommend adding a disclosure that meets the following requirements:

  1. Easily visible to all users.
  2. Under 500 characters.
  3. Clearly calls out that the app complies with the Google API Services User Data Policy, including the Limited Use requirements.
  4. Contains a link to the Google API Services User Data Policy so that it is easily accessible to all users.

Example disclosure: “(App’s) use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.”

Note that apps distributed on Google Play are also subject to the Google Play Developer Distribution Agreement

Please reply directly to this email with the URL to the disclosure once it is added to your app or with confirmation that you will not be adding a disclosure. 

Scopes Justification

You must provide a detailed justification for your requested scope(s), and an explanation for why a narrower scope would not be enough.

  • https://www.googleapis.com/auth/calendar.acls
  • https://www.googleapis.com/auth/calendar.acls.readonly
  • https://www.googleapis.com/auth/calendar.readonly
  • https://www.googleapis.com/auth/calendar.calendarlist
  • https://www.googleapis.com/auth/calendar.calendars
  • https://www.googleapis.com/auth/calendar.calendars.readonly
  • https://www.googleapis.com/auth/calendar.events
  • https://www.googleapis.com/auth/calendar.events.owned
  • https://www.googleapis.com/auth/calendar.events.owned.readonly
  • https://www.googleapis.com/auth/calendar.settings.readonly
  • https://www.googleapis.com/auth/calendar.events.readonly

For example: https://mail.google.com/ to read and compose from Gmail. I will need read access in order to____ so that my app can ____. I will need compose access in order to ____ so that my app can ____ . A narrower scope would not be sufficient because ____.

Read these pages for more information about OAuth Scopes: 

  • OAuth 2.0 Scopes Page

Sign in branding 

The Google sign-in button on your app’s homepage URL is not compliant with the  Google sign-in branding guidelines.  (please see the attached screenshot)

Validation of App Functionality

In order that we can better understand your app’s functionality and your compliance with the Google API Services User Data Policy please reply back to this email with screenshot(s) or an unlisted YouTube or Google Drive file link to a video of the following:

  • Any branding guidelines.(s) and/or the button(s) used to launch the OAuth API integration.
  • The URL bar with the OAuth Client ID, which contains the project number.254950490992 (This is not required for native Android, iOS, and desktop installed apps.)
  • The Permissions Page may not be viewable due to using an account that has already granted permission to the application: Planipets.
  • Click "1 service" to showcase the data your application has requested from your users. (As seen in timestamp 00:26 of your demo video)
  • Your video will help us to check that you're requesting the most narrow scope(s) possible. Users are usually more prepared to grant access to limited, clearly-described scopes. If you ask for more data than you need, we'll either reject your request or suggest a more appropriate scope.

Thank you for your patience. Please let us know if you have any questions. You can also find more information in the OAuth API Verification FAQ.