You may not realize it, but passwords are the single biggest threat to your online security – they’re easy to steal, they’re hard to remember, and managing them is tedious. Many people believe that a password should be as long and complicated as possible – but in many cases, this can actually increase the security risk.
Project Strobe was started to help users have control over their data while giving developers more explicit rules of the road to ensure everyone is confident that their data is secure.
One result of this effort has been to expand our app verification program to cover more apps and more types of data access.
It is important to understand how the process works so that you can optimally build your app and streamline the verification process.
Add a visibly trusted and secure Sign In With Google button to your app.
Users sign-in to a Google Account once, without re-entering username or password when visiting your site. On return visits sign users in automatically or with one click.
Create new accounts with a single tap and get assisted signed-in across devices, reducing the risk of duplicate accounts and forgotten passwords.
Securely store and retrieve username/password credentials, avoiding users having to re-enter credentials on return visits.
Google's OAuth 2.0 APIs conform to the OpenID Connect specification, are OpenID Certified, and can be used for both authentication and authorization.
While we normally recommend the use of Sign In With Google for user authentication, in some situations you may want to call our APIs directly.
Integrate your services and APIs with Google, share media and data with Google Assistant, Smart Home, YouTube and more. After obtaining user consent securely link an individual Google account with an account on your platform with OAuth 2.0 standard flows.
Improve user privacy with custom scopes, sharing only the data necessary for a specific use case. Increase user trust by clearly communicating how Google uses this data.