Privacy & contact.

Public posts and identity

Reading LGTM needs no account. Anyone can sign in with X to submit a post. LGTM then stores your public X account ID, handle, display name, and profile photo URL, and discards the temporary X access token after reading that identity. Each account can publish up to 20 posts in a rolling 24 hours, and nobody can submit their own post.

When you submit a post, your handle and your one-line pitch are shown publicly with the post on the board and in the daily archive.

Submitting a post does not use a device cookie or your IP address. LGTM keeps a signed device cookie and keyed hashes (HMAC-SHA256 with a server secret) of the device ID and IP address, never the raw IP, for the paid-bid flow, which is being retired. Paid bids are processed by Stripe, which handles your payment details.

Each published row stores an automatic title, the tweet's public text (the post text, long-post note, or X Article title, cleaned for display), source tweet ID and link, edit IDs, author attribution, submitter attribution, and publication time. LGTM shows the tweet text with attribution and a link to the post on X, and refreshes it so edits and deletions on X are reflected. X Article bodies are never stored. Readable source text passes transiently to the summary model through Vercel AI Gateway to suggest the title. The request asks the model provider not to use the text for training or retain it. Rows and public profiles persist until the operator removes them or the source becomes unavailable.

Visible picks appear on a public curator profile with the curator's public X identity, number of picks, authors featured, and qualifying outbound clicks from the last 24 hours. Each pick also shows its all-time qualifying click total. The weekly editorial spotlight can feature a curator and a visible pick. Downloadable share cards contain the reviewed LGTM title and public author and curator attribution. Hidden picks are excluded from profiles, spotlights, and cards.

Device, sign-in and click cookies

The HttpOnly device cookie holds a random ID signed by LGTM and lasts up to two years; it is used only for the paid-bid flow above. The sign-in cookie contains an opaque token and lasts up to 30 days. LGTM stores its hash and expiry, checks it before authorized actions, and revokes it when you sign out. An hourly cleanup job deletes expired database sessions in batches.

A separate opaque visitor cookie lasts up to one year. LGTM stores hashed visitor receipts to count at most one intentional outbound open per browser per tweet in a rolling 24 hours. These counts approximate visitors; they do not prove that someone read or engaged with a tweet. Known bots and previews do not count, and opens without JavaScript or through context menus may not count. An hourly cleanup job deletes receipts older than 24 hours in batches. Top still ranks the 24-hour count. Each pick keeps a running total of qualifying clicks after its receipt is deleted, and that total is what the feed shows beside the pick.

Analytics

The application includes DataFast and Google Analytics scripts for observing site use. These services are separate from LGTM's outbound click ranking. Hosting and analytics providers may process request and device information under their own policies.

LGTM records use of its copy, download, and share controls. Opening a share flow does not prove that someone published on X, and it does not increase a tweet's ranking.

Contact

For questions about your account data, contact daniel@indiethinkers.com with your X handle. LGTM does not take requests to remove posts from the board; the operator removes spam at their discretion. The terms cover what you agree to when you use LGTM.

Confirmed unavailable sources can be hidden by the operator's refresh job. Temporary lookup failures preserve a row for retry. Hidden submissions keep edit aliases and publication allowance records so removal cannot enable duplicate reposts or reset the posting limit.