Does Deleting a Gemini Public Link Delete a Recipient's Continued Chat?
Deleting a Gemini public link stops the URL, but not a recipient's continued chat. Learn what remains and how to contain the exposure.
No. Deleting a Gemini public link stops new access through that URL, but it does not delete a copy that another person already created by choosing “Continue this chat.” Google says the continued conversation can be stored in that person's Gemini Apps Activity, under that person's Google Account. The original sharer cannot remotely erase it with the public-link control.
That distinction is easy to miss because a Gemini share page looks like one conversation. In practice, it can create at least two separate records:
- the public snapshot at the
g.co/gemini/share/...address; and - a continued conversation saved in a recipient's account.
Revoking the first does not revoke the second. If a shared Gemini chat contained private, regulated, embarrassing, or commercially sensitive information, treat link deletion as containment—not complete recall.
The Short Answer
Google's current Gemini chat-sharing guide is explicit about both sides of the boundary:
- deleting the public link makes the old link show that the chat no longer exists;
- it does not delete the original chat from the creator's Gemini Apps Activity; and
- it does not delete the chat from another person's Gemini Apps Activity if that person continued the shared chat.
The recipient owns the continued conversation in the practical sense that it is now stored with the recipient's account and controlled through that account's activity settings. The creator can ask the recipient to delete it, but the creator's “Delete public link” action is not a remote-delete command for the recipient's copy.
| Record | Where it lives | What the creator can do | What link deletion does |
|---|---|---|---|
| Original Gemini chat | Creator's Gemini Apps Activity | Delete it with the creator's activity controls | Does not delete it |
| Public share page | Google's public-link surface | Delete the link from Your public links | Makes that URL stop serving the chat |
| Recipient's continued chat | Recipient's Gemini Apps Activity, when saved | Ask the recipient to delete it | Does not delete it |
| Repost containing the URL | Social network, forum, email, or messaging service | Delete posts the creator controls; request removal elsewhere | Leaves the post, although its destination should be dead |
| Screenshot, download, quote, or manual copy | Recipient device or third-party service | Request deletion where possible | Does nothing |
The safest mental model is: a share link is an access path, not a recall system.
What Is Confirmed
Anyone with the public link can read and reshare the snapshot
Google says creating a Gemini public link creates a shared page that anyone with the URL can read, even if the creator did not send the link to that person directly. That person can also reshare the link.
The page is a snapshot. Google says it shows the conversation as it appeared when the creator made the link. Later edits or additions to the creator's chat do not automatically update that public page.
That snapshot behavior helps explain the deletion boundary. The public page is not simply a live window into the creator's current sidebar. It is its own sharing surface with its own URL and control.
Eligible recipients can continue a shared chat in their own Gemini account
Google's sharing guide says a person opening someone else's public chat can select Continue this chat and continue it with Gemini on their own. The feature is not available to users under 18, and chats created with Gems have an exception. Google also says that a shared chat created by a Google AI subscriber may require the recipient to have a Google AI subscription before continuing it.
When the recipient's Keep Activity setting is on, Google says the shared chat is stored in that recipient's Gemini Apps Activity with the recipient's Google Account.
That is more consequential than simply bookmarking the public URL. The recipient has converted material from the public snapshot into an account-level conversation that can continue independently.
Deleting the creator's public link does not delete the recipient's continued chat
This is the central confirmed fact. Google's current sharing guide says deleting a public link “doesn't delete the chat from other's Gemini Apps activity” when they continued it in Gemini on their own.
After deletion, a new visitor using the old public URL should see a message that the chat no longer exists and be redirected to Gemini. But the already-continued conversation does not depend on that URL remaining live.
The recipient has a separate activity-deletion path
Google's Gemini Apps Activity guide tells a signed-in user how to delete all Gemini Apps activity, a date range, a day, or a specific activity item. That is the control a recipient would use for a continued copy saved to their account.
Google says manual or automatic activity deletion starts a process that first removes the item from view and then removes it from storage systems. The creator cannot operate those controls in someone else's account.
“Keep Activity off” is not the same as instant non-retention
If Keep Activity is off, a continued conversation may not appear as a persistent item in the recipient's visible Gemini Apps Activity. That still does not justify saying the data was never stored.
Google's activity guide says conversations are saved with the account for up to 72 hours when Keep Activity is off so Google can provide the service and process feedback. The Gemini Apps Privacy Hub adds that these chats may be used to respond, protect Google and its users, and process feedback.
The practical answer therefore depends on the recipient's settings and actions, but the creator's deletion power does not expand. The creator still cannot use link deletion to control another account's retained or continued material.
What Is Still Unclear
Google's documentation clearly answers the main question, but it cannot tell a creator what every recipient actually did.
You cannot see a complete list of people who continued the chat
Google's public help page does not describe a creator dashboard listing every account that opened, reshared, screenshotted, downloaded, quoted, or continued a public chat. Without a recipient telling you, you may not know whether an account-level copy exists.
That uncertainty is why deletion should be paired with incident-style scoping rather than a simple assumption that the link was never used.
You cannot prove that no manual copy exists
Even if nobody used Continue this chat, a visitor could have copied text, downloaded an included image, saved the page, taken screenshots, pasted the conversation into another AI service, or quoted it in a private message.
Google says a public shared chat can include AI-generated artifacts such as Canvas documents, images, and videos. The sharing page also warns that an uploaded image can be available and downloadable from the shared chat. Deleting the URL later does not reach those copies.
A dead link does not remove the post that contained it
Google says deleting a Gemini public link does not delete third-party posts containing the link. A social post, forum entry, email, ticket, or message can remain visible even when clicking its URL no longer reveals the Gemini page.
That remaining post may still disclose context through its text, preview, title, thumbnail, quoted excerpt, or replies. Cleanup needs to cover the post as well as the destination.
Reviewed or disassociated data may follow a different lifecycle
The Gemini Apps Privacy Hub says that when Keep Activity is on, saved activity can be used to provide, improve, and develop Google services, including training generative AI models, with help from human reviewers. It also says activity already reviewed by service providers may be retained separately after being disconnected from the account.
Those rules are about Google's processing lifecycle, not the public-link control. Deleting a link does not prove that every representation used for safety, feedback, or service improvement is immediately erased. The exact outcome depends on settings, whether feedback was submitted, and whether material had already entered a reviewed-data path.
Work and school accounts can behave differently
Google notes that Workspace administrators can disable Gemini conversation sharing. Its current Workspace access guide says that when an administrator restricts sharing, people opening the chat link receive an error.
Managed retention, history, access, and deletion may also be controlled by the organization. A personal-account cleanup checklist should not be treated as proof of what a work or school administrator can inspect or delete.
Why A Continued Chat Is A Separate Privacy Event
It is tempting to think that a recipient is merely “viewing your chat.” Continuing it changes the data path.
The public snapshot can become input to a new account-level interaction. The recipient can add questions, combine the inherited context with new information, and generate new outputs. The resulting conversation can develop beyond what the creator ever wrote or approved.
That creates four separate privacy risks:
- Persistence: the inherited content may live under another account's retention settings.
- Expansion: the recipient can add context and generate new material based on the shared content.
- Redistribution: the recipient can share, export, quote, or screenshot the new conversation.
- Loss of control: the creator has no direct control over the recipient's account or copies.
None of this means the recipient has done something malicious. It means the sharing action changed who controls later deletion.
Use The RECALL Checklist After Sharing Sensitive Gemini Content
Deleting the public link should be the first step, not the last one. Use RECALL to scope the records that may remain.
R — Revoke the exact public link
In Gemini, open Settings & help > Your public links, locate the URL, and choose Delete public link. If the exposure is broad or you cannot reliably identify the correct link, review every public link and use Google's Delete all links option when appropriate.
Save the exact URL before deleting it if you need to verify the result or document an incident. Do not publish the URL in a public incident note.
E — Examine the old URL while signed out
Test the exact link in a signed-out or private browser window. Google's expected behavior is a message that the chat no longer exists followed by a redirect to Gemini.
Signed-out testing matters because an authenticated browser can hide account-state differences. Record the time, URL, response, and any cached preview that remains. If the content is still reachable, recheck that you deleted the correct public-link record.
C — Contact known recipients
Ask people who received the link whether they opened it, selected Continue this chat, downloaded any media, took screenshots, copied passages, or reshared it. Keep the request factual and specific.
A useful request is:
I revoked the Gemini share link because it contained information that should not remain shared. Did you continue the chat or save any part of it? If so, please delete the continued conversation from your Gemini Apps Activity and remove any copies or reshares.
The request is not proof of deletion, but it is more effective than asking vaguely whether someone “still has the link.”
A — Audit third-party posts and previews
Search the places where the link was posted: email, team chat, issue trackers, forums, social networks, documents, and notes. Delete posts you control and request deletion from services or people who control the others.
Look for cached link previews, quoted prompt text, screenshots, filenames, and comments that repeat the sensitive content. A dead URL can still leave meaningful metadata behind.
L — Limit the original account's remaining records
Deleting the public link does not delete the creator's original Gemini chat. Use Gemini Apps Activity to delete the relevant source conversation if that is part of your cleanup objective.
Remember that deleting the chat and deleting the public link are related but distinct controls. Our focused guide, Does Deleting a Gemini Chat Delete Its Public Share Link?, explains why both should be handled and verified separately.
L — Learn what the incident requires next
If the shared content included credentials, access tokens, private keys, financial numbers, health information, student information, legal strategy, customer data, unpublished results, or regulated records, deletion may not be enough.
Rotate secrets. Notify the appropriate security, privacy, legal, compliance, or records team. Preserve the minimum evidence needed for the investigation. Follow applicable breach, contractual, or organizational procedures. Do not rely on a request to a recipient as a substitute for professional incident handling.
How To Delete A Recipient's Continued Gemini Chat
Only the recipient can perform this account-level cleanup, unless a managed-account administrator has separate authorized controls.
For a personal account, Google's current steps are:
- Sign in to Gemini.
- Open Settings & help > Activity, or use Google's Gemini Apps Activity page.
- Find the continued conversation or relevant activity item.
- Delete that specific item, day, date range, or all Gemini Apps activity as appropriate.
- Review recent or pinned chats to confirm it no longer appears.
- Remove any screenshots, downloads, exports, reshares, or third-party copies separately.
The recipient should also review Keep Activity and auto-delete settings. Google says the default auto-delete period for Gemini Apps Activity is 18 months and can be changed to 3 or 36 months or turned off. That setting affects future lifecycle management; it does not replace deletion of an item that should be removed now.
How To Share Gemini Chats More Safely Next Time
Public-link cleanup is inherently weaker than preventing sensitive material from entering the share page.
Before creating a link:
- remove names, addresses, account numbers, credentials, private URLs, and distinctive facts;
- check the entire conversation, not just the last response you want to share;
- inspect uploaded images and generated artifacts;
- assume anyone with the URL can read and reshare it;
- assume an eligible recipient can continue it into their own account;
- use a synthetic example when the real data is not necessary;
- prefer a short excerpt in a controlled channel over a public conversation link; and
- for managed organizations, consider disabling conversation sharing when the business need does not justify it.
Redaction also needs judgment. Removing a person's name may not be enough when a combination of employer, location, date, job title, diagnosis, transaction, or unusual event still identifies them.
Where OpenVeil Fits—and Where It Does Not
OpenVeil is a hosted, privacy-focused AI workspace for adults. Normal chat history is stored in the user's browser, and OpenVeil does not maintain a normal server-side chat-history record. That narrower history design can be useful when you do not want a long account-level cloud archive of ordinary chats.
OpenVeil is not fully offline. Active prompts, uploads, search, voice, image, video, and other requests still require processing by OpenVeil and necessary providers. Browser-local history is not the same as anonymity, zero logs, or no provider processing.
Most importantly for this question, OpenVeil cannot revoke a Gemini public link, delete another person's Gemini Apps Activity, erase screenshots, retract pasted text, or undo information you intentionally shared with another person or service. No AI product can make a recipient's independent copy remotely disappear merely because the creator deletes a local or public record.
OpenVeil is a fit when your goal is a narrower private workspace for future AI conversations. It is not a cleanup tool for data already shared through Gemini.
Frequently Asked Questions
If I delete a Gemini public link, can someone still open the old URL?
Google says no. The visitor should see that the chat no longer exists and be redirected to Gemini. Verify the exact URL while signed out because deleting the wrong link or leaving another public link active can produce a different result.
Does deleting the link delete my original Gemini chat?
No. Google says the public-link action does not delete the chat from the creator's Gemini Apps Activity. Delete the original activity separately if you want it removed.
Does deleting my original Gemini chat delete the recipient's continued chat?
No. The recipient's continued conversation is associated with the recipient's account when saved. Deleting records in the creator's account does not operate the recipient's controls.
Can I tell who continued my Gemini chat?
Google's current public help documentation does not describe a creator-facing list of everyone who continued a public conversation. Ask known recipients and scope other evidence, but do not treat lack of evidence as proof that no copy exists.
What if the recipient had Keep Activity turned off?
The continued chat may not appear as a persistent item in visible Gemini Apps Activity. Google still says conversations with Keep Activity off are saved with the account for up to 72 hours to provide the service, process feedback, and protect users and Google. The creator still has no remote-delete control over that path.
Can a Workspace administrator delete the recipient's copy?
That depends on the organization's edition, policies, retention configuration, account authority, and current admin controls. Google's public consumer steps should not be used to infer an administrator's exact powers. Ask the authorized Workspace administrator or records team.
Does deleting the link remove screenshots or copied text?
No. Screenshots, downloads, exports, pasted passages, quotes, and reposts are separate copies. They must be addressed where they exist.
Is a Gemini public link private because it is not indexed or sent directly to everyone?
No. Google describes it as a public link and says anyone with the URL can read the chat and reshare it. A hard-to-guess URL is not an access-control list.
Bottom Line
Deleting a Gemini public link stops that URL from serving the shared chat, but it does not delete a conversation that a recipient already continued into their own Gemini Apps Activity. It also does not erase the creator's original chat, third-party posts, screenshots, downloads, quotes, or manual copies.
Use link deletion to contain further access. Then verify the dead URL, contact known recipients, remove third-party posts, delete the creator's source chat when appropriate, and handle any sensitive-data exposure through the right security or privacy process.
The durable rule is simple: once an AI conversation has crossed into another person's account or device, deleting the share link can close the door, but it cannot retrieve everything that already passed through it.