We use data only to run the fact-checking service.
FactCheckRadar checks claims, tweets, images, screenshots, and sources that you choose to submit. This policy explains what we collect, why we collect it, and what we do not do with it.
Last updated: April 24, 2026
Short version
When you ask FactCheckRadar to check something, we send the selected text, image, page URL, and related context to our backend so we can create the report. We do not sell your data. We do not use your submitted content for unrelated advertising. We do not collect browsing history in the background.
Data we collect
Depending on what feature you use, FactCheckRadar may collect and process:
- Selected text and surrounding context: the claim, tweet text, or article text you ask us to fact-check.
- Page information: the page URL, page title, source URL, or tweet URL connected to the check.
- Images or frames: image URLs, selected images, screenshots, or captured video frames when you ask us to investigate an image or visual claim.
- Report data: generated verdicts, summaries, reasoning, sources, and recheck schedules.
- Account and billing identifiers: an extension identity, session token, credit balance, payment status, and related billing records.
- Email address: only if email verification is enabled and you enter your email for verification.
- Basic diagnostic events: status logs that help us understand whether a fact-check started, failed, completed, or needs recovery.
- Website analytics: basic website visit information, such as page views and referral information, to understand traffic and improve the public website.
Why we use this data
We use this data to provide and maintain FactCheckRadar:
- Generate source-backed fact-check reports.
- Find and parse public web sources relevant to the claim.
- Show your local reports and published public reports.
- Run deeper checks and scheduled developing-story rechecks.
- Manage credits, billing, email verification, abuse prevention, and service limits.
- Debug failures, recover stuck jobs, and improve reliability.
- Measure public website traffic and understand which public reports are being read.
When reports become public
Fact-check reports are private by default inside your extension. A report becomes publicly visible on the FactCheckRadar website only when you choose to publish or share it. Published reports may include the claim, summary, verdict, source links, and related context needed to understand the fact-check.
Third-party services
To create reports, send verification emails, process payments, and measure public website traffic, FactCheckRadar uses trusted third-party services. These may include AI model providers, web search and page parsing providers, email delivery providers, payment processors, hosting providers, database providers, and analytics providers. We send them only the information needed for the requested feature to work.
What we do not do
- We do not sell user data.
- We do not use submitted claims, images, or page content for unrelated advertising.
- We do not collect all browsing history.
- We do not read pages you did not interact with for a fact-check feature.
- We do not publish your report unless you choose to share or publish it.
Local extension storage
The extension stores some information locally in your browser, such as report records, billing identity, client session tokens, pending recheck notifications, and settings needed to keep the extension working. This local data stays in your browser unless it is sent to our backend for a feature you use.
Security
We use HTTPS for communication with our backend and keep access tokens in Chrome extension local storage. We limit access to operational systems and use the data for the service purposes described in this policy.
Data retention
We keep submitted fact-check data, billing records, published reports, diagnostics, and analytics for as long as needed to provide the service, prevent abuse, maintain records, debug problems, and operate public article pages. Published reports may remain public until removed or unpublished.
Your choices
- You can choose not to publish a report.
- You can remove the extension from Chrome to stop extension-side collection.
- You can avoid entering an email unless verification is required for your account.
- You can contact us through the Chrome Web Store listing or the FactCheckRadar website if you need help with privacy or published content.
Changes to this policy
We may update this policy as FactCheckRadar changes. When we make important changes, we will update this page and the date above.