DuckDuckGo on October 7, 2026 added chat sharing to Duck.ai, its AI chat service, with share links that expire after 48 hours unless the sender picks another window. The company says each shared conversation is encrypted on the sender's device before upload, and that the only key able to unlock it travels inside the link itself, so DuckDuckGo cannot read what it stores.

In Short

DuckDuckGo now lets people send a link to a Duck.ai chat so someone else can read it, keep chatting from it, or save it, without needing an account. The chat is locked before it leaves your device, the key sits in the part of the link that browsers do not send to servers, and the page tells search engines not to list it. Links disappear after 48 hours by default, though nothing stops a recipient from copying what they read.

What DuckDuckGo shipped

The feature was described in a post filed under AI on DuckDuckGo's Spread Privacy blog on October 7, 2026, written by Ben Kaiser. "You can now create a link to share a Duck.ai chat! Anyone who receives the link can read the chat, continue it, or save it. No account required," according to the post. Sharing is optional, according to DuckDuckGo, and was available at Duck.ai from the date of publication.

There are two entry points. A share icon sits beneath every Duck.ai response, and clicking it offers a choice between sharing only that response or the entire chat up to that point. A full conversation can also be shared from the three-dot menu next to it in the chat list, through Share and then Create Share Link. The link is then copied and sent through whatever channel the sender chooses.

The interface shown in the announcement makes the trade-offs visible at the point of sharing. The share dialog carries a toggle between "Response" and "Entire Chat", a line stating that the feature creates a copy of the chat that can be viewed and saved by anyone who opens the link, a line reading "Encrypted. Not even DuckDuckGo can read your chat," and a note that follow-ups remain private. Below those sits an expiry selector with four values: 1 day, 2 days, 7 days and 30 days.

Recipients get more than a transcript. Anyone who opens the link can read the chat, continue the conversation on their own, or save it into their own Duck.ai chat list, according to DuckDuckGo. The conversation then forks. Follow-ups the recipient adds stay private to the recipient, and follow-ups the original sender adds stay private to the sender. Neither side sees the other's continuation.

There are limits on what travels with the link. Images generated by the AI are included in the shared chat, while files the sender uploaded are not, according to the company. Senders can review every link they have shared, with expiration dates, and delete any of them under Duck.ai Settings, in a new Shared Chats section.

Why DuckDuckGo built it

DuckDuckGo framed the feature as a fix for copy and paste. People use Duck.ai to compare options before a purchase, plan a trip, or debug code, according to the post, and until now the only way to pass that work to someone else was to paste it into another app. That "gives the other person a block of text instead of an interactive conversation they can continue," according to DuckDuckGo.

The company acknowledged the tension in adding a sharing function to a product designed around keeping chats private. "You may be asking, 'how can we add sharing to a product that is designed to keep your chats private to you?' As a privacy-focused company, we take this concern seriously, and we designed this feature with privacy at its core," the post states.

How the encryption works

The architecture rests on a familiar web technique. When a share link is created, the chat is encrypted on the sender's device before it is uploaded, according to DuckDuckGo. The resulting link has two components. The first is an identifier that tells DuckDuckGo's servers which encrypted chat to fetch. The second is the decryption key.

That key sits in the URL fragment - the portion of the address after the # character. "Browsers typically leave the fragment out of any requests they send to servers - including ours," according to DuckDuckGo. The server therefore receives the identifier, returns the encrypted blob, and the decryption happens in the recipient's browser using a key the server never received.

DuckDuckGo used an analogy for the arrangement: "sharing a chat is like storing a locked box with us and handing the key directly to your recipient." The company also said it tested the implementation to make sure the key does not end up in places where URLs commonly leak inside an organisation's own systems. "We tested this carefully to ensure the key will never wind up in our telemetry, error reports, or other logs," according to the post.

What the fragment design does and does not settle

The word "typically" in DuckDuckGo's description is doing honest work. Under standard HTTP behaviour, the fragment is not transmitted to the server in a request, which is why the design is common in encrypted file-sharing and paste services. But the fragment remains readable by scripts running on the page itself - that is how the browser obtains the key to decrypt the chat in the first place. The protection therefore depends on the code DuckDuckGo serves on those pages not sending the fragment anywhere, which is precisely the property the company says it tested for in its telemetry and error reporting. The post does not name the encryption algorithm, the key length, or whether the client code has been independently audited.

