
Long-lived Google accounts tend to accumulate connections to services that were authorized once and then forgotten. A calendar tool, a photo editor, a fitness app or a sign-in button on a website can keep permissions to profile data or other resources long after the user has stopped relying on it. Google documents a linked-apps page where users can review which third-party services hold access and remove it. The mechanism behind these connections is OAuth, an authorization framework that lets an application request access to a service’s resources on the user’s behalf without normally receiving the account password.
- Key Point: Google provides a dedicated page at myaccount.google.com/permissions where users can review and revoke third-party app access.
- Key Point: OAuth grants an app an authorization token rather than the account password, but the token can still expose profile data and other permitted resources.
- Key Point: Revoking access stops future use of the connection but does not necessarily erase data the app already copied.
- Key Point: Removing a connected app is distinct from ending a subscription or deleting an account held by that app.
What a connected app actually holds
Under a standard OAuth flow, the provider handles sign-in and the application receives an authorization token instead of the user’s provider password. A scope describes the access requested, and an access token is the credential the app uses to reach an API. The permission screen should state which account is involved and what access is being granted. Google’s own consent screens identify the specific permissions, or scopes, an app is requesting.
Some integrations ask for more than their core function appears to require. An app that only needs to display an event, for example, should not automatically need broad permission to edit unrelated data. Names and logos on a consent screen are not proof of identity, and a legitimate provider screen does not make a suspicious application trustworthy. Users should compare each requested permission with the task the app is meant to perform.
How to review and revoke access
The practical route is to open the account provider’s official settings directly rather than following an unexpected message to a consent screen. On Google, the linked-apps page lists third-party services with access to the account and allows the user to remove that access. Other providers use different menus, and employers or schools may impose administrator restrictions on what users can approve.
Before approving any new connection, users should confirm which account is selected, who is requesting access and whether the connection was intended. An unfamiliar or unexpectedly broad request should be declined or closed and verified with the provider or organization before proceeding. Sign-in credentials, one-time codes and approval prompts belong only in the official provider’s flow.
What revocation does and does not do
Removing an app’s access can stop the connection or disable features that depend on it. It does not necessarily delete data the app already copied, cancel an account held by that service or end a subscription. Users who want data removed must check the app’s own privacy and deletion options separately. If a connection was approved without recognition, the recommended step is to remove access through the provider and follow its security guidance.
The distinction matters because connected-app access is a form of delegated authorization rather than a password handoff. A token can remain valid for as long as the provider and the app allow, which is why periodic review of the linked-apps page is more useful than a one-time cleanup. The same logic applies to devices and active sessions, which can persist even after an app is removed from an account list.
Why this matters beyond a single account
Connected apps are also becoming a larger part of how Google’s own products operate. Google opened a public preview of its Connected Apps Platform, which lets approved applications run inside AI Mode in Search and in the Gemini app. Developers connect through a remote MCP server or through AppFunctions, which Google refers to as Android MCP, and registration takes place through a Google Connected Console. Google reviews and tests each app before publication, and its policy bars apps from deceiving or influencing the model into selecting one connected app over another.
Google has launched more than 50 connected apps across Search and Gemini, and it says additional developers, geographic markets and products will be added in the coming months. As more services seek permission to act on a user’s behalf, the consent screen and the linked-apps page become the main points of control. For anyone who has used the same Google account for years, the first step is simply to look at what is still connected.
