Signing in with Google is one of Tarc's two account creation methods, and works slightly differently on the web app versus the Android app for technical reasons.
Tapping "Sign in with Google" redirects your browser to Google's standard OAuth consent screen, then back to Tarc once you approve. This is the same flow used by most websites that offer Google sign-in.
Google's OAuth consent screen blocks itself from loading inside a generic in-app browser view (a security measure Google enforces broadly, not something specific to Tarc). To work around this, the Android app opens the Google sign-in page in the system browser (Chrome Custom Tabs) rather than an embedded view, and then returns to the app automatically via a deep link once you've signed in.
Your email address and basic profile information, as provided by Google's standard sign-in flow. Tarc never receives or stores your Google password.
The first time you sign in with Google, you'll choose a username to complete account setup — see Create an Account.
Google's OAuth consent screen blocks itself from loading inside embedded in-app browser views as a security measure — opening the system browser (Chrome Custom Tabs) and returning via a deep link is the standard, required workaround.
No — Google handles authentication entirely; Tarc only receives your email address and basic profile information after you approve sign-in.
The underlying account result is the same, but the technical flow differs: the web app uses a standard browser redirect, while Android opens the system browser and returns via a deep link.