The fragment also travels wherever the full link travels. Anyone who holds the complete URL holds the key. That is by design: the link is the credential.

Indexing, guessing and expiry

Encryption addresses what DuckDuckGo can see. A second set of controls addresses who else can find the chat. DuckDuckGo listed four.

Unguessable links. Share links are long and random, "so no one can find your chat by guessing the link," according to the company. The post does not state the length of the identifier or key.

Noindex in two places. Every shared chat page tells search engines not to index it, "both in the page and in the response our servers send when the page is requested," according to DuckDuckGo. That describes a robots directive in the page markup and an equivalent instruction in the HTTP response header. Google's own documentation supports both forms: PPC Land reported in March 2025 that Google's robots meta tag documentation covers the page-level tag and the X-Robots-Tag header, and also notes that if a page is blocked in robots.txt, Google never sees the page-level rules at all. DuckDuckGo's post does not say whether share pages are also disallowed in robots.txt, a configuration that would prevent crawlers from reading the noindex instruction. "Google and other search engines will see those instructions and drop the page from their index, so it won't show up in their search results," according to the company. Compliance with these directives, like every other indexing control, rests with each crawler.

Expiry and deletion. Links expire after 48 hours by default, after which the shared chats are deleted from DuckDuckGo's servers, according to the post. The sender can instead choose 1, 2, 7 or 30 days, or delete the link at any time before it lapses. Copies already saved by recipients survive: "Anyone who saved a copy before deletion will keep their copy," the company states.

Fire Button coverage. The Fire Button inside Duck.ai, DuckDuckGo's one-step data-clearing control, now also deletes shared links. The company described this as a way to clear every chat and every link at once.

The incidents DuckDuckGo says it studied

The announcement is explicit about its reference points. "Over the past year, shared conversations from ChatGPT and Claude have appeared in search results, sometimes including users' names and other personal details," according to DuckDuckGo. The company gave two causes: in some cases people had opted in to making their chats discoverable without understanding what that meant, and in others share pages simply were not blocked from indexing.

DuckDuckGo said it studied those incidents before building its own system and set out four contrasts. Duck.ai share pages are blocked from indexing. There is no opt-in to discoverability at all. Content is encrypted with a key DuckDuckGo says it never sees or stores. Every link carries an expiration date.

The post does not name dates, numbers of exposed conversations, or the specific product changes either company made afterwards, and those claims are DuckDuckGo's characterisation of competitors.

What independent research has found about share pages

The broader record on chatbot share links is less flattering to the category than any single incident. Researchers at IMDEA Networks tested nine AI chat services in Spain in May 2026, and PPC Land reported on October 5, 2026 that six of nine web clients passed conversation URLs, chat titles, prompts or screenshots to outside firms. That study found every service exposed shared conversations without login and identified nine third parties present on sharing pages. Five web clients disclosed conversation URLs or their identifiers to nine services, and ChatGPT and Claude sent bare conversation IDs to Datadog, which the authors said could be used to rebuild the URL. Grok's permalinks were public by default, with an opt-out.

Duck.ai was not among the nine services IMDEA tested. A separate UC Davis study of 20 chatbots, which PPC Land covered in May 2026, found that 17 of 20 sent data to third parties during a normal chat, and that 15 of 20 sent per-conversation chat URLs to at least one third party. Duck.ai, Gemini and Meta AI were the three that contacted no external third parties in that test. The UC Davis paper predates Duck.ai's sharing feature, so it says nothing directly about the new share pages.

That research context explains the specific design choice on the key. A share URL that leaks to an analytics vendor or a tracking pixel is a privacy problem wherever the content is stored in readable form. Under DuckDuckGo's design, a leaked identifier without the fragment would point only to ciphertext. A leaked full URL, however, would carry the key with it.

The limitation DuckDuckGo spells out

The post devotes a section to what the feature cannot do. "Once you share a chat and someone else reads it, no technical measure can stop that person from saving it outside of Duck.ai or sharing it with people you did not intend," according to DuckDuckGo. The company went further: "Even if we tried to stop them from saving it digitally, they could memorize it or write it down on a sticky note. This is an inherent limitation of any private messaging or sharing tool, no matter how it's designed."

