---
title: "Privacy Policy — tweettoimage.com"
description: "What tweettoimage.com does and does not collect. Images and videos render in your browser and are never uploaded. Read what the link you paste actually touches."
url: "https://tweettoimage.com/privacy"
locale: "en"
site: "tweettoimage.com"
updated: "2026-09-07"
---

# Privacy policy

The short version: your renders are made in your browser and never uploaded, we have no account system for the web tool, and we run no advertising or third-party tracking. The longer version is below, and it is specific rather than boilerplate.

## What never leaves your browser

The image, video or GIF you export is drawn and encoded on your own device and saved straight to it. We never receive it, so there is nothing for us to store, inspect or lose.

The same is true of anything you add in the editor: watermark text, a logo image you choose, and every style setting are applied locally and are not sent to us.

## What does reach our server

A post has to be fetched before it can be drawn, so these things do go through us:

- The post link you paste. Our server looks the post up through a public third-party API and returns the text, author and media to your browser.
- A cached copy of that public post data, kept for up to 24 hours so that a popular post is not re-fetched for every visitor. It contains only what is already public on X, and it is keyed by the post, never by you.
- The post's images and video, which are proxied through our domain rather than loaded from X directly. This is a technical requirement — a browser cannot read a cross-origin image back off a canvas — and not a way of recording what you looked at.
- One exception on video: a small number of browsers can encode video but not audio. For those, and only when you ask for an MP4 with sound, the clip is rendered on our server instead, then deleted from the temporary cache on its normal expiry. Every other export is local.

## Logs, cookies and analytics

Our host, Cloudflare, keeps standard server request logs — IP address, timestamp, the URL requested — which are what make it possible to keep the service up and stop abuse. We do not join those to anything or build a profile from them.

We set no advertising cookies and run no third-party analytics or tracking scripts. Your theme preference is kept in your browser's own local storage, which never travels to us.

Rate limiting on the free server-side video fallback counts requests against a coarse network block rather than storing your address, and those counters expire on their own.

## Payments and API accounts

If you subscribe to an API plan, checkout is handled entirely by our payment provider, Polar. We never see or store your card details. What we receive back is your subscription status and the email you gave them, which is what an API key is issued against.

API keys are stored only as a hash. We cannot read your key back, which is why it is shown once at checkout and has to be kept somewhere safe on your side.

## What we do not do

We do not sell or rent your data, we do not share it with advertisers, and we do not use the posts you convert to train anything.

## Your rights and how to use them

You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. For anyone using only the free web tool the honest answer is usually that we hold nothing tied to you at all; for a subscriber it is your email and subscription record.

Email us and we will handle it.

[contact@tweet.download](mailto:contact@tweet.download)

## Related tools

- [Turn a tweet into an image](https://tweettoimage.com/)
- [Terms of service](https://tweettoimage.com/terms)
- [Contact us](https://tweettoimage.com/contact)
- [About tweettoimage.com](https://tweettoimage.com/about)