Privacy Policy
Last updated: October 20, 2026
1. Short version
Yeet does not have an account system and does not sell data. Draft text, images (when Copy Images is on), post URLs, and login cookies stay in your browser. Cross-posting runs locally — Yeet does not proxy posts through our servers. There is no Yeet backend that receives your content.
2. What Yeet reads
When you use Yeet, the extension reads the text in the X or Threads compose box so it can open the other site and inject that draft. If Copy Images is enabled, it also reads image files attached in the composer shell (not feed or timeline media) so it can attach them on the destination. That content is not uploaded to our servers.
Copy Videos / Copy GIFs toggles are visible in Settings but locked until that support ships. Yeet does not copy videos or GIFs today; if one is attached, it skips the cross-post with an alert and your source post still goes through.
The popup may check whether you are signed in by looking for X's auth_token cookie on x.com and Threads' sessionid cookie on threads.com or instagram.com. Yeet only checks that those cookies exist. Cookie values are not sent to us and are not stored on a server.
3. What is stored on your device
Yeet uses Chrome local storage (storage + unlimitedStorage) for:
isActive— whether the extension is turned oncopyImages,copyVideos,copyGifs— media preference flags (copyImagesis active; videos/GIFs remain locked)xContexts/threadsContexts— which composer types (new post, reply, quote, etc.) are allowed to yeet in each directionlastSavedAt— a local timestamp for settings changespendingYeetText— temporary plain text waiting to be injected on the destination site, then cleared after a successful postpendingYeetImages— temporary image payloads for the destination attach step, then cleared after a successful post (or skip)lastYeet— the last draft you yeeted: text, timestamp, source platform, and when available the destination post URL / id for the popup linkyeetProgress— local progress status shown in the popup (idle / yeeting / done / error)xAccountPremium— a local cache of whether your X account looks Premium, used only for character-limit checks
Draft text and images are stashed in extension storage rather than put in the intent URL, so links and Open Graph previews behave normally. Nothing here leaves your device. You can clear it by removing the extension or using Reset in Settings.
4. Network requests
Yeet does not fetch remote configuration or selector files. Platform UI selectors ship bundled with the extension build.
Opening X or Threads compose pages happens in your browser, as you. Yeet does not proxy those posts through our servers.
After a yeet, the extension may briefly watch the local browser response from X (CreateTweet) or Threads (configure-text APIs) to pick up the new post URL / id so it can show that link in the popup. That response is not sent to us.
5. What we do not do
- No selling or transferring user data to third parties
- No analytics SDKs, ads, or tracking pixels in the extension
- No use of your data to determine creditworthiness
- No remote JavaScript or Wasm loaded into the extension
6. Open source
Yeet is open source under the MIT License. You can read the code here: github.com/shivam-taneja/yeet. Product site: yeet.shivamtaneja.com.
7. Contact
Questions about this policy: shivamtaneja.com/contact.
