A familiar app name can appear in several roles
Google’s linked-app learning page separates three filters: using Google to sign in, permitting an app to access Google data, and linking another service to Google. A music app might be connected for voice playback, while another app simply uses Google as its sign-in method. The name alone does not show which permission you granted.
Match the removal to the unwanted behaviour
Google’s management instructions explain that stopping Sign in with Google ends automatic sign-in without deleting data held by that app. Removing a link through which Google accesses the other service stops features that depend on it. Removing the other app’s access to Google data works in the opposite direction. Read the details under the connection rather than selecting a similarly named saved password. Filter by the connection type if an app appears more than once.
Check the account before and after the change
For example, someone who wants a speaker to stop controlling a music account should inspect the linked-account function. Someone concerned about an unused app reading Google information should inspect its data access instead. Before changing anything, confirm that the correct Google account is open and that another authorised sign-in route exists where needed. Afterwards, test the specific behaviour you intended to stop. The service’s own profile, records and billing controls remain separate questions; do not infer their status from a connection disappearing.
Questions, answered
Does deleting Sign in with Google erase the other app’s stored data?
Google explicitly says it does not; use that service’s own data and account controls.