Privacy policy

Updated October 27, 2026

This notice describes the data used by TweetLens's archive website, requests, sign-in, purchases and email support. Contact hello@tweetlens.com with questions for Michael at TweetLens.

Archives and public browsing

The free public collection can be read without an account. Archives contain captured X posts and related context, which can include usernames, account and post identifiers, text, dates, engagement counts, photos and videos. A captured copy can remain available after the original post disappears from X. Coverage varies by account and capture date.

Purchased archives are made available through access grants to the relevant TweetLens accounts. Buying or requesting an archive does not automatically publish it in the free collection.

Requests, purchases and sign-in

For an archive request, we record the requested account, your email address, the request date and source, purchase-update preference and review status. We use these to review the request, reply, and send relevant availability updates.

For a purchase, we also keep your X account identifier, the archive and agreed scope, price, delivery deadline, access period, payment references and status, and delivery/refund notice records. These connect payment to the correct account, provide access, process refunds and resolve problems.

X sign-in provides your numeric account ID and username. The X consent screen includes read-access scopes; the sign-in code uses the returned access token for an account-identity lookup, not to post or read direct messages. X passwords are entered on X, not in TweetLens forms. A required session cookie keeps your sign-in and form protections; sign-in recovery records are also stored on the server. Logging out clears the TweetLens session cookie.

Payments and service providers

Browser checkout is hosted by Stripe. TweetLens sends the order reference, archive description, amount and your delivery email to Stripe, and receives payment status and references. The TweetLens order form does not collect a full card number or card security code.

Agent card payments use Stripe shared payment tokens. TweetLens stores the scoped payment token and payment request in restricted server-side retry records so an interrupted attempt can be recovered without starting another payment. This is separate from the browser checkout flow.

Website hosting, analytics, payment and email infrastructure process the data needed to run these services. X and Stripe also handle data under their own policies: X privacy policy and Stripe privacy policy.

Email and support

Request confirmations, relevant archive offers, delivery and refund messages are sent by email. Copies of transactional messages and notifications of incoming mail go to Michael, who operates the service. Email addresses and message content are kept in mail and support records.

Email support uses automated classification, drafting and review tools, including Claude. Sender information, subject, message text and conversation context can be sent to that service to prepare a reply, as well as reviewed by Michael. Do not send passwords, full payment-card details or unrelated sensitive documents by email.

Website logs and analytics

Web-server logs record requests, including IP address, browser information, requested URL and referrer. We use Umami analytics to understand visits and use of the site. Its browser script sends page titles and URLs, referrers, language, screen size and interaction events; URLs can include query parameters and fragments.

The archive reader also records product events that can include the account being viewed, search text, view and filter choices, and clicked links. Avoid entering confidential information in search fields. This extra reader-event logging respects a supported browser Do Not Track signal; that signal does not switch off all page analytics or server logs.

Retention and choices

There is no single automatic deletion deadline for request, purchase, payment-recovery, correspondence, analytics and operational records. Records and backups can remain after an archive's viewing period ends. The access period shown in an offer describes when you can view the archive; it is not a promise that all related records or copies are deleted at that time.

Email hello@tweetlens.com to ask about your information, request correction or deletion, stop archive-availability updates, or raise a concern about archived content. Include only enough information to identify the request or order. We may need to verify that you are the account holder and review which records are needed for payments, disputes, security or other obligations. A request does not itself erase records or change a paid order.