Google Account App Access: Review and Remove Connections

Cybersecurity & Privacy / Google Account / Practical guide

To remove an app’s access to your Google Account, open your account’s linked apps page, choose the app, review its data permissions, and remove the access you no longer need. Check sign-in links separately, and remember that disconnecting an app does not erase information it already copied.

An old calendar integration, document converter, or sign-in button can leave a connection you have forgotten. A useful review answers three questions: what is connected, what can it do, and which connection can you safely remove?

01 / Identify which direction the connection works

Google’s linked apps overview describes several relationships. The app name alone does not tell you which one you approved.

For the third row, Google Account Linking can let Google use a music service or connected device on your behalf. That direction matters: an app reading your Calendar and Google controlling your linked music account are different arrangements.

Review each relationship shown under the app. Treat the review as a small access inventory, with a separate decision for each connection.

02 / Read the action, not just the product name

A permission mentioning Drive or Calendar needs more scrutiny than a product label. Google’s data-access guidance distinguishes basic profile information, viewing or copying data, and managing data. Managing can include creating, editing, or deleting information.

The authorized scope matters: permission for Calendar does not automatically grant access to Photos or Contacts. Read the actual description rather than assuming every connection has full-account access.

Hypothetical example: you used an app once to copy appointments into a planning board. You no longer use the board. Even if its calendar permission made sense during setup, there is no continuing benefit from leaving that connection active. Record the app and remove the unused access.

For an app you still use, write down the task in ordinary language: “Create a calendar entry when a client confirms a booking.” Then compare that task with the permissions displayed. A mismatch is a reason to investigate the vendor’s explanation before authorizing more access.

03 / Prepare before disconnecting a useful service

For a routine cleanup, begin with apps you clearly no longer need. For an active service, check the dependency before changing it.

• Identify the person or workflow that uses the app.
• Save any records you need from that service through its supported export tools.
• Check scheduled jobs, booking flows, or reports that depend on the integration.
• Record which Google Account is connected and what you intend to remove.
• If you will remove Google sign-in, establish another supported way into the same app account first.

Google explains that your Google Account and your account with the other service remain separate accounts. Alternative login methods depend on the app. Contact its support if you cannot tell whether adding a password will preserve access to the same account.

Avoid experimenting by signing up again with another email address. You could end up reviewing an empty new account while your original records remain elsewhere. Confirm the account identity and stored work before changing its login arrangement.

04 / Remove the connection you actually intend to stop

The following controls follow Google’s current connection-management instructions. Labels can vary as the account interface changes.

Stop an app accessing Google data

1. Open the linked apps page and confirm the Google Account.
2. Select Access to your Google Account, then the app.
3. Open See details and review the listed permissions.
4. Select Remove access and confirm.

Stop Google sign-in or remove a linked account

For a sign-in connection, select Sign in with Google, choose the app, open its details, and select Stop using Sign in with Google. Confirm the change.

For Google’s access to an external account, select Linked account, choose the app, then use See details under Google’s access and select Delete link. Confirm.

If agent permissions appear, review them too. Removing an agent’s permission by itself does not disconnect the underlying app link.

Make one deliberate change at a time. For a business workflow, record the change beside the responsible person’s name so that a later reconnection request has context.

05 / Check the permission record and the affected workflow

Return to the connections page and inspect the same app in the same Google Account. Confirm that the relationship you removed is absent. If another relationship remains, decide whether it is still required.

Then inspect the app’s own integration settings. Look for a disconnected account or a request to reconnect. Do not approve a new request simply to make a warning disappear: that may restore the permission you just removed.

For an integration you are retiring, check that its replacement handles the real task. A harmless test booking or a sample document can help, provided you are authorized to create it. Record the observed outcome; an old record still visible in the app is not proof of continuing Google access.

There is a technical reason to review authorization directly. Google’s OAuth documentation explains that apps use access tokens for permitted operations, and may use refresh tokens to obtain new ones. Therefore, do not assume that closing a browser tab establishes whether an integration remains authorized.

06 / Deal separately with data already copied

Revoking access controls the connection; it does not pull back a copy already stored elsewhere. Google’s data-sharing safety guidance notes that apps can save information on their own servers and that retention depends on the app’s policies.

If your goal is to leave the service, inspect its privacy, export, account-deletion, and billing controls. Ask the provider what deletion covers and whether there are retention exceptions. Treat the answers as vendor-specific; do not assume every app follows the same process.

Keep a short exit checklist: required records saved, Google connection removed, vendor deletion request handled, and any subscription reviewed separately. Mark unresolved items rather than treating the disappearance of an app tile as proof that the whole exit is complete.

For Sign in with Google specifically, Google does not share your Google password. Removing consent does not erase the profile information previously shared. This is why changing a login connection and deleting an app account need separate decisions.

07 / Keep a small, useful access record

Record four things for each connection you retain: the app, its purpose, its permissions, and who will review it. Add a review date that fits your usage, and revisit the record after finishing a trial or replacing a workflow.

At the next consent screen, compare the requested access with that record. Treat additional permissions as a new decision. A familiar app name is not a reason to approve every new capability.

Account access is also separate from what software can do inside your browser. If the service includes an extension, review its installation and permissions using our browser extension permissions guide.

Frequently asked questions