Refresh after an update
If Chrome reloaded the extension, refresh the page before scanning again.
Most problems have a specific recovery state in the extension. If you contact support, a request ID and the error label are usually enough to investigate.
If Chrome reloaded the extension, refresh the page before scanning again.
Chrome internal pages, the Web Store, local files, and protected browser pages cannot be scanned.
The free beta backend can take a short moment to wake after being idle. Use the displayed retry button.
The free beta includes ten scans per day. Cached results should not consume another scan.
| Message | What to do |
|---|---|
| You're offline | Reconnect, then choose Try again. |
| FactScope is waking up | Wait briefly and use the retry button. |
| Analysis took too long | Retry once. If it repeats, include the request ID in a support message. |
| Analysis provider unavailable | Try later; this is a service failure, not a verdict on the content. |
| This page cannot be scanned | Open a normal public http or https page. |
| Image could not be accessed | Try another copy of the image or open the original post. |
| No checkable factual claims | Try a page containing a concrete statement about an event, person, number, policy, date, or place. |
Matching reporting can help investigate a claim without confirming every exact detail. FactScope reserves supported or contradicted findings for stronger, inspectable evidence.
A cache can miss when the extracted content, canonical URL, or analysis version changed, or when the stored result expired. A genuine cache hit should return quickly and should not reduce the daily quota.
No. It means FactScope did not find qualifying coverage during that scan. New, local, paywalled, or poorly indexed reporting may be missing.
Yes. Open Privacy & data in the extension to clear local history, disable optional telemetry, or delete installation-linked server data. See the privacy policy for temporary abuse-prevention records.
No. Start with the error label, request ID, extension version, and whether it was a page or image scan. Do not send private or sensitive content.
Include the extension version, approximate time of the scan, error label, and request ID if one was shown. Support is currently handled by the project maintainer, so replies are not guaranteed to be immediate.
Do not include private page text, credentials, or personal documents.