Tweet Deletion Tools Compared on Privacy: On-Device or Uploaded

The article "Tweet Deletion Tools Compared on Privacy: On-Device or Uploaded" compares three different architectures for tweet deletion tools, focusing on where the analysis takes place, the access needed, and how long data is kept. On-device analysis keeps the archive in browser memory, never uploads anything, and has no access granted.

Cloud bulk deletion tools send the archive or credentials to a server, requiring read and write account access, and may retain data for a period set by the vendor. Direct deletion via platform API also requires full scope access. The right choice depends on the content of the archive and the user's comfort with the vendor handling that content.

Permission scope refers to the ability to act as the account, with actions such as posting, deleting, changing avatar and bio, reading direct messages, and inspecting follow lists. A broader permission scope increases the potential impact of a security incident. Retention promises should answer specific questions about how data is stored, when it's removed, and whether backups and logs are purged.

A policy that answers these questions provides measurable privacy assurances. The article suggests a checklist to evaluate tools, focusing on analysis location, permission scope, retention period, and revocation options. When choosing a tool, starting with an on-device analysis that costs nothing and uploads nothing can help determine what's in the archive before deciding if speed is worth granting access to a third party.