DuckDuckGo's guidance in the post is to send links directly to intended recipients, to share publicly only content the sender is comfortable seeing in public, and to keep expirations short, with the 48-hour default as its own example.

The save function adds a wrinkle. Recipients can save a shared chat into their own Duck.ai history, and that saved copy is not affected when the sender deletes the link. Deletion therefore removes the server copy and ends access for anyone who has not yet opened or saved it. It does not recall anything already received.

Where the feature sits in Duck.ai's privacy model

DuckDuckGo restated the baseline privacy claims that Duck.ai has carried since launch. "We call the AI models on your behalf so providers never see your IP address, chats are never used for training, and your chat history is stored on your device rather than our servers," according to the post. The sharing feature is the first in that model to place chat content on DuckDuckGo's servers by design, which is why the company built it around a key the server does not hold.

PPC Land covered the original launch of DuckDuckGo AI Chat on June 9, 2024, when the service offered GPT-3.5 Turbo, Claude 3 Haiku, Llama 3 and Mixtral 8x7B, stripped user IP addresses before forwarding requests, and said it had agreements requiring model providers to delete stored chats within 30 days. A browser redesign in July 2025 added more Duck.ai entry points and kept the Fire Button's one-click clearing.

The sharing feature also follows research that DuckDuckGo itself published in August 2026. That survey of 1,944 US adults, run by the company to support its own product and covered by PPC Land, found that 56% of self-described AI enthusiasts and 32% of AI users had told a chatbot something they kept from people in their lives, and that 53% did not know or were unsure that chats are used for AI training. Content of that kind is exactly what makes a share link sensitive.

Duck.ai remains optional. The company noted that it and all of DuckDuckGo's AI features can be hidden through search settings and the Duck.ai section of DuckDuckGo browser settings. PPC Land's June 2026 survey of AI controls across 10 search engines found DuckDuckGo's opt-out options the clearest among major mainstream engines. Feedback on sharing can be sent through a Share Feedback button inside Duck.ai, which the company says is anonymous.

Why this matters for marketers

For the advertising and search community, the feature is notable less for its convenience than for what it withholds. Indexed share pages from AI chat services have been one of the few public windows into what people actually ask chatbots and which brands surface in the answers. Duck.ai share pages, by DuckDuckGo's account, will not appear in search results, will not be readable by the platform, and will mostly vanish within two days. Whatever visibility marketers track in AI answers, these conversations are designed to sit outside it.

The design also sharpens a contrast that has been building in PPC Land's coverage through 2026. The IMDEA and UC Davis studies documented conversation URLs, chat titles and identifiers flowing from chatbot interfaces into advertising and analytics systems, at the same time as conversational platforms move toward ad-supported models. DuckDuckGo's approach treats the share URL as sensitive material that is never legible on its own servers. Whether rival services adopt client-side encryption for share links, or keep server-readable pages with indexing controls, will determine how much shared AI conversation data remains available to search engines, trackers and the platforms themselves.

There are open questions. DuckDuckGo did not disclose the cryptographic primitives, an independent audit, or any figures on Duck.ai usage, and the claim that the key never reaches its logs is the company's own, based on its own testing. The 48-hour default is the most consequential product decision in the release, because defaults decide how most links behave, and it is shorter than the 7-day and 30-day options the same dialog offers.

Timeline

Summary

Who: DuckDuckGo, in a post by Ben Kaiser on its Spread Privacy blog, for users of its Duck.ai chat service and anyone they send a link to.

What: Duck.ai now creates share links for a single response or a full chat. Chats are encrypted on the sender's device, the decryption key sits in the URL fragment, share pages carry noindex instructions in the page and the server response, links expire after 48 hours by default (or 1, 2, 7 or 30 days), and the Fire Button deletes shared links. Recipients can read, continue privately, or save the chat; uploaded files are excluded.

When: October 7, 2026.

Where: At Duck.ai and inside DuckDuckGo's apps and browsers, with link management under Duck.ai Settings > Shared Chats.

Why: DuckDuckGo says copy and paste gave recipients static text instead of a conversation they could continue, and that it designed sharing after studying cases where ChatGPT and Claude share pages appeared in search results with personal details. The company acknowledges no technical measure prevents a recipient from copying a chat once read.