MarketBubbleSearch for X: privacy

Effective 2 November 2026

MarketBubbleSearch for X is a browser extension. On X posts that are recordings in search.lexthedev.com, or clips of one, it adds a button that shows the recording's summary, where a clip came from, and a box to ask about it. It is an independent project by Lex (@Lexx_eth), not affiliated with X Corp. or with any show it covers.

In short: it sends a post's id when you click its button, and your question when you ask one. Nothing about you, your X account or what you scroll past ever leaves your browser. It stores nothing, asks for no permissions, and nothing is sold.

What the extension sends, and when

The list of posts the archive holds. On an x.com page with a video post, or a post linking a show's broadcast or a YouTube video, it downloads that list from search.lexthedev.com, at most once an hour. The request carries nothing about you or the page. Which posts get a button is worked out in your browser, against that list.
A post's id, when you click its button, to get that post's summary.
A post's id and your question, when you ask one.

That is all. It does not read or send your X account, your timeline, your messages, your cookies or your browsing history. Its requests carry no cookies, no referrer and no identifier. On x.com it looks only at each post's own id and whether the post has a video, a show's broadcast or a YouTube link, to decide where a button goes, and that never leaves your browser.

What it keeps on your device

Nothing. It has no storage permission and writes nothing to your browser's storage. The list of posts may sit in Chrome's ordinary web cache for up to an hour, the way any page's files do, and holds no information about you.

What happens to a question

To answer it, the question goes to the services that search the archive and write the answer: Voyage AI turns it into a search, Pinecone holds the index it is searched against, and a language model (Anthropic's Claude, through UsePod) writes the answer from what the search found. They receive the question to answer it, and nothing else of yours.
The server logs each question asked through the extension, its first 120 characters, with the post it was about, so we can see what people ask and fix wrong answers. That log line has no IP address and no account in it.
The same question about the same post within 24 hours is answered from a cache held in the server's memory, so it isn't paid for twice.

Your IP address

Like every web server, ours sees the IP address of each request, and our host (Render) keeps it in its request logs, with the address requested but not your question, on its own rolling schedule. The server also holds your IP address in memory, only to apply its per-minute and daily limits to each address, so no one address can use up everyone's answers. The daily count is cleared at midnight UTC, and the address is not written to our own logs or storage.

What we never do

Sell, rent or trade anything the extension sends.
Use it for advertising, or to build a profile of anyone.
Use it to decide creditworthiness or for lending.
Share it with anyone beyond the services named above, which use it only to answer.
Read it, except to keep the service working and fix wrong answers.

The use of information received from the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Permissions

None. It runs on https://x.com/* and talks only to https://search.lexthedev.com. The only other addresses it opens are the shows themselves, at a second, in a new tab and only when you click: X's broadcast player, an X post, or a YouTube video. No code is loaded from anywhere: everything that runs is in the extension, and the source is public on GitHub.

Children

The extension and the site are not directed at children under 13, and we don't knowingly collect anything from them.

Changes

If what the extension sends or what the server keeps ever changes, this page changes first, with a new date at the top.

Contact

Message @mbubbleSearch on X, or open an issue on GitHub.