Privacy Policy
Last updated November 18, 2026
Introduction
We value your privacy and are committed to protecting any data handled by
the MarketInspection Chrome extension and the service behind it. This policy
explains what is processed, what is stored, and what is never sent anywhere,
in plain terms.
Information We Process (Not Collect Locally)
When you run an analysis, the extension processes in your own browser:
- The ticker you asked about, and the as-of date you chose
- Price history and company identity fetched from public sources
- Filing figures from SEC EDGAR
- Headlines and public posts about that ticker
- Your scoring settings, chart indicators and display preferences
- Your history log of past analyses, and how those calls turned out
Important Note: settings, cached readings, the history log
and your favourites are stored locally in your browser using Chrome’s
storage API. We have no access to them. Every request for prices, filings,
headlines and posts is made by your browser, directly to the source
— nothing is proxied through us, and we never see the responses.
Information We Collect on Our Servers
The rating itself is computed on our server, because the weighing is not
shipped inside the extension. To do that and to run accounts, we collect and
store:
-
Account Information: your Google account id, email
address, name and profile picture URL, received from Google OAuth and used
for authentication only -
Subscription Data: your plan (Free, Monthly, Yearly,
Lifetime), when a cancelled subscription stops being honoured, your Stripe
customer and subscription identifiers, and your monthly and lifetime
analysis counts -
Session Data: a hash of each sign-in token —
never the token itself — the browser’s user-agent string, and when the
session was created, last seen and expires. Sessions expire after 30 days -
Analysis Records: one row per rating, holding the ticker,
the as-of date, the resulting rating, four summary numbers (net,
confidence, coverage, signal count), whether it counted against your
allowance, your plan at the time, and a one-way hash of your IP address
combined with your session token
That list is the complete contents of those tables. The readings themselves
are sent to be scored, used to compute the verdict, and then discarded —
they are never written to the database and are in no backup of it.
What We Don’t Collect
- We do not store your price history, article text or post bodies
- We do not store your IP address — only an irreversible hash of it, which cannot be turned back into an address
- We do not collect browsing history, viewing habits, or the addresses of the pages you visit
- We do not read the content of any page you have open
- We do not receive or store your Google password
- We do not see or store your card details
- We do not receive anything from the AI backend you configure, if you configure one
- We do not sell data, run advertising networks, or build profiles
How We Use the Information
The collected information is used solely for:
- Authentication: verifying your identity through Google OAuth
- Scoring: computing the rating from the readings your browser sends
- Quota: counting analyses against the free monthly allowance
- Billing Management: managing subscriptions through Stripe
- Abuse Prevention: spotting one account being shared as a public API key, which is the only purpose the IP hash serves
We never use your data for advertising, for marketing to third parties, or
for any purpose unrelated to providing the analysis service.
Permissions We Request and Their Usage
The extension requests the following permissions to function correctly:
- storage: to save your settings, cached readings, history log and favourites locally on your device
- unlimitedStorage: because the cache of past readings can exceed Chrome’s default quota; it is still entirely local
- sidePanel: to show the report beside the page you are reading rather than over it
- tabs: to open the report, the options page and the sign-in page, and to watch for the sign-in redirect returning so the session can be collected. The address of a tab is read only to offer the ticker that page is about, and is never sent or stored
- declarativeNetRequest: to set one request header. SEC EDGAR requires every automated caller to identify itself, so requests to sec.gov carry the extension’s name and a contact address — and nothing about you
-
host_permissions, each for one purpose:
marketinspection.com— our own scoring, account and billing endpointsquery1.finance.yahoo.com,query2.finance.yahoo.com— prices, company identity and headlinesdata.sec.gov,www.sec.gov— filingsapi.stocktwits.com,www.reddit.com— public postsapi.frankfurter.dev,api.coingecko.com,api.gdeltproject.org— stand-in sources, used only when a primary source will not answerapi.twelvedata.com— prices, only if you enter your own keylocalhost,127.0.0.1— to reach an AI model server running on your own machine, if you choose to use onecodingdir.com/extension-ads— listings for the developer’s other extensions, shown in the popup and welcome page; the request carries no account identifier
-
optional host permission (
https://*/*): requested
at runtime, only if you ask the extension to use an AI endpoint of your own
at an address we cannot know in advance. It is never requested otherwise, and
Chrome asks you before granting it
Data Protection
- Secure Authentication: Google OAuth 2.0, with CSRF protection on the sign-in round trip
- Tokens Never Stored: we store only a SHA-256 hash of each session token. A copy of our database would not let anyone sign in as you
- Tokens Never in a URL: the sign-in redirect carries a single-use code that expires in sixty seconds and dies on first use. The real token is exchanged over POST, so it never reaches browser history, a server log or a referrer header
- IP Addresses Hashed: what is stored is a one-way hash of the address combined with your session token, never the address
- Encrypted Communication: everything between the extension and our servers uses HTTPS
- Payment Security: all payment processing is handled by Stripe (PCI DSS compliant). We never see or store card details
- Session Expiration: sessions expire after 30 days, and signing out deletes that session immediately
- No Third-Party Tracking: no analytics tools, no tracking pixels, no advertising networks, in the extension or on this site
Information Sharing
We do not:
- Sell or rent your personal information to anyone
- Share your data with third parties for marketing purposes
- Use your data for advertising or profiling
- Share which tickers you analyse, or the ratings you received, with anyone
- Access any account you hold anywhere else
Third-Party Services We Use
-
Google OAuth: for secure authentication. We receive only
your email, name, profile picture URL and account id. Google’s use of your
login data is governed by their privacy policy -
Stripe: for payment processing and subscription
management. Stripe collects payment information, billing address and
email. We never have access to your full card details. Their use of your
data is governed by
Stripe’s privacy policy
Public Data Sources
The extension fetches from Yahoo Finance, SEC EDGAR, StockTwits, Frankfurter,
CoinGecko, GDELT and — if you supply a key — Twelve Data. Those requests come
from your browser, so each service receives what any visitor’s browser sends
it, including your IP address. They are independent services under their own
privacy policies, and we have no agreement with them about your data. Article
thumbnails are requested with the referrer suppressed, so the image host is
not told which page asked for them. The report always names which source each
reading came from.
The AI Backend, If You Enable One
The optional AI write-up and headline reading are off by default. If you turn
them on, the headlines, post text and finished readings are sent to whichever
backend you configure: Chrome’s on-device model, which sends nothing
anywhere; a server running on your own machine; or an API endpoint and key
you supply. We are not a party to that request and never see it, and anything
it costs you is between you and that provider.
Server Usage
Our extension uses a secure backend server (marketinspection.com) for:
- Scoring the readings into a rating
- User authentication and session management
- Subscription plan management and quota counting
All server operations use encrypted HTTPS connections. Data is stored in a
MySQL database with access restricted to authorised administrators. This
website runs on WordPress in a separate database, with a database user that
has no access to the service’s data at all.
The Video on This Site
The home page embeds a walkthrough video from
youtube-nocookie.com, YouTube’s privacy-enhanced domain.
Loading the page contacts YouTube, which receives your IP address and
browser details as any site you visit would. YouTube does not set a
tracking cookie on that domain unless you start playback, and we receive
nothing at all from it. Google’s use of that data is governed by their own
privacy policy.
Your Rights and Choices
You have the right to:
- Delete Your Account: open the extension’s options page, scroll to Delete your account, and confirm. This removes your account, your analysis history and every signed-in browser, and cancels any active subscription — immediately, while you wait. There is no queue and no review
- Access Your Data: request a copy of everything we store about you by emailing us
- Correct Your Data: your name, email and picture refresh from your Google account at each sign-in
- Manage Subscriptions: cancel or change your plan at any time through the Stripe billing portal, reachable from Manage subscription in the toolbar popup
- Opt Out of AI Processing: the AI write-up and headline reading are off unless you configure a backend, and can be switched off again in the options page
- Opt Out Entirely: uninstall the extension to stop all processing. That also removes everything it kept locally — settings, cached readings and history log
- Complain: if you think we have handled your data badly, please tell us first. You also have the right to complain to your national data protection authority
Data Retention
- Account, Plan and Usage Counters: retained while the account is active. Deleted the moment you delete the account, or within 30 days of an emailed request
- Analysis Records: retained while the account is active, as the audit trail behind your usage count. Deleted with the account
- Sessions: 30 days, or immediately on sign-out. Expired rows are swept automatically
- Sign-in Handover Codes: sixty seconds, and deleted on first use
- Settings, Cache and History Log: stored in your browser only, for as long as the extension is installed
- Deletion Record: one log line saying that an account was deleted, when, and how many rows went — with no email, no name and no identifier that still points at anybody
- Payment Records: retained as required by law (typically 7 years for tax purposes), held by Stripe rather than by us
Children’s Privacy
Our service is not directed to children. We do not knowingly create accounts
for anyone under 16, and we do not knowingly collect personal information
from them. If you believe a child has provided us with personal information,
please contact us immediately and we will delete it.
International Data Transfers
Our servers are located in the United States. If you are accessing the service
from elsewhere, your information may be transferred to, stored and processed
there. By using the service, you consent to this transfer. Google and Stripe
operate their own international infrastructure under their own policies.
Changes to the Privacy Policy
We may update this Privacy Policy to reflect changes in our practices, legal
requirements or service features. Any material changes will be:
- Posted on this page with an updated “Last Updated” date
- Announced in the extension’s release notes
- Notified to active users by email, for significant changes
Your continued use of the extension after changes are posted constitutes
acceptance of the updated policy.
Security Incidents
In the unlikely event of a data breach affecting your personal information,
we will:
- Notify affected users within 72 hours by email
- Describe the nature of the breach and the data affected
- Explain the steps we are taking to address it
- Provide recommendations to protect yourself
Contact Information
For any question, concern or request regarding this policy or your data: admin [AT] marketinspection [DOT] com
Data Requests: write with “Data Request” in the subject line,
from the address your account uses.
Response Time: we aim to answer every privacy enquiry within
5 business days.
Legal Basis for Processing (GDPR)
For users in the European Economic Area and the United Kingdom, we process
your data on these bases:
- Contractual Necessity: to provide the analysis service you signed up for
- Legitimate Interest: to prevent abuse of the free allowance and to keep the service secure
- Legal Obligation: to keep the payment records tax law requires
- Consent: for optional features such as the AI write-up and headline reading, which you can withdraw at any time by switching them off
Consent
By installing and using the MarketInspection extension, you consent to:
- The processing of information as described in this privacy policy
- Your browser fetching public market data directly from the sources listed above
- The storage of your account, plan and analysis records on our servers
- The use of browser storage for your settings, cache and history log
You can withdraw consent at any time by:
- Deleting your account from the options page
- Cancelling your subscription
- Uninstalling the extension
This policy is governed by the laws of France.