A control room for 𝕏

How it works

Columns are refreshed by a central reader, so ten people following the same account cost 𝕏 one request, not ten. That is why you can follow public accounts straight away, with no account of your own: the reader is already fetching them. Keyword columns, your home feed and the AI need your own 𝕏 session. While you are connected, the part of your 𝕏 quota you do not use helps refresh everyone’s columns: at least 60% of your searches and 80% of the rest always stay yours, and your home feed and private columns are never used for anyone else.

There are two ways to give it one. The browser extension is the short one: it hands over the 𝕏 session this browser already has, so there is no login screen and nothing to type. Otherwise you can sign in here, and FeedScope signs in for you once, in a browser it runs, and keeps only the session it gets back — the same two cookies your own browser would hold. Your password is used for that sign-in and then discarded; it is never stored. Either way the session stays in your browser, not on our server, unless you choose to lend your quota while away too (below).

If you sign in here

Use the account’s e-mail: 𝕏 sends a code to it and you enter it here. With the @username, 𝕏 asks for the password instead and often refuses that from a place it does not know, which a server never is. Accounts 𝕏 has flagged cannot be verified at all; use another one. The extension has none of this to get wrong, which is why it is the one we suggest first.

Whichever way you connect, use a 𝕏 account you keep for tools rather than your main one. The full terms are in the sign-in window, before you type anything.

What we store

• Your workspace: the columns, searches, filters and layout, keyed by your 𝕏 account id, so it follows you across devices. With it, which columns you open and how often, and when you last saw each one, to show you what is new.
• Your bookmarks, the threads you save (with your account; without one they stay in the browser) and your "Tell me when" alerts.
• Your Telegram link, if you set one up: the chat id and your Telegram @username. For the morning brief, its hour, time zone and language. Disconnecting, or sending /stop to the bot, stops the messages; ask if you want the link deleted too. If you subscribe to briefs from the bot (the links on the brief pages, or /brief): the chat id, your Telegram id, the topic, hour and language, until you send /stop.
• Browser notifications, if you turn them on: the address your browser gives us to reach it and its keys, your language and time zone. A notification travels, encrypted, through your browser maker’s push service (Google, Mozilla, Apple, Microsoft). Turning them off in the Alerts panel, or signing out on that browser, deletes the address. With alerts on, your columns keep being read while FeedScope is closed, up to 30 days after you last opened them.
• The public posts your columns collect, in a shared archive that feeds the briefs, the analytics and the AI answers. Posts, and the briefs, translations and sentiment analyses made from them, are kept 90 days; the public daily brief pages (/b) stay online as an archive. When a post of an account column vanishes from X we ask X about it, and so for an account X stops showing and, the day after, for the posts the public briefs cite. If it is gone (deleted, or its account suspended or closed), it leaves the archive, the public pages, the briefs and the AI answers (past days’ brief pages catch up within the hour); the text of briefs already written stays. Readers who already had that column when the post went still see it there, marked as deleted, until 90 days after it was posted; readers who add the column later do not. A deleted post we have not checked yet, or one from an account that later turns protected, stays for the 90 days: if you wrote it and want it gone sooner, tell us from the feedback entry in the Help menu.
• The questions you ask the AI and its answers: 7 days, or for as long as the link stays shared if you share one. For the AI features (briefs, translations, answers, sentiment, crisis reply drafts, the PDF report), the columns’ words, the posts and your questions go to the model provider (through OpenRouter). Briefs you share: your account id, the column and the brief, until you ask us to take them down.
• A usage log (sign-ins and how you signed in, which tools were used and when, what the AI features you use cost, and the words of your archive searches, your AI questions and the columns you use the tools on), to keep the service running and to see what is worth improving: the words go after 90 days, the rest after 12 months, or sooner if you ask.
• The messages you send us through the feedback form, and the contact if you leave one.
• Protected accounts you follow: their column is read with your session, and their posts stay in your browser. We do not store them, show them to anyone else or send them to the AI.
• Page visits, counted with Google Analytics only if you accept: Google receives the page’s address without its private parts (no parameters; shared links and personal columns masked), its title and the browser’s technical details. No advertising signals.
• Server logs, kept up to 15 days: the web server notes the IP address and the page requested, which can include the words searched; the application logs its work (for example the words of the columns it refreshes, and the IP address of a request turned away for going over a limit). Nightly backups hold a copy of the data for up to 17 days.
• A fingerprint of your session (a hash, not the session itself) next to your 𝕏 account id, so you stay recognised when 𝕏 briefly fails to answer. It is dropped after six months unused.
• When you hand your session to a second device, the encrypted bundle: usable for ninety seconds; your browser holds the key, and we hold bytes we cannot read. The first device to use them empties them; if nobody does, they are gone within a day.

The browser extension

“Connect to FeedScope” reads the two session cookies 𝕏 already set in your browser (auth_token and ct0). While FeedScope’s Connect window is open, the page asks the extension whether you are signed in to 𝕏, and the extension answers only yes or no. It hands the two cookies to the FeedScope page you have open only when you click to connect, so you are signed in without typing a password. It reads nothing else, keeps no copy, and sends nothing to any server of its own; the only network request is the one FeedScope itself makes to its own backend, the same as any signed-in visit. Removing the extension, or disconnecting in FeedScope, ends it.

We do not store your password, we do not read your direct messages, and we do not sell or share any of this, except what the AI provider receives for the AI features (the morning brief too) and, if you accept, the page visits Google Analytics counts. Disconnecting removes your session from the browser; ask and we delete the rest.

Google Analytics runs only if you accept it. Change your choice

Costs and limits

FeedScope is free while it is being tried. The public daily briefs need no account. The AI features are rate-limited per person so nobody can run up the bill.