Your account and your data

Updated October 29, 2026. Fact Threader is an independent project run by the repository maintainer. It is not part of Meta or ICE.

Right now, this is a demo

The sample account is made up. Your choices stay in the page and disappear when you reload. The demo does not sign in to Threads, post anything, or save account details. It sets no application cookies.

There are no ads or analytics scripts. Cloudflare hosts the site and handles ordinary connection information, including IP addresses, to deliver and protect it.

When Threads sign-in opens

The app will ask for basic account access and permission to publish the posts you approve. It will save your Threads ID and username, an encrypted access token and its expiry date, your approved posts and schedule, and a short activity history. Your browser session will expire after seven days.

Those records let the app run the schedule you chose. It does not ask for followers, private messages, contacts, demographic information, or browsing history. It does not choose messages based on who you are.

Each post includes a source link and the words “Scheduled post.” New facts do not get added to your schedule automatically.

Pause or disconnect

Pause stops future posts. Something already being sent to Threads can still appear.

Disconnect and delete removes your saved token, schedule, approvals, sessions, pending jobs, and activity from the active database. It leaves posts already on Threads alone. You also need to remove Fact Threader in Threads app permissions to revoke its access there; deleting the local token is a separate action.

If you lose access, ask for a private contact route on GitHub. Do not put tokens, ID documents, or other private information in a public issue. A private support address and any deletion callback Meta requires must be in place before real accounts can connect.

How long records stay

Routine maintenance clears expired sessions and temporary sign-in records. Activity history is kept for up to 90 days. Deleting an account removes its active records, but infrastructure backups can take longer to expire. The backup retention window must be documented before sign-in opens.

Application logs use event names and random references rather than tokens or post text. Query strings are redacted in the Worker configuration. All other logging destinations must be checked before real sign-ins are allowed.

Fixing a fact

Report the fact ID and the supporting evidence. Changing or withdrawing a fact stops queues that include it until their owners review it again. Account owners decide how to correct anything already published.

Contributions and corrections on GitHub are public. Keep private information out of them.