Privacy

Last updated October 26, 2026

A plain-language description of what Twitter Viewer handles and why. Reading the free preview needs no account.

What we handle

If you create a Twitter Viewer account: your email address and name, and, if you sign in with Google, the basic profile details Google shares with us (name, email address and profile picture). We also keep purchase records, your credit balance and activity, the IDs of the tweets you unlocked, and basic technical logs needed to run and protect the service.

We never ask for or store your X password, login or session cookie.

Usernames and links you enter

To show a result we send the username or tweet ID you entered to our third-party data provider, which returns the public data. Your request also reaches our servers and hosting provider. We do not keep a history of what you look up for free, and the text you type into the lookup box is masked in our analytics. The address of a profile or tweet page you open can still appear in analytics reports (see Analytics below).

When you unlock tweets with credits, we record which tweet IDs you unlocked so that you are never charged twice for the same tweet.

When you download a video, we record which video it was, when, and how it was paid for (your free download or a credit), so that repeat downloads within 24 hours are not charged again and a failed download is refunded. We do not keep the video files.

Why we use your data

To run the service you asked for (show results, sign you in, process payments and deliver credits), to keep it secure and prevent abuse, to meet legal and accounting obligations, and, with your agreement where the law requires it, to measure how the site is used so we can improve it.

  • Contract: your account, purchases, credit balance and unlock records.
  • Legitimate interests: security, abuse prevention, fixing errors and keeping basic service statistics.
  • Consent: analytics and session-replay cookies where a cookie banner is shown.
  • Legal obligation: tax and accounting records for purchases.

Who we share it with

We do not sell your data and we do not show ads. We use a small number of service providers, each only for its job:

  • Our public-data provider: receives the username or tweet ID you look up and returns public data.
  • Stripe: processes card payments. You enter payment details on Stripe’s page, not ours, and we receive confirmation, the pack and the amount.
  • Google: sign-in with Google (if you choose it) and Google Analytics.
  • Our hosting and database provider: runs the site and stores account and purchase records.
  • Microsoft Clarity, if switched on: session replay and heatmaps (see Analytics).

Abuse prevention

To limit automated use we count requests per visitor using a short-lived identifier derived from the network address. These counters are kept for no longer than 24 hours.

Analytics

We use Google Analytics (Google) to understand how Twitter Viewer is used and where visitors come from, and we may use Microsoft Clarity (Microsoft) to fix usability problems. They receive the pages you visit, how you got here, your browser, device and screen size, and an approximate location derived from your IP address. When you are signed in we send Google an internal account ID, never your email address.

To tell which sources bring visitors who later sign up or buy, we remember in your browser the source of your first visit (for example a campaign tag, a search engine or a referring site) and of your current visit, and attach it to our usage events. We do this only where you have not declined analytics cookies.

Clarity records how you move through a page (clicks, taps, scrolling and cursor movement) so we can build heatmaps and replay sessions. We mask what you type into the lookup box, and we mask everything on sign-in, account and admin pages.

Google and Microsoft process this data under their own privacy policies. We use these reports in aggregate, never to identify you.

Cookies and local storage

We use a session cookie to keep you signed in, a cookie that remembers your cookie choice, a cookie (SITE_LOCALE) that remembers the language you last used so that links from your account pages lead back to it, and browser storage for the first-visit source described above and for resuming a purchase after you sign in. Our analytics tools set their own cookies (for example _ga from Google Analytics, and _clck and _clsk from Clarity) to tell visits apart.

Where we show a cookie banner, Clarity loads only after you accept, and Google Analytics runs without cookies until you do. You can change or withdraw your choice at any time with “Cookie Settings” in the footer. You can also block these cookies in your browser settings. Twitter Viewer does not use advertising cookies.

How long we keep it

Request counters used to limit abuse: up to 24 hours. Server logs kept by our hosting provider: a short period set by that provider, normally no more than 30 days. Account details, credit balance and unlock records: until you delete your account. Purchase and payment records: kept for the period tax and accounting law requires (generally up to seven years) even after an account is deleted. Analytics reports: kept by Google for the retention period we set in Google Analytics (14 months at most).

Your rights and choices

You can ask to see, correct, export or delete the personal data we hold about you, to object to or restrict how we use it, and to withdraw consent at any time, by emailing support@x-twitter-viewer.com from the address on the account. We reply within 30 days. Deleting your account removes your profile, balance and unlock records; unused credits are lost unless you ask for a refund first (see Terms).

If you are in the European Economic Area, the United Kingdom or California, you also have the rights your local law gives you, including the right to complain to your data protection authority. We do not sell or share personal information for advertising.

Read the Terms of Use

Where data is processed

Our providers may process data in the United States and other countries. Where required, transfers rely on the safeguards those providers offer, such as standard contractual clauses.

Security

Connections use HTTPS, payments are handled by Stripe, and passwords are stored hashed. No system is perfectly secure, so use a password you do not use elsewhere, or sign in with Google.

Age

Twitter Viewer is for people aged 18 or over. We do not knowingly collect data from children; if you think a child has given us data, email us and we will delete it.

Changes

If this page changes in a way that matters, we will update the date at the top and, for significant changes, tell signed-in users by email.