Does YunoBot send your messages anywhere? A network test, and how to repeat it
No request made while loading YunoBot or chatting with it contained any word of the message, in its URL or its body. In a Chrome test on 3 October 2026 a message was sent after the page had settled, and the only new traffic was two analytics requests from this site's own tags. The reply is computed by a WebAssembly module inside the page, so there is no chat endpoint to send the text to.
- Test date
- 3 October 2026
- Browser
- Headless Chrome driven over the DevTools protocol, phone-sized viewport, cache disabled
- Page
- https://yunusemrevurgun.com/yunobot (production)
- Message
- "Explain Chessko difficulty levels please"
- Requests before sending
- 41 (21 to this site, the rest third-party analytics)
- Requests after sending
- 2, both to Yandex Metrika: a click-map GET and a POST with an empty body
- Requests containing the message
- 0 of 43
What exactly was tested?
A script opened the production page, waited for it to load plus nine seconds for the WebAssembly core, the knowledge pack and the analytics tags to settle, confirmed the input was enabled, then typed the message and clicked Send. It waited a further sixteen seconds. For every request it recorded the URL, the method and, for POSTs, the body fetched through Network.getRequestPostData. It then decoded each URL and body and searched them for every word of more than four letters in the message: explain, chessko, difficulty, levels and please. There were no matches.
What traffic does the page make?
| When | To | What |
|---|---|---|
| On load | This site (21 requests) | The page, CSS, fonts, scripts, the worker, core.wasm, the knowledge pack, images and the manifest, plus a Cloudflare real-user-monitoring POST |
| On load | Third parties | Google Tag Manager and Google Analytics, Yandex Metrika (including its cookie-sync requests), the Cloudflare Insights beacon and gor.bio |
| After sending | Yandex Metrika | A click-map GET carrying the page address and where the click landed, and a POST with an empty body |
| After sending | This site | Nothing |
The site loads analytics tags on every page, including this one. They are separate from the chat: in this test, none of the requests they made carried the typed text.
How can I repeat the test myself?
- Open the chatbot, then open your browser's developer tools (F12) and go to the Network tab.
- Wait until the page has settled, tick Preserve log and clear the list.
- Send a message containing a word nobody else would use, for example
quokka-7731 weather. - Search the traffic for that word: use the Network panel's search (Ctrl+Shift+F, or Cmd+Option+F on a Mac), which searches request headers and bodies, and also type the word into the filter box, which matches URLs.
- To take the analytics out of the picture, block
*yandex*,*googletagmanager*,*google-analytics*and*gor.bio*in Network request blocking, reload and repeat.
If the word appears nowhere, your message did not leave the page.
What does this test not prove?
It is one message in one browser over one run, with a window of sixteen seconds after sending. It inspects requests; it cannot speak for a browser extension you have installed, or for code that is changed later. Because the chatbot is client-side code, anyone can re-run the check on whatever the site serves at the time. Treat it as a method, not a certificate.
Where does the reply come from, then?
From a WebAssembly module running in a Web Worker in the page. It classifies the message and searches a knowledge pack that was downloaded when the page loaded. How YunoBot works describes each step.
Quick answers
- Does YunoBot store my conversation?
- Messages are held in browser memory for the current conversation. Clear starts a new one, and Export saves a file on your own device.
- Do the site's analytics tags see what I type?
- In the test, none of the requests those tags made contained the typed message. They did receive the page address and click events.
- Can I check this myself?
- Yes. Open the Network tab, send a message with a unique word and search the traffic for it. The steps above take about a minute.