# Disconnecting an app does not retrieve every copy it received

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Disconnecting an app does not retrieve every copy it received

ID: MHC-D-RESEARCH-0164 · Version: 0.1.0 · Kind: concept
Source: https://vedokrok.com/knowledge/disconnecting-an-app-does-not-retrieve-every-copy-it-received

Closing the tap does not empty the other bucket.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You are disconnecting a linked app and need to know which access ends and which data remains.

### Avoid when

- Check the provider’s current controls and retention process. A removal confirmation is not proof of erasure or that every existing session ended; work accounts may need an administrator.

### Explanation

First identify the connection being removed. Google separates sign-in links, an app’s access to Google data, and an agent’s permission to use that app. Ending one is not a promise that all the others end. Removing a data-access grant stops that route; it does not retrieve copies already held by the developer. Account closure and data deletion need their own checks.

### Example

You stop a Google agent from using a linked planning app. The app’s account connection remains; inspect its data-access grant separately before calling it disconnected.

### Check

Can you name the access you ended, any links still present, and what must happen to the developer’s existing copies?

### Limits

- Check the provider’s current controls and retention process. A removal confirmation is not proof of erasure or that every existing session ended; work accounts may need an administrator.

### Evidence and sources

- supports: Linked-app grants identify data and actions available to the developer; previously copied data can remain under that developer's retention policy. — google-linked-app-data. Claim basis: technical_definition. Claim limit: The consent screen does not certify trustworthy handling after access is granted.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Access level; data retention; considerations before granting access"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Access level; data retention; deletion considerations)
- supports: Google manages sign-in links, app data-access grants and agent permissions separately. Stopping an agent does not remove the app’s account link; removing a sign-in link does not delete the app’s stored data. — google-linked-app-management. Claim basis: technical_definition. Claim limit: Each control affects its stated connection. This documentation does not establish closure of every existing app session or deletion of previously copied data.
Source access: selected_html_passages; accessed on: 2026-10-03; inspected sections: ["Sign in with Google", "Share access to your Google Account with an app from a developer other than Google", "Gemini and agent permissions"].
Source note: Selected official HTML sections read on 3 October 2026. This records current documented distinctions, not a verified feature-introduction date or a hands-on account test. The earlier source record remains in Git history.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Manage linked apps: Sign in with Google; Share access to your Google Account; Gemini and agent permissions)
- google-linked-app-data: How Google helps you share some of your account data with apps from other developers safely — https://support.google.com/accounts/answer/14013600
- google-linked-app-management: Manage links between your Google Account and apps from other developers — https://support.google.com/accounts/answer/13533235?hl=en

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
