Last updated 1 August 2026

Privacy Policy

The tool runs in your browser, so most of the data a product like this would normally collect simply never exists. Here is precisely what does, and where it goes.

1.The short version

  • There is no account. You can use the whole free product without telling us anything about yourself.
  • The posts you capture and the images you export never reach our servers. Everything is rendered on your own device.
  • We set one cookie, and only if you buy Pro. It remembers that this browser has a licence. It is not used to track you, here or anywhere else.
  • Our analytics is cookieless and aggregate. No profiles, no cross-site tracking, no advertising networks, and nothing sold to anyone — ever.
  • Payment details never touch us. Polar handles checkout as merchant of record; we receive your email address and an order reference.

2.Who is responsible

The data controller is SYRNIK LTD, 66 Paul Street, London, England, EC2A 4NA, United Kingdom — registered in England & Wales, company no. 17257080. This policy covers the website, the web editor and the Twitter Screenshot Chrome extension.

For anything in this policy, including a request about your data, write to support@twitter-screenshot.com.

3.The posts you capture

They are processed entirely in your browser. The extension reads the post you clicked from the page you are already looking at, and the editor draws it and exports the PNG on your own device. We have no upload endpoint, no image storage, and no copy of anything you make. Profile pictures and post images are fetched by your browser straight from X’s servers, not through us.

One qualification, stated plainly. The extension hands the captured post to the editor inside the page address. That address is sent to our host when the editor page loads, so it can appear in the standard, short-lived request logs every web host keeps for delivery and security. We do not read, analyse or retain those logs, and the editor strips the payload out of the address as soon as it has loaded, so it does not linger in your browser history.

4.What we collect

If you buy Pro
Checkout is run by Polar, who collects the name, email address, billing country and payment details needed to take the payment and charge the right tax. From that, we receive your email address, an order and customer reference, and your licence key. We never receive or store card numbers.
If you email us
We keep your message and address so we can reply and, if it turns into a refund or a bug, so we have a record of it.
Whenever anyone visits
Aggregate usage measurement through Vercel Web Analytics and Speed Insights: page address, referrer, approximate location from the IP address (country, region, city — the address itself is not stored), device type, browser and operating system, and page-load timings. Visitors are identified by a hash derived from the request that is discarded after 24 hours, so it cannot follow you across days, sites or sessions.
While you use the editor
Product measurement through PostHog, on the editor page only, so we can see which parts of the tool people actually use and where the Pro offer gets in the way. It records which settings were selected — the background, the effect, the export size and so on — whether an export succeeded, and whether you met the paywall and what you did about it. It never records the post you captured, its author, its images, your uploaded background or your watermark text. It keeps its state in memory for the length of one page view, so it sets nothing on your device and cannot recognise you on your next visit, and it builds no profile of anyone. The editor you can try on the home page is exempt — playing with it sends nothing at all.

That is the complete list. We do not build profiles, we do not run advertising or marketing trackers, and we do not sell or share personal data with anyone for their own purposes.

5.Cookies and browser storage

If you have not bought Pro, this site sets no cookies at all. Analytics works without them, which is why there is no consent banner to click through.

When you buy Pro, we set one cookie: ts_pro. It holds a signed token saying that this browser holds a valid licence, together with the customer reference we use to re-check it and the date it was last checked. It carries no name, no analytics identifier and no browsing history. It is strictly necessary — it is the entire mechanism by which the editor knows you paid, and there is no way to offer Pro without something like it. Technically: signed, HttpOnly, Secure, SameSite=Lax, and set to last up to 400 days, which is the maximum a browser will honour.

Two other pieces of storage stay on your own device and are never sent to us:

  • Your licence key, in the browser’s local storage, so that clearing cookies alone doesn’t lock you out of something you paid for.
  • Your licence key, in the extension’s own storage, so a new browser profile unlocks itself instead of asking you to paste a key. If you have Chrome sync switched on, Chrome replicates that value between your own signed-in devices through your Google account, exactly as it does your bookmarks.

You can delete all three at any time through your browser settings. Doing so removes Pro from that browser; re-entering your licence key restores it.

6.What the extension can and cannot see

The extension runs only on x.com and twitter.com. It cannot read any other site, because it is not permitted to load there.

On those two, it does one thing: when you press its button, it reads the post you pressed it on — the text, author, timestamp, counts and image addresses that are already rendered on screen — and opens the editor with them. It does not read your direct messages, your drafts, your notifications or your account settings, it does not act on your behalf, and it sends nothing to us.

Its permissions are the minimum that requires: activeTab and scripting to read the post in the tab you are looking at, and storage to keep your Pro licence key. There is no network access to anything but X’s own page and our editor.

7.Who else is involved

Five companies, each doing one job:

  • Vercel Inc. — hosting and content delivery, plus the cookieless analytics described above. Handles the request logs mentioned in section 3.
  • PostHog, Inc. — the editor measurement described in section 4, on their European service, so that data is stored in the EU and never leaves it. Their privacy policy covers what they do as our processor.
  • Polar Software, Inc. — checkout, invoicing, tax and refunds, as merchant of record. Their privacy policy governs what they collect at checkout.
  • Google LLC — distributes the extension through the Chrome Web Store, and synchronises your licence key between your own devices if you have Chrome sync enabled.
  • Our email provider — carries support correspondence to and from support@twitter-screenshot.com.

Some of these are based in the United States. Where personal data reaches them, the transfer relies on the UK and EU Standard Contractual Clauses or an equivalent approved safeguard offered by that provider.

9.Your rights

Under UK and EU data protection law you can ask us for a copy of your data, ask us to correct or delete it, ask us to restrict or stop a particular use, or ask for it in a portable format. You can also withdraw consent where we relied on it.

Email support@twitter-screenshot.com and we will answer within 30 days. There is little to find: for most people we hold an email address and an order reference, and nothing else.

Deleting your data ends your Pro licence, because the licence record is the data. We will say so before acting on the request.

If you think we have handled your data badly, you can complain to the UK Information Commissioner’s Office at ico.org.uk, or to your local supervisory authority in the EU. We would rather you told us first.

10.Children

The Service is not directed at children and we do not knowingly collect data from anyone under 13 (or under the minimum age in your country, where that is higher). If you believe a child has sent us personal data, email support@twitter-screenshot.com and we will delete it.

11.Changes to this policy

If what we do with data changes, this page changes with it and the “last updated” date at the top moves. Anything that materially affects you — a new cookie, a new recipient of your data — will be described here before it starts, not after.

The commercial terms sit in the Terms of Service.