What scopes should I choose for Google OAuth and how do I justify them?

What scopes should I choose for Google OAuth and how do I justify them?

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: 
  1. Referral program: We use the Google Contacts data to let our users pick their friends from their Google Contacts to send a referral to our application. We need both contacts.readonly and contacts.other.readonly in order to provide a consistent experience that people are used to where anyone they have interacted with shows up in the list of contacts. 
  2. Newsletter referral program: We use the Google Contacts data to let our users pick their friends from their Google Contacts to earn rewards by encouraging their friends to sign up for our newsletter. We need both contacts.readonly and contacts.other.readonly in order to provide a consistent experience that people are used to where anyone they have interacted with shows up in the list of contacts.
  3. Platform invitation: We use the Google Contacts data to let our users pick their friends from their Google Contacts to invite their friends to join them on our platform. We need both contacts.readonly and contacts.other.readonly in order to provide a consistent experience that people are used to where anyone they have interacted with shows up in the list of contacts.
  4. In general: We use the Google Contacts data to let our users pick their friends from their Google Contacts to [insert use case here]. We need both contacts.readonly and contacts.other.readonly in order to provide a consistent experience that people are used to where anyone they have interacted with shows up in the list of contacts.

See our complete Google OAuth guide here

Don’t hesitate to hit us up with any questions at support@cloudsponge.com. We also take dare requests. Just don’t dare us to exercise or get fresh air.