Revoke third-party account access without assuming it deletes their data
Review Google account connections, distinguish sign-in from data permissions and remove access you no longer intend to grant.
In brief
“Sign in with Google” and permission to read Google account data are related but distinct connections. Review the actual access listed for an app rather than assuming the login button gives it everything or nothing.
This is useful after testing an app, changing jobs or discovering a service you no longer use.
Read the grant’s scope
Look for the particular products and actions listed, such as Drive file access or profile information. Compare that with the app’s intended task. A calendar helper requesting unrelated mail access deserves a closer explanation before you continue using it.
Remove the right connection
Use the removal action shown for that connection type. Confirm whether signing in to the app will need another supported route afterward. On a work account, involve the administrator for managed integrations so a cleanup does not unexpectedly break a necessary shared workflow.
Close the data-retention gap
Open the app’s own account controls if you want its stored data erased. Keep a record of the revoked access and any deletion request. If the grant was suspicious, inspect sessions and account recovery too; removing one app does not establish that all attacker access is gone.
Before you act
Revoking future access does not necessarily delete data the app already copied or close the account you created there. A separate deletion request may be needed.
What to do next
- Open your Google Account’s third-party connections page directly.
- Select the app and inspect whether the link is sign-in, account linking or access to Google data.
- Remove an unnecessary connection and check the app’s own data/account deletion controls separately.
