Review and Remove Apps Linked to Your Google Account

To remove an app’s access to your Google data, start at your Google Account’s Linked apps page. Open the app’s details, check the permission involved and remove the connection you no longer want. Before disconnecting a service you still use, check how you will sign in afterwards.

The distinction matters because a Google sign-in button, permission to read your calendar and a music service linked to Google are different arrangements. Removing one does not necessarily remove the others. It also does not erase information an app has already received.

This guide covers personal Google Accounts using Google’s current documentation. For a work or school account, your organisation can impose its own app-access rules; ask its administrator about a blocked or managed connection.

First, work out what the connection allows

An app’s name and logo do not tell you what you authorised. Google’s overview of linked apps describes several kinds of connection, which can coexist for the same service.

Connection	What you have allowed
Google sign-in	Google helps establish your identity when you enter another service.
An app’s access to Google data	The app can use the particular Google data and actions you approved.
Google’s access to another account	Google can use authorised features of the other service on your behalf.

For ordinary Sign in with Google, Google shares your name, email address and profile picture with your permission. It does not hand over your Google password. Access to other Google information requires an additional permission request. A site using Google sign-in therefore does not automatically have access to your inbox. Google explains these boundaries in its sign-in privacy guide.

Data access is a separate question. A calendar integration might be allowed to read events, while another permission could allow changes. Google distinguishes viewing or copying information from managing it, which can include creating, editing or deleting data. Read the action as well as the product name in the permission details.

Account linking can work in the other direction. Connecting a music account so Google can play something from that service lets Google use features of the music account. That is a different purpose from letting the music service inspect your Google data. Google’s account-linking explanation gives examples involving music, connected-home devices and television services.

Before removing a sign-in you still need

For routine housekeeping, prepare access to the service before removing its Google sign-in connection. Google and the service maintain separate accounts, and some providers do not support multiple sign-in methods for the same account. Google’s connection troubleshooting guidance makes both points clear.

Open the service directly and check its account settings. If it offers a way to add a password, passkey or another sign-in method to your existing account, follow that provider’s instructions. Test the alternative in a separate browser session, then check that you can see the same projects, purchases or saved work. A successful login to an empty new account is not the result you need.

Keep your working session open while you check. If there is no supported alternative, contact the provider before removing a sign-in you rely on. Do not assume its password-reset form will create an alternative for a Google-only account.

If you are leaving the service entirely, decide what you need to export and whether you also want to close the account there. Treat that as a separate task from removing Google access.

These preparation steps are for connections you recognise and still trust. If a grant looks suspicious, prioritise revoking it and securing the account; preserving a convenient login can wait.

Remove the connection that matches your goal

Open Linked apps, confirm the Google Account, select the service, then use See details where offered.

Google’s current removal instructions distinguish these controls:

To stop the app using Google account data, choose Remove access.
To disconnect its Google sign-in arrangement, choose Stop using Sign in with Google.
To stop Google accessing the other service, choose Delete link.

Confirm the change and check the relevant permission afterwards. A service can have multiple connection types, so review each one you want to remove. Repeat for your other Google Accounts.

If you also see Gemini or AI-agent permissions

Removing an agent’s permission leaves the underlying app connection in place. Review that connection separately if you want to disconnect the service. Google notes that AI linking features vary by region and app.

Decide what to keep by the job it still does

There is no useful target number of connected apps. A short list can contain an unnecessary permission; a longer list can support several deliberate workflows. The practical question is whether you can explain each connection’s current purpose and accept its access.

For each app, ask:

What do I still use it for? Name the actual task, such as importing appointments or signing into a course platform.
What can it access or change? Read the permission wording rather than relying on the app’s category.
Does that access fit the task? A request to manage unrelated information deserves an explanation from the provider before you approve it.
Would I reconnect it today? If the answer is no, decide whether to remove the grant, close the provider account or do both.

Permission breadth is only part of that judgement. Consider who operates the service, how it uses information and whether you are comfortable with its retention policy. Google’s data-sharing guidance explains why information copied onto another company’s servers needs this separate consideration.

A worked example: keep the planner, retire the integration

Suppose a planning app has two connections: you sign in through Google, and it can also manage your Google Calendar. You still use its notes, but you stopped using calendar synchronisation months ago. This is an illustrative situation, not a claim about a particular app.

Start by identifying both entries. Your goal is to retire calendar access while retaining a way into your notes. Remove the data-access connection and check how the planner behaves. A feature that depended on Calendar may stop working; decide whether that feature is still necessary before granting access again.

You might keep Google sign-in because it still serves a purpose. Alternatively, if the provider supports another method for the same account and you have tested it, you could remove that connection too.

Finally, consider the appointments the planner already imported. Review its own controls or contact its operator about those records. Stopping further access and asking for stored information to be deleted are two different outcomes. Record which one you have actually completed.

Revoking access does not finish every cleanup task

Previously copied information can remain with the provider. Removing a grant stops further access through that permission; it does not retrieve files or records already transferred. Retention and deletion depend on the provider’s policies and processes. If you want those copies removed, use its data-deletion controls or contact it. Google describes this limitation in its guidance on sharing account data.

An existing session at the service is a separate issue. Google’s developer documentation explains that a website manages its own signed-in session after Google authentication. Do not use an open, still-working tab as proof that removal failed, or assume every device was signed out. Use the provider’s session controls if your goal includes ending access on other devices.

Deleting the provider account may leave a Google connection behind. Google says the provider does not necessarily notify it when that account is deleted. After closing a service, check the Linked apps list as well. Conversely, deleting a Google connection is not the same as closing the provider account. The account troubleshooting page explains the separation.

Will changing your Google password remove every app?

Do not rely on a password change as a substitute for reviewing app grants. Google API access can use tokens, credentials that represent approved access without giving an app your password. Some integrations can also refresh an expired access token.

Google’s OAuth documentation lists several reasons a refresh token can stop working. It specifically includes a password change when the token contains Gmail permissions, and lists user revocation separately. That is not a promise that every connected app loses every permission after a password reset.

The practical recommendation follows from that distinction: change a compromised password, and explicitly remove grants you no longer authorise. Do not choose between the two when both are needed.

If you find a connection you cannot explain

An unfamiliar entry deserves investigation, but the list alone is not proof of a breach. Check the provider identity and the task associated with it. If you cannot justify its access, remove it. If there are other warning signs, such as unrecognised account activity or changes to your recovery details, follow Google’s compromised-account recovery guidance.

That wider review includes security events, signed-in devices, recovery information and unexpected settings. An app-permission cleanup addresses one route into your data; it cannot establish that every other route is secure.

Finish by checking the result you actually wanted: obsolete permissions are gone, the accounts you still need remain accessible, and any requests to delete stored data have been handled with the relevant providers. Keep the connections whose purpose you can still explain.

Sources

Information checked against Google documentation on 30 October 2026.