Re: [Action Needed] OAuth Verification Request Acknowledgement
Desi cryptoniun
Appeal Received
This is an automated email. Please ignore it if you have already responded to your prior submission.
If you have not yet responded, please read the information below carefully to determine the next step of your submission review.
Please respond to this email to begin the verification process. This verification request will be auto closed if we do not receive a reply.
Thank you for submitting your OAuth application for review. We acknowledge receiving the same. Before we begin your app's review we need you to:
Please confirm, by replying to this email, that your app does not fall in any of the following categories
1. If your application is requesting Fit API scopes:
Google Fit APIs are being deprecated and beginning May 1, 2024 we are no longer accepting application verification requests for Google Fit API scopes. Any application verification request containing only Google Fit API scopes will be auto closed and may not receive any further communication from the verification team.
Existing access to Google Fit API scopes will not be immediately impacted. For additional information and support, please refer to this blog post announcement.
2. If your application is for Personal use only:
The app is not shared with anyone else or will be used by fewer than 100 users. Hence, you can continue using the app by bypassing the unverified app warning during sign-in. It is recommended, however, that your project’s publish state is set to testing and continue to use your app under testing mode.
3. If your application is for Internal use only:
An app is internal when the people in your domains only use it internally. Learn more about public and internal applications. Learn how to mark your app as Internal in the FAQ How can I mark my app as internal-only?
4. If your application is for Development/Testing/Staging use only:
If your app is in development/testing/staging mode and not ready to be publicly accessible, then you do not need to submit your app for verification. Note that your app will be subject to the unverified app screen and the 100-user cap will be in effect when an app is in development/testing/staging. If your app is for Development/Testing/Staging, it is recommended that you keep your app’s publish status set to Testing and only update to In Production once it is ready for public use. Learn more about Publishing status.
5. If your application is a Gmail SMTP Plugin only for use by WordPress Site Admin(s):
If your app is WordPress Gmail SMTP plug-in where you and/or your other WordPress site admin(s) are the only users logging into the app, your app does not require verification. You can continue using the app by bypassing the unverified app warning during sign-in. It is recommended, however, that your project’s publish state is set to testing, and you continue to use your app under testing mode.
Please note: Switching between publish states (testing or production) and/or visibility statuses (internal or external) may impact your verification process and cause delays. Therefore, we recommend avoiding unnecessary changes.
Once we receive your confirmation, we will be able to start reviewing your submission and let you know if anything else is required from you.
Thank you for your patience.
GO TO MY CONSOLE
Best regards, The Google Trust & Safety Security & Privacy Team
© ${current_year} Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043
You have received this mandatory service announcement to update you about important changes to Google Cloud Platform or your account.
Desi cryptoniun
Hello Google Developer,
Thank you for your patience while we reviewed your submission for project 143077157120(Project ID: tomato-250225). We need you to address the following items for us to continue your app’s verification:
- The application name listed on your OAuth consent screen does not match the application name on your homepage.
- The logo shown on your OAuth consent screen does not match the logo on your homepage.
Please take the following action(s) to continue with your request
⤷ Update and resubmit your app in Cloud Console with the following:
- An accurate and up-to-date application name (Learn more)
- An accurate and up-to-date logo (Learn more)
Important! Once you have addressed the issues above, reply directly to this email to confirm. You must reply to this email after fixing the highlighted issues to continue with the app verification process.
No longer need access to these scopes?
Please reply to this email to cancel the verification request.
Need to make changes to your verification request?
Please make direct changes on the Cloud Console. Save and submit the changes when finished.
How do I check my submission status?
Please visit the Verification Center in the Cloud Console to check the review progress for each verification requirement
What are the verification requirements?
As a reminder, before your application can be approved you must meet the below requirements:
All Scopes (Non-Sensitive, Sensitive, Restricted)
Restricted and Sensitive Only
- App Privacy Policy
- Demo Video
- In-app Testing
- Application Use Cases
- Requesting Minimum Scopes
- AI/ML Model Training Privacy Policy Disclosure for Workspace APIs
Data Portability APIs Scope
Restricted Only
Need other help?
For more information on OAuth Verification, you can read the terms or policies for the APIs or products your app uses, as well as the following resources:
General Information
Verification Overviews
Troubleshooting
Thank you,
The Third Party Data Safety Team