Start with the access list, not your memory
A Google Account can be connected to services that use Google sign in or request access to products such as Gmail, Drive, Calendar, Photos, and Contacts. Those connections are not all equivalent. One app may only receive basic account details, while another may be allowed to view or change data. Google says a linked app can access only the services and permissions you authorize, so the first useful audit is to read the actual list instead of guessing from the app name.
Open your Google Account’s linked apps page and inspect each entry. Google’s official review instructions say to select an app, choose “See details,” and review the products and access level shown there. Look for services you no longer use, old experiments, duplicate tools, and names you do not recognize. A familiar brand is not a reason to skip the details, because an old connection can outlive the project that created it.
Decide what should stay
Keep a connection only when you can explain why it needs the listed access today. A calendar planning tool may need calendar data, but that does not automatically justify access to Drive or Contacts. Read the developer’s privacy policy and security information before approving a service. Google specifically warns against giving a third party your Google password. The permission screen is safer because it grants selected access rather than handing over the whole account.
For a service you still use, check whether it offers a narrower setting or a way to disconnect individual features. If the permission is broader than the job requires, contact the developer or move the task to a service with a clearer access model. Keep notes for work or school tools that are approved by an administrator. A managed account may restrict what you can authorize or remove, and a missing removal button is not a reason to bypass policy.
What revoking access actually does
When you select “Remove access” and confirm, the app can no longer use that Google authorization to access your account. Google says this may make some features unavailable. For example, a service may stop importing Google Calendar events. Removing a data-access grant and removing a Sign in with Google connection are different actions, so check which connection type you are deleting. Removing the connection does not delete your Google Account, and the separate account you created with that service remains separate from it.
Revocation is also not a recall button. If the service already copied files, messages, contacts, or other information, removing access does not automatically delete that copy. Google’s data portability guidance says the third party remains responsible for copies it received. Visit the service’s own privacy or account page to request deletion, and check its retention policy. If you suspect misuse, change relevant passwords, review recent account activity, and use Google’s account recovery and two step verification guidance.
A small audit that stays useful
After revoking an entry, record what stopped working and whether you still need the service. Do not confuse a failed sign in with proof that your Google Account is compromised. Reauthorize only after reading the new request. Repeat the audit when you stop using a service, change jobs, or finish a one time project. For broader warning signs on a computer, see how to recognize spyware and adware. The goal is not to remove every connection. It is to make every remaining connection understandable.
References
Google Account Help: Review and manage linked apps; Google Account Help: Share some access to your Google Account data with apps; Google Account Help: Share a copy of your data with a third party.