LAST UPDATED OCT 14, 2026

Privacy Policy

We collect as little as we can: what you search, and, only if you buy, your Google account ID, email address and name. Two analytics tools measure how pages are used, and we note how you found us. One browser setting switches all of that off.

This policy covers the Deleted Tweet Finder website, operated by Deleted Tweet Finder (“we”, “us”).

What we collect

  • Your searches. The X/Twitter username or tweet link you enter, and the results we build from saved snapshots of public tweet pages (counts, sample tweets, tweet records). Searching doesn't need an account.
  • Google sign-in. Only when you sign in to buy or open an archive: your Google account ID, email address and name. We request only the basic openid, email and profile scopes and don't store your profile photo. The sign-in tokens Google returns are stored encrypted and never used to access other Google data.
  • Purchases. Payments are handled by Stripe. We keep the order record: your account, the username bought, amount, currency, Stripe payment references, status and dates. We never see or store your card details.
  • How you found us. When you open the site, your browser keeps a short note of how you arrived: the website that linked to us (its domain only), the first page you landed on (its path only, never a query string and never the private part of an archive link), and any campaign tags in the link, such as utm_source=chatgpt.com. The note is kept in your browser's local storage, as an item named dtf_attr. After 30 days we no longer use it, and your next visit replaces it. Where Google Analytics is loaded, a few short fields from it are added to every event we send it, so its reports can be split by source: a channel such as search or ai and the referring site or campaign name, for your first arrival and your latest one, and the path of the first page you landed on. The note itself is sent to us only when you start a purchase, and is then saved with that order, so we can tell which sites and channels bring people who buy. It never holds a username, tweet, link or email address, is not a cookie, and carries no ID. A browser that sends Global Privacy Control or Do Not Track gets no note, nothing is added to analytics events (neither tool is loaded for it), and nothing is saved with its orders except that a privacy signal was set.
  • Technical data. A sign-in session cookie (HttpOnly) and, for security, the IP address and browser type recorded with your session and in server logs. We also use your connection's IP address for a country lookup on our own server, so we can show the European price in euros and other prices in US dollars. The lookup uses an offline database, sends no visitor data to its provider and stores no additional IP address or country record. A short-lived signed price quote stays in page memory and is sent back when you start checkout, so Stripe charges the price you saw. This functional price selection continues when analytics and source notes are switched off.
  • How pages are used. Microsoft Clarity records clicks, scrolling, mouse movement and a replay of how each page looked in your browser. Google Analytics records which pages you open and which buttons and links you use, as a short fixed name for each one. Both set cookies to tell one visit from another. What you type, and everything on archive and link-result pages, in the sign-in and My archives panels, is masked before it leaves your browser. The events our own code sends never carry a username, tweet, link or email address — but a page's address in your browser bar can contain the account you searched or the tweet link you checked, and that address is not fully masked by either tool. See Site analytics below, including what that gap is and how to switch both tools off.

How we use it

  • To run searches and build the archives you unlock.
  • To keep each unlocked archive private to the Google account that bought it.
  • To email you when an archive is ready, or when a payment is refunded.
  • To handle refunds, support requests and removal requests.
  • To prevent abuse and keep the service secure.
  • To show and charge the same regional price and currency.
  • To see how pages are used, so we can fix what confuses people.
  • To see which sites and channels bring people who buy.

We don't sell your data, advertise to you, or publish anyone's searches. Site analytics, described below, are the one place where other companies receive information about your visit for purposes of their own.

Who else processes it

  • Snapshot lookups. To build results, our servers look up saved snapshots of public tweet pages for the username or tweet you searched. Only that username or tweet is used; your IP address and account details are never included. Images reach you either through our own servers or from our own storage; your browser is never sent to the place a snapshot came from.
  • Google for sign-in, Stripe for payments, and Resend for archive-ready and refund emails. When there is a “how you found us” note, Stripe also receives a short label with the payment for your first arrival and, if it differs, your latest one: a channel such as search or ai, the referring site or campaign name, and the path of the page you landed on. If a privacy signal was set, the label only says so.
  • Service providers that store and process data on our behalf: Google Cloud (hosting), Supabase (database), Inngest (background jobs) and Cloudflare (image storage for unlocked archives).
  • Microsoft (Clarity) and Google (Google Analytics) for site analytics. These two are the exception on this list: both may also use what they collect for purposes of their own, not only on our behalf.

Apart from the two analytics providers, these providers may only use the data to provide their service to us. We may also disclose information if the law requires it, or to protect the service and its users from fraud or abuse.

Site analytics

To see which parts of the site work and which confuse people, we use two tools: Microsoft Clarity and Google Analytics. Both record the address of each page you open, along with your screen size, browser, language and roughly where in the world your connection comes from.

Microsoft Clarity adds clicks, scrolling, mouse movement, and a replay of how the page looked while you were on it. Clarity masks anything typed into a field before it leaves your browser, and we mask more on top of that: every archive page, every saved link-check result, the sign-in and My archives panels, and the account button. The username you searched, the tweets in your results and your email address, as displayed on the page, are replaced with placeholder characters and never reach Microsoft that way. Our Clarity setup does not mask page, referring or clicked addresses: the free preview, archive and single-link-check pages can carry the account you searched or the tweet link you checked in the browser's address bar, and Clarity records that address as-is. Full results still require signing in with the account that bought them, so that part of the address never grants access on its own.

