FactButcher Privacy Policy

Last updated: 2026-07-01

This Privacy Policy describes how the FactButcher web app, account dashboard, Chrome extension, Telegram Bot, and FactButcher API (the "Service") handle data when you use FactButcher.

Who is responsible

The Service is operated by Teplitsa (Teplitsa of Social Technology, te-st.org) ("we", "us"), which is the party responsible for the personal data processed through the Service. For any privacy, support, or data-deletion request, contact us at support@factbutcher.com.

Data we collect and handle

  • Submitted text: The text you highlight, submit, or send to the bot for fact-checking.
  • Account data: If you register for an account, we process your email address, plan status, API keys, and subscription status. Payments and billing details are handled through Stripe.
  • Session data: The web app, dashboard, and Chrome extension may store sign-in session tokens locally so you stay signed in.
  • Telegram data: If you use the Telegram Bot, we may store your numeric Telegram user ID separately from the texts you send for fact-checking. We use it to operate the bot and process support or data-deletion requests. We do not store your Telegram username, first name, last name, or phone number in this registry.
  • Usage analytics: For request analytics, quota, and rate limiting, we use pseudonymous hashed identifiers instead of raw account, Telegram, or browser identifiers.

How we use data

  • Provide the Service: Return fact-checking results for the text you submit.
  • Account management: Keep you signed in, manage subscriptions, and enforce plan limits.
  • Telegram support and deletion requests: Process support and data-deletion requests related to Telegram bot usage.
  • Service improvement: Monitor reliability, understand usage, and improve result quality.

How we protect request analytics

For request analytics, we use pseudonymous hashed identifiers instead of raw account, Telegram, or browser identifiers. This helps us group usage and improve the Service without storing real contact identifiers in request analytics.

The Telegram contact registry is kept separate from fact-checking queries. It does not store request text, trace IDs, analytics hashes, or usage history.

Data storage and retention

  • The web app stores sign-in session data and guest browser identifiers in local browser storage.
  • The Chrome extension stores its sign-in state, installation identifier, and temporary request state in Chrome extension storage.
  • The Service may log submitted text, fact-checking results, and pseudonymous identifiers to operate and improve the Service.
  • The Telegram contact registry stores Telegram user IDs separately from fact-checking queries.
  • We retain logs and registry data only as long as needed for these purposes.

Data sharing

  • We do not sell your data.
  • Submitted text may be processed by third-party AI or fact-checking providers used by the Service, such as OpenAI, Google Fact Check Tools API, and Perplexity AI.
  • Analytics are processed through Langfuse.
  • Authentication and account data are processed through Supabase.
  • Payments are processed through Stripe.
  • We use infrastructure providers to host and operate the Service.

Security

  • Data is transmitted over HTTPS.
  • Sign-in session tokens stored by the web app, dashboard, or extension remain in local browser or extension storage on that device.
  • The Chrome extension stores its local auth state separately from websites.

Your choices

  • Sign out in the web app, dashboard, or extension, or clear your browser/extension data, to remove local stored sign-in data.
  • Contact us to request deletion of your account data, removal of your Telegram user ID from the contact registry, or deletion of service-side logs where applicable.

Contact