Is Delete X Tweets - Remove Twitter Posts safe?

Clean risk

Delete X Tweets captures X/Twitter API headers and reuses them to call X/Twitter GraphQL endpoints.

While you use it on x.com or twitter.com, its service worker records UserTweets and UserByScreenName GraphQL request URLs and request headers in Chrome local storage. The content script later reads those saved headers, including authorization and CSRF-related credentials, and uses them with credentialed fetches to X/Twitter GraphQL APIs to load profiles/tweets and delete tweets after user action.

Browser Agentsv2.9.0Chrome Web Store
0Risk
Who publishes it

Browser Agents - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
Browser Agents

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

Where it sends data

Destinations our analysis observed Delete X Tweets - Remove Twitter Posts contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • x.com

    Delete X Tweets - Remove Twitter Posts sends data to x.com. 22 other extensions we have analysed send data here.

  • twitter.com

    Delete X Tweets - Remove Twitter Posts sends data to twitter.com. 8 other extensions we have analysed send data here.

Updated 30 September 2026hlnlgomflnboogkaampmdhiaifjkfcgc