Kirill Bondar 5/5/2025 2:15:16 AM OAuth 2 uses the concept of "application" -- one that requests the data on user's behalf. The application requests the set of privileges and keeps track of user's granted permissions. To let database library samples work out of the box we registered two OAuth 2 applications -- one with Google and one with Microsoft. Both requesting broadest set of privileges possible and because of that one registered with Google triggers the warning. We even started verification process but were unable to explain properly why our OAuth 2 application wants to access every piece of user's data. For best results, you should probably register your own OAuth 2 application with Google asking just for privileges you need. By registering an application, you will obtain your very own Client ID and Client Secret, and its security parameters will be under your control. Here is Google's instructions: https://developers.google.com/identity/protocols/oauth2/web-serverRedirect URL mentioned in instructions is: https://www.teamdesk.net/secure/oauth.aspxModify your third-party account to use: Type: OAuth 2 Authorization URL: https://accounts.google.com/o/oauth2/v2/auth?access_type=offlineToken URL: https://oauth2.googleapis.com/tokenClient ID: <obtained from application registered at Google> Client Secret: <obtained from application registered at Google> Scope: https://www.googleapis.com/auth/calendar | 
