Removing an AI assistant’s access can stop new collection while leaving yesterday’s transcripts, summaries and exports intact. A ticket marked “integration removed” leaves those copies unaccounted for.
OAuth token revocation invalidates tokens, not the data already collected. Google’s <a href="https://support.google.com/accounts/answer/14012355?hl=en” rel=”nofollow noopener” target=”_blank”>account guidance says that users may need to ask a developer to delete data it already holds.
For a meeting assistant, use five steps: inventory, establish a test baseline, remove access, handle retained copies, and verify closure.
Assign an internal owner to the offboarding ticket. Check retention requirements and legal holds before requesting deletion. Preserve the evidence needed for the ticket before closing the account or losing access to its administrative console.
Inventory the actual backlog, including meeting IDs, dates, record counts and known destinations. A test meeting can check a deletion path; it cannot account for every historical copy.
Give each row an internal owner, a requested action, a due date and a status. Name the provider contact separately when execution depends on them. For retained records, document the approved reason and permitted access. An unanswered provider request remains open.
2. Establish a harmless baseline
Consider a fictional company testing its meeting assistant before retirement. A test meeting says that project Juniper uses reference code JN-742. The assistant creates a transcript and summary, then copies an action item into a tracker.
Confirm which copies actually contain the invented fact. Save their IDs and successful retrieval results. In a fresh assistant session, ask “What is Juniper’s reference code?” without including the answer. Repeat with a differently worded question and record any
Use invented data throughout, including in query logs. A failed lookup after deletion means little if the same check never worked before deletion.
3. Remove every route to new collection
Record the account, grants and permissions being removed. Disconnecting an integration in the assistant’s dashboard may differ from revoking its grant at the identity orother users’ grants and existing sessions. Restrict reauthorization where organizational policy permits
OAuth is only one route. Check calendar invitations, meeting-bot admission and personal accounts that can invite the assistant independently. Remove or block those routes through the relevant administrative controls.
Ask the provider which access tokens, refresh tokens and grants its revocation action invalidates. RFC 7009 describes token-dependent behavior and possible propagation delays. Its instruction to stop using a successfully revoked token applies to the client application. Administrators should use documented verification methods, not replay credentials.
After any propagation delay the provider documents, hold a new, harmless test meeting under the affected setup. Check whether the bot appears or a new recording, transcript or summary is created. Inspect collection and job logs where available. Record the setup, time, observations and any visibility gaps. Absence of a bot alone does not prove that every collection route is closed.
Delete eligible records through the supported process. Reconcile the actual inventory against deletion receipts, remaining IDs and documented exceptions. Check derived summaries and search entries separately from their
Handle tracker items, downloaded exports and recap emails at their destinations. Removing a file from the assistant does not remove someone else’s download. If an external recipient’s copy cannot be verified, record that limitation and the responsible owner.
For backups, record the retention period and who can restore them. Ask how deletions are reapplied before restored data becomes available. Capture the provider’s evidence when direct testing is unavailable. Track subprocessor copies and required retention separately rather than describing everything as erased.
5. Verify, then close what is resolved
Repeat the baseline checks by record ID and in fresh assistant sessions. Do not put the reference code in the questions. If it returns, inspect the citedese checks.” Retrieval failure alone is not proof of deletion
Pair these checks with inventory reconciliation, administrative records and provider evidence. Close resolved items individually. Keep unresolved copies, pending backup expiry and access gaps assigned to named owners with review dates.
Before the next purchase, ask whether the assistant can identify derived records, report deletion status and explain what survives a restore. Agentkit’s checklist for deleting derived memory includes questions covering these copies.
Alan Edwards is a software developer and technology writer. He builds applications with large language models and writes about AI agents and cybersecurity.
