TruScope
ProductHow it worksPrivacyMethodologySupport
Log inAdd to Chrome
← Back to TruScope

Privacy policy

Your reading should stay yours.

A plain-language explanation of what stays on your device, what you choose to share, and which online services TruScope uses.

Last updated August 16, 2026
01
Local analysis

Normal article analysis does not use a TruScope analysis server.

02
Account controls

Accounts sync preferences—not article text or your local archive.

03
Explicit feedback

A complete record is uploaded only after you choose Submit feedback.

On this page

01Scope and our privacy model02Article access and local analysis03Information stored on your device04Accounts and synced preferences05Optional analysis feedback06Website, contact, and analytics data07Browser permissions and service providers08Security, choices, and requests09Changes and contact
01

Scope and our privacy model

This Privacy Policy covers the TruScope browser extension, the truscope.app website, account features, and the optional feedback service. TruScope is designed so ordinary article analysis happens on your device. We do not operate a remote article-analysis service.

The short version

Reading and analysis stay local by default. Data leaves your device when you choose an online feature such as account sign-in, synced preferences, optional feedback, or the website contact form.

02

Article access and local analysis

The extension can run on HTTP and HTTPS pages. When you ask TruScope to analyze a page—or enable an automatic analysis feature—it reads the current page to identify article text and metadata such as the title, byline, publication information, URL, and canonical URL.

The extracted content is processed by models and supporting logic bundled with the extension. Normal analysis does not upload the page URL or article text to TruScope. Results, evidence highlights, model details, and the local analysis archive are produced on your device.

TruScope may display publisher context from a registry packaged with the extension. That context is separate from the article analysis and does not alter the result.

03

Information stored on your device

TruScope uses Chrome extension storage for information including:

  • your most recent result and analysis status;
  • a local archive of up to 100 analysis records;
  • article text, evidence, model and methodology details inside that archive;
  • theme, notification, highlighting, automatic-analysis, and prompt preferences;
  • guest or account session information; and
  • short-lived navigation and model-lifecycle state.

You can export the archive as JSON or CSV. Exporting creates a file that you control and may contain full article text. Signing out, exiting guest mode, clearing extension data, or uninstalling the extension can remove locally stored information, subject to Chrome’s own browser and synchronization behavior.

04

Accounts and synced preferences

When you create an account, Firebase Authentication processes your email address and authentication credentials. For Google sign-in, Google and Firebase provide TruScope with your account identifier, email address, and sign-in provider information. TruScope does not receive your Google password.

Signed-in users can synchronize a limited set of extension preferences through Firestore: appearance, automatic analysis, smart prompts, highlighting, and notifications. Article text, analysis results, and the local archive are not stored in your account preference document.

Authentication sessions are stored using browser or extension persistence. TruScope’s website creates a short-lived sign-in bridge token so the installed extension can use the same Firebase account.

05

Optional analysis feedback

Feedback is separate from analysis and is never submitted merely by choosing a helpful or unhelpful rating. Before submission, the extension discloses that the following complete record will be sent:

  • your helpful or unhelpful rating and optional comment;
  • the article URL, title, byline, extracted text, and extraction metadata;
  • the result, evidence, diagnostics, thresholds, model version, and methodology version;
  • a random request identifier and Firebase user identifier; and
  • whether the session is an account or anonymous guest session.

Guests receive an anonymous Firebase identity only when they submit feedback. The server uses an HMAC-protected network identifier for abuse prevention and does not store the raw network address. Feedback records do not include the account email address.

Submitted feedback is stored in Firestore for product evaluation, security, deduplication, and abuse prevention. TruScope does not currently apply a fixed automatic deletion period to submitted feedback. Contact us if you want us to evaluate a deletion request.

06

Website, contact, and analytics data

If you use the contact form, we process the name, email address, subject, and message you provide. The form is delivered through Resend to TruScope’s support inbox so we can respond.

The production website may use Firebase Analytics to understand basic site usage and interactions such as selecting an install link. This can involve technical information and a pseudonymous installation identifier. Analytics and App Check are not required for local website development and are disabled on localhost.

07

Browser permissions and service providers

TruScope requests permissions for page access, local storage, notifications, alarms, scripting, and an offscreen document used to run bundled models reliably. Page access is used for article extraction, article prompts, and evidence highlighting—not to build a remote browsing history.

We rely on service providers for limited online functions:

  • Google Firebase for authentication, preference sync, hosting, feedback processing, and Firestore;
  • Google reCAPTCHA/App Check for website abuse monitoring;
  • Resend for contact-form delivery; and
  • Google Chrome Web Store for distribution and store analytics governed by Google’s policies.

These providers process information under their own terms and privacy commitments. We do not sell personal information or article content.

08

Security, choices, and requests

TruScope uses HTTPS for online features, Firebase Authentication, server-side token verification, restricted database rules, request validation, rate limits, and local session clearing. No security measure can guarantee absolute protection.

You can use guest mode, disable optional features, avoid submitting feedback, export or clear local records, sign out, or uninstall the extension. You may ask to access, correct, or delete account-related information by emailing us. We may need to verify your identity before completing a request, and some information may be retained where required for security, legal obligations, or resolving disputes.

TruScope is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

09

Changes and contact

We may update this policy as TruScope changes. The date at the top shows the latest revision. Material changes will be presented through the website, extension, store listing, or another reasonable channel.

Questions and privacy requests can be sent to truscope.help@gmail.com or through the contact page.

Questions or data requestsWe’ll help you find the right answer.
truscope.help@gmail.com
TruScope

See the signals behind the story—and the evidence behind every signal.

ProductProduct tourPrivacyMethodology
ConnectContactSupport the projectRelease notes
LegalPrivacy policyTerms of service
© 2026 TruScopeBuilt for thoughtful reading.