Last updated July 2, 2026
The extension has no server of its own — there's no shared account, no bill I pay on your behalf, and nothing routed through anyone else's infrastructure. Your key talks directly to Anthropic. It also means you're never sharing usage or cost with anyone else: what you look up is yours alone. Setup takes a couple of minutes — see install & setup.
No, and there are no plans to charge money for it or show ads in it.
No. Threads doesn't have a "who viewed your profile" feature, so a lookup looks exactly like you visiting their profile page in a browser tab — because that's functionally what's happening behind the scenes. See the privacy policy for the full breakdown of what goes where.
Everything the extension stores — your API key and the local results cache — lives only in Chrome's local storage for that extension. Uninstalling deletes it immediately. Nothing was ever stored anywhere else to begin with.
It's Claude's frank read of a person's recent public posts and replies — genuine, mixed, or suspicious, plus trait chips and a plain-language summary. It's meant as decision support for whether engaging with someone seems worthwhile, not a moral judgment or a character reference: it's one AI's opinion of a small, recent sample (see known issues for the caveats), and verdicts are private to you.
Yes — hover your own username anywhere it appears on Threads (in a comment thread, a followers list, etc.) and it works the same as looking up anyone else. A dedicated one-click "Analyze me" shortcut is on the wishlist but not built yet; check the changelog for what's shipped.
Please do! It's a public listing now, so anyone can install it straight from the Chrome Web Store — or send them to this site if they'd like the fuller story first.
Bug reports and feature suggestions are very welcome! Email me at adam@thriendorfaux.com — the easiest way to attach screenshots with no restrictions. A Threads DM to @thatadamguy works too, though I'll need to approve your first message before you can attach media there (a Threads message-request limitation, not a personal thing!). Either way — I have a day job, so thanks in advance for your patience :)
If you find a security vulnerability, I'd appreciate hearing about it privately first, so I can fix it before anyone else stumbles onto it.
The extension has to read posts that Threads only renders client-side, which it does by briefly opening background tabs and scripting them — machinery built on Chrome's extension APIs specifically. Safari has its own separate extension system that would need its own build, and mobile browsers (plus the Threads apps) don't support extensions at all. Nothing's ruled out forever, but it's not currently planned.