Application Use Cases

If you have received this notification in your email from the OAuth verification team, your application use case potentially falls under a prohibited use case for Google Drive.

We require more information to determine whether your app fits within an approved use case and/or is permitted to access Google Drive scopes under the Google Drive API Terms of Service. 

Step 1: Understand the acceptable and prohibited use cases for Google Drive

Review the appropriate use cases outlined in the Google Drive API policy to understand how your app has been assessed.

Step 2a: if you agree your app is a prohibited use case

Reply directly to the email you received from the OAuth Verification team and we will close your request.

Step 2b: if you believe your app is an acceptable use case

Reply directly to the email you received from the OAuth Verification with the following information:

• Clarify which acceptable use case your app aligns to

• Detailed reasoning for how your app aligns to this use case based on functionality, user features, and an in-depth explanation of how the requested Google Drive scopes are being used by your app

If you have received this notification in your email from the OAuth verification team, your application use case potentially falls under a prohibited use case for Gmail.

We require more information to determine whether your application fits within an approved use case and/or is permitted to access Gmail scopes under the Google Workspace API Terms of Service. 

Step 1: Understand the acceptable and prohibited use cases for Google Drive

Review review the appropriate use cases outlined in the Gmail API policy to understand how your application may be categorized

Step 2a: if you agree your app is a prohibited use case

Reply directly to the email you received from the OAuth Verification team and we will close your request.

Step 2b: if you believe your app is an acceptable use case

Reply directly to the email you received from the OAuth Verification team with the following information:

• Clarify which acceptable use case your app aligns to

• Detailed reasoning for how your app aligns to this use case based on functionality, user features, and an in-depth explanation of how the requested Gmail scopes are being used by your app

If you have received this notification in your email from the OAuth verification team, your application use case potentially falls under a prohibited use case for Fit.

We require more information to determine whether your app fits within an approved use case and/or is permitted to access Fit scopes under the Google Fit Developer and User Data Policy. 

Step 1: Understand the acceptable and prohibited use cases for Google Drive

Review review the appropriate use cases outlined in the Google Fit Developer and User Data Policy to understand how your application may be categorized

Step 2a: if you agree your app is a prohibited use case

Reply directly to the email you received from the OAuth Verification team and we will close your request.

Step 2b: if you believe your app is an acceptable use case

Reply directly to the email you received from the OAuth Verification team with the following information:

• Clarify which acceptable use case your app aligns to

• Detailed reasoning for how your app aligns to this use case based on functionality, user features, and an in-depth explanation of how the requested Fit scopes are being used by your app

Based on the information you provided, we need to assess whether your application is using Google user data to enable health research. All apps accessing data for this purpose are required to follow the Google Fit Health Research Policy and complete an additional assessment. This is based on an assessment of one or more of the following:

• The demo video you provided
• Your privacy policy
• Testing of your application

What we need to continue your review

Please complete the following questionnaire to continue verification: Fit & Health Research. Once you have submitted the questionnaire, reply directly to this email to let us know. Your application will then continue to the next phase of the verification process.

If you believe this is an error

Respond to the email you received to confirm you are not a Health Research application and clarify that your app will not use Google user data to enable health research.

If you have received this notification in your email from the OAuth verification team, your application use case potentially falls under a prohibited use case for Workspace APIs. Transfer and use of Workspace API data for generalized machine-learning (ML) or artificial intelligence (AI) models is prohibited.

We require more information to determine whether your app fits within an approved AI/ML use case and/or is permitted to access Workspace API scopes under the Google Workspace API User Data Policy. 

Step 1: Understand the acceptable and prohibited use cases for Workspace APIs

Review the appropriate use cases outlined in the Workspace API user data policy and Google Workspace API Policy Protections for Generative AI to understand how your app has been assessed.

Step 2a: if you intend or are attempting to use Google Workspace data to train generalized AI and/or ML models

Reply directly to the email you received from the OAuth Verification team and we will close your request.

Step 2b: if your app is using Google Workspace data to train personalized AI/ML models ONLY, or your app is not using AI/ML models at all:

Reply directly to the email you received from the OAuth Verification team and confirm the following:

• You have updated your privacy policy to clearly describe what Google user data (if any) your app uses for developing, improving, or training AI and/or ML models.
• You have updated your privacy policy to explicitly affirm that Google Workspace APIs are not used to develop, improve, or train generalized/non-personalized AI and/or ML models.
• You have updated your privacy policy to clearly describe what Google user data (if any) your app transfers to third-party AI tools, and that the transfer is not for generalized/ non-personalized AI/ML models.