Kaito reached out for an open dialogue after my findings tweet, and i was able to review the extension update before the open sourced release full before/after in the image, but the parts worth saying out loud: - a clarification on my original post: the claude, chatgpt and binance verifiers were in the shipped code but never live in the product. which verifiers actually run is decided server-side and those were never switched on. it was a dormant and never running feature. they're now removed from the extension entirely, which is the right call - the fix that mattered most to me is host permissions: 1.0.1 asked read/write perms for every site you visited. 1.0.2 asks for X and Kaito only, then prompts per site when you verify something the reason that matters isn't what the extension does today, it's that a future update could have widened what it reads with no chrome prompt or signal to the user at all (think a rogue employee) - they also fixed one i missed. the full page url was being sent, which on x means your search queries and your dm conversation ids. now stripped to the page type - they're also now inviting public review on future releases, which is the ACTUAL real fix here what didn't change, and shouldn't get lost: - the device fingerprint still uploads with your twitter id attached - the X feed logging, dwell times, clicks and follows are the same - agreeing to all the above is still required to use pulse all three were true before my post and are true now. the difference is the consent screen now says so, instead of listing device fingerprints as something it doesn't collect overall I would consider the extension a lot cleaner, or at least properly scoped kudos to @KaitoAI team: they engaged on every specific instead of going quiet. rarer than it should be in this industry