Privacy Policy

TweetShot — last updated 17 September 2026

TweetShot is an image editor that runs entirely inside your browser. This policy explains exactly what it does and does not do with your data.

The short version: TweetShot does not collect, transmit, sell or share any data. Every image you edit is processed locally on your own device using the browser's built-in <canvas> API. Nothing is ever uploaded to us or to anyone else.

What the extension accesses, and why

AccessWhyWhere it goes
Photos you choose to editTo display and edit them in the editorStays in your browser's memory. Never uploaded.
The composer page (x.com, twitter.com)To add the “Edit photo” button, detect attached images, and put the edited image back into the tweetStays on the page. No page content is transmitted.
Browser local storageTo remember your editor preferences (brush size, theme, saved looks) and, in the full-page editor, an unfinished edit so it survives a reloadStays on your device. Never transmitted.
Clipboard (write only)To copy the edited image when you press Copy, or as a fallback when the composer cannot be reachedWritten only when you ask for it. Never read.
Right-click menuTo add one item, “Edit this image with TweetShot”, on X/Twitter pagesLocal only.

What TweetShot never does

Fonts

The editor's typefaces (Archivo and IBM Plex, both open source under the SIL Open Font License) are bundled as files inside the extension and loaded with the browser's FontFace API. They are not fetched from Google Fonts or any other server at runtime.

Metadata

When you save an edited image, it is re-encoded by your browser. This removes the original file's EXIF metadata, including GPS location information. That is deliberate — but be aware it applies to any image you export.

Permissions explained

Children's privacy

TweetShot does not collect data from anyone, including children.

Changes to this policy

If this policy changes, the “last updated” date above will change and the new version will ship with the extension update.

Contact

Questions about this policy: open an issue on GitHub.