Once the user approves, Google sends a temporary, single-use authorization code back to Opera’s servers, not directly to the browser.
However, users must understand the trade-off: You are trading a piece of your identity correlation (Google knowing you use Opera) for the convenience of not managing another password. opera login with google
Ultimately, Opera implemented this feature not because they love Google, but because they understand human nature: People will not use a sync feature if the login is harder than the sync is worth. By lowering that barrier with Google Login, Opera ensures that more users stay locked into their browser ecosystem—even if Google gets a small nod along the way. Once the user approves, Google sends a temporary,
For the average user who already lives inside Google’s ecosystem, it is a safe, fast, and efficient way to sync their Opera browser across devices. For the privacy-conscious, it is a vector to be avoided in favor of a standalone Opera account. By lowering that barrier with Google Login, Opera
Opera redirects the user to Google’s OAuth 2.0 authorization server. The URL contains parameters specific to Opera, including the client_id , redirect_uri , and scope .