Udostępnianie rozmów z Claude AI wymaga zrozumienia ustawień prywatności.
Technology · V2 version after source audit
Instructions for sharing a Claude conversation, updating the snapshot, revoking the link, and checking privacy before sending.
First publication:
14 January 2025
Verification:
18 July 2026
Length:
931 words
Reading time:
approx. 4 min
checked sources
Evidence level:
High for the current Anthropic help documentation; the interface may change
Author’s schematic illustration prepared for this article. It does not replace a documentary photograph or measurement.
What we know
- A shared chat is a snapshot covering messages sent before the link was created or updated.
- New messages after sharing remain private until the user updates the snapshot.
- The link can be revoked by changing the chat visibility from Shared to Private.
What remains uncertain
- Button names and their placement may differ between plans and app versions.
- Sharing an organisational project has different rules from sharing a single chat.
- One should not assume that revoking the link deletes copies previously saved by recipients.
1. 1. How to create a conversation link
2. 2. What exactly the person with the link sees
3. 3. Whether later messages appear automatically
4. 4. How to revoke sharing
5. 5. Sharing a conversation and sharing a project are not the same
6. 6. Checklist before sending the link
7. 7. When it is better not to use a public link
8. 8. Questions and answers
9. Bibliography and sources
10. The most important rule: the link shows a snapshot, not automatically the entire future chat
11. Control list before sending the link
1. How to create a conversation link
1. Open the conversation you want to share.
2. Open the conversation menu or the sharing button visible in the current interface.
3. Choose the option to share or publish the chat.
4. Read the preview and the message describing the scope of publication.
5. Confirm creation of the link.
6. Copy the address and open it in a private window to see the view of a non-logged-in person.
Button names may change with product updates. The official Claude Help Centre maintains the current „Share and unshare chats” instructions.[[1]](#ref-1)
2. What exactly the person with the link sees
The recipient sees the published content of the conversation. They do not get access to the sidebar, account history, other projects, or billing data. One must assume, however, that everything visible in the snapshot can be copied, saved as a screenshot, or quoted outside Claude.
The risk is not limited to names and email addresses. Conversations often contain:
- fragments of contracts and client documents,
- contact details, order numbers, and identifiers,
- API keys, tokens, and temporary passwords,
- internal strategies, prices, and financial data,
- attachments and text extracted from attachments,
- file names revealing the project or client,
- instructions the author did not intend to publish.
3. Whether later messages appear automatically
A shared conversation should be treated as a snapshot. According to Anthropic’s documentation, the published version can be updated, but later messages should not be considered automatically public without checking the settings.[[1]](#ref-1)
This solution has an advantage: after creating the link, you can continue working privately. The danger arises when the user later updates the snapshot without re-reading the new messages.
4. How to revoke sharing
1. Open the source conversation on your account.
2. Go to the sharing menu.
3. Choose unshare, disable link, or the equivalent option.
4. Confirm deactivation.
5. Check the link in a private window.
Disabling the link blocks further access through the Claude address. It does not delete copies the recipient previously saved. Therefore revoking publication does not fully repair the disclosure of confidential information.
5. Sharing a conversation and sharing a project are not the same
A Claude project can contain project knowledge, instructions, and many conversations. Visibility and collaboration settings apply to a broader space than a single chat snapshot. The official Help Centre describes managing project visibility separately.[[2]](#ref-2)
6. Checklist before sending the link
- Does the conversation contain personal data?
- Have you pasted a password, token, API key, or secret address?
- Does the content belong to a client, employer, or another person?
- Can the attachments be legally shared?
- Does the recipient need the whole conversation, or only the final result?
- Are there incorrect model responses in the middle that, without comment, could be taken as facts?
- Should the link remain active indefinitely?
Anthropic publishes separate information about privacy and data processing. For business data, the terms of the specific plan and the organisation’s policy should also be checked.[[3]](#ref-3)
7. When it is better not to use a public link
For sending a result to a client, an edited document is often better. It allows removing unnecessary prompts, failed attempts, and working data. In a corporate environment, an approved document system with access control may be safer.
A public link makes sense for content intended for further distribution: a tutorial, prompt example, public analysis, or demo conversation. It still needs to be read as material intended for publication.
8. Questions and answers
Can the person with the link edit my chat?
They do not edit the source conversation on your account. They can, however, copy the content or start their own work based on it if the interface provides such a possibility.
Is the link private if I sent it to one person?
One should not assume so. Any recipient can forward the address.
Does deleting the conversation disable the link?
It is safest to use the explicit revoke-sharing function and check the address after logging out.
Are later messages public?
Treat the publication as a snapshot and check the preview on every update. Do not assume the state is automatic.
Bibliography and sources
1. Claude Help Center, [Share and unshare chats](https://support.claude.com/en/articles/10593882-share-and-unshare-chats).
2. Claude Help Center, [Manage project visibility and sharing](https://support.claude.com/en/articles/9519189-manage-project-visibility-and-sharing).
3. Anthropic, [Privacy Center](https://privacy.anthropic.com/).
4. Anthropic, [Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms).
5. Anthropic, [Trust Center](https://trust.anthropic.com/).
SN
Redakcja Spraw Nauki
Popular-science material prepared on the basis of the sources indicated in the bibliography. In health-related topics, the text does not replace medical advice, and in organism identification it does not replace consultation with a specialist.
The most important rule: the link shows a snapshot, not automatically the entire future chat
After creating the link, the recipient sees the content included in the shared snapshot. The further conversation is not appended automatically. To add it, the owner must re-enter the sharing menu and choose update. This limits accidental disclosure of later messages, but does not relieve the obligation to check content before the first sharing.
The chat may contain artefacts, document fragments, surnames, client data, logs, tokens, or medical data. Before creating the link, scroll through the conversation from the beginning and also check attachments and elements generated in artefacts.
Control list before sending the link
- Remove passwords, API keys, document numbers, and login data.
- Anonymise data of clients, employees, and patients.
- Check that the artefact does not contain metadata or content from the source file.
- Do not share confidential project instructions or materials covered by an NDA.
- After collaboration ends, disable the link and check visibility.
- Assume the recipient can take a screenshot or copy the text.
In a Team or Enterprise environment, project visibility is managed separately. A chat in a project does not automatically become shared just because the project is available to the team; sharing a specific conversation still requires user action.
Variable interface:
the instructions were verified on 18 July 2026. When publishing, it is worth adding current screenshots from your own account and blurring private data.