We have written an exhaustive guide on getting approved for Google OAuth here.
We recommend watching this video before you begin:
*Recently Google changed their requirements for the privacy policy. They have provided this examples, "“(App’s) use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.” You can simply copy/paste and then add your app's name to fulfill the requirement.
Are you getting frustrated? Reach out at support@cloudsponge.com. We meditated before logging in today, We’ll send some of our zen your way.
To use Google Contacts for the Contact Picker, choose the People API scopes, contacts. readonly and contacts. other.readonly. To justify your scopes, pick one of the use case justifications below: Referral program: We use the Google Contacts data to ...
Add us to your Google OAuth Google OAuth is tricky to get right. We understand the frustrations, we’ve helped 100’s of customers through the process. That’s why you should consider this recommended step when setting up your Google OAuth. Adding us to ...
You need to prove that you own your domain before Google approves your OAuth project. Here’s how to do it. Did you already verify your domain? Maybe you aren’t quite sure that your domain is verified. Maybe you are trying to figure out which Google ...
There’s one critical step in the process, which is to add the ../auth.contacts.readonly and ../auth.contacts.other.readonly scope to your Google developer account. If this scope isn’t present, Google will just rubber stamp your verification and make ...
Years ago, CloudSponge was able to share Google OAuth credentials. Over time, Google stopped allowing us to share these credentials with you. You will need to get verified by Google for the People API. You can read our complete guide on Google OAuth ...