Google Analytics records no replay and no mouse movement. The events our own code sends it carry a short fixed name we chose in advance — for example that a search was submitted, that an unlock button was pressed, that checkout was opened, or which export format was chosen — never the text on the page, and never a username, tweet, link or email address. Every event also carries how you found us, as the short fields described under “What we collect”; Clarity is not given them. Before our code sends a page's address, it removes the entire query string and any fragment and replaces the private part of an archive link with the word redacted; the same filtering applies to the referring address, and an external referrer keeps only its origin. On October 14, 2026, we disabled Google Analytics' enhanced measurement, including automatic browser-history page views, site-search detection, outbound clicks and form interactions. Google Analytics can still generate basic visit, session and engagement events independently of the events our own code sends; those automatic events are not controlled by our event filter. When a purchase completes we also send that one happened, the amount, and an order reference that means nothing outside our own records, and how the buyer found us as that order saved it.

Clarity sets _clck and _clsk from this site, and MUID, CLID, ANONCHK, MR and SM from Microsoft. Google Analytics sets _ga and _ga_RDZLWDG80J, both from this site. Microsoft receives its data as an independent controller and may use it for its own purposes, including advertising profiles, under the Microsoft Privacy Statement. What Google may do with what it collects is set out in How Google uses information from sites that use its services; we have switched off the settings that would let it be used to build advertising audiences (Google Signals and ad personalization). Google works out an approximate location from your IP address and states that it does not log or store the address itself. Neither company is sent your name or email address, and apart from the purchase record described above, nothing we send either one is tied to an order.

Microsoft keeps replays for 30 days and aggregated click data for 9 months. Google keeps the event-level data behind its reports for 14 months, and the aggregated reports for longer.

To switch both off, turn on Global Privacy Control or Do Not Track in your browser or a privacy extension. We check for both before anything loads: if either is set, neither tool is loaded and none of the cookies above are set. Blocking clarity.ms and googletagmanager.com in a content blocker stops them as well. Blocking third-party cookies is only a partial measure: it stops the Microsoft cookies listed above, but _clck, _clsk, _ga and _ga_RDZLWDG80J are set by this site and are not affected. These are the only two analytics tools on the site, and we run no advertising tags.

How long we keep it

Free previews and link checks7 days, then deleted automatically
Unlocked archives and exports30 days from payment, or sooner if you delete them
Shared processing cacheUp to 30 days. Used only by our servers to avoid re-fetching the same account; never shown to anyone without a valid order
Account detailsUntil you delete your account
Order and payment recordsAs long as we must keep them for tax, accounting and payment disputes
How you found usIn your browser; we stop using it after 30 days, and your next visit replaces it. If you start a purchase, it is saved with that order until you delete your account. Stripe keeps its own copy of the short label with the payment record, and Google Analytics keeps the short fields with its events (14 months)
Site analyticsHeld by Microsoft: session replays 30 days, aggregated click data 9 months. Held by Google: event-level data 14 months, aggregated reports for longer

Your choices

  • Delete an archive at any time from its page or from My archives. Its results and exports are removed right away.
  • Delete your account from My archives. This removes your account details, your access to every archive and the “how you found us” note saved with your orders. Payment records are kept.
  • Turn on Global Privacy Control or Do Not Track and we won’t note how you found us. Clearing this site’s data in your browser removes a note that is already there.
  • Ask us for a copy of your data, a correction, or deletion through the Contact & Removal page.

US state privacy rights

Depending on where you live in the United States, you may have the right to know what personal information we collect, use and disclose about you, to get a copy of it, and to have it corrected or deleted. We honor these requests from anyone who asks, and we won't treat you differently for using these rights. The categories we collect are the ones listed above: identifiers (Google account ID, email address, name), commercial information (orders), and internet activity (searches, IP address, browser type, the site analytics described above and how they found us). We collect them from you, from Google when you sign in, and through Microsoft Clarity and Google Analytics, for the purposes described in this policy.

We don't sell personal information for money, use sensitive personal information to infer anything about you, or disclose personal information to third parties for their own direct marketing. Letting Microsoft Clarity collect the site analytics described above may count as “sharing” for cross-context behavioral advertising under some state laws, because Microsoft may use what it collects for its own advertising. For Google Analytics we have switched off the settings that would put it in the same position. You can opt out of both at any time, and a Global Privacy Control signal from your browser opts you out automatically.

To make a request, email support@deletedtweetfinder.org from the address on your account, or have an authorized agent contact us with your written permission. We'll confirm your identity through that email address and respond within 45 days.

Do Not Track and Global Privacy Control

We don't track you across other websites ourselves. For the two analytics tools we do run, a browser Do Not Track or Global Privacy Control signal counts as an opt-out: neither Microsoft Clarity nor Google Analytics is loaded at all, and neither sets a cookie. The same signals stop the “how you found us” note: nothing is written to your browser, a note already there is deleted, and if you then buy, the order records only that a privacy signal was set. Nothing else changes — searching, signing in, buying and opening archives all work the same.

Security

Data is sent over HTTPS, sign-in tokens are stored encrypted, and unlocked archives are available only to the Google account that bought them. No system is perfectly secure, so please contact us if you notice a problem.

Children

The service isn't directed to children under 16, and we don't knowingly collect their data.

Changes

If we change this policy, we'll update the date above. Material changes will be noted on this page before they take effect.

Contact

Privacy questions and requests: support@deletedtweetfinder.org.