Extension Privacy Policy

This policy explains how the ModelReady.app browser extension handles data when you use it to audit a website for AI search readiness, landing page clarity, metadata, schema, and related recommendations. The short version: the extension only works on a URL you choose to audit, and we do not sell your data or use it for advertising.

1. What we collect

When you open the extension, it may read the URL of your active browser tab to pre-fill the audit field. You can edit that field or paste a different URL. When you click “Audit this page,” the selected URL is sent to ModelReady.app so our server can fetch the public web page, run automated checks, and generate an audit report.

For an audit, our server may process public page information such as the page title, meta tags, headings, visible text signals, links, structured data, HTTP status, and other technical facts needed to evaluate the page. The extension does not read page HTML, form fields, cookies, passwords, or private page content from your browser.

The extension stores a short local audit history on your device so you can reopen recent results. It can also store an in-progress audit ID temporarily, so closing and reopening the popup does not restart the same audit.

We collect limited product analytics events, such as popup opened, audit started, audit completed, audit failed, report link clicked, and history item opened. These events may include the URL or report URL involved in the event and are associated with a random anonymous ID generated by the extension.

If you sign in, we store your session token in chrome.storage.local on your device. Your email address is used to authenticate you and associate full audit reports with your ModelReady.app account.

2. What we do not collect

• We do not read page HTML, cookies, passwords, form values, or private content from your browser.
• We do not request host_permissions, so the extension cannot continuously access every site you visit.
• We do not use advertising cookies, third-party tracking pixels, or fingerprinting in the extension.
• We do not sell or rent your data.

3. Permissions explained

The extension requests only the browser permissions needed to run audits, remember local state, and support account sign-in:

• activeTab - when you open the extension, it reads the URL of the current tab to pre-fill the audit field with the page you are on. Access is limited to the active tab and only at the moment you invoke the extension.
• storage - stores local history, in-progress audit state, the anonymous analytics ID, and your session token if you sign in.

4. How we use data

We use extension data to provide the audit you request, maintain your account session, show recent local results, prevent abuse, debug reliability issues, understand aggregate product usage, and improve the quality of ModelReady.app audits.

We do not use extension data for advertising, cross-site ad tracking, credit decisions, or unrelated profiling.

5. Third-party services

We use the following services to operate the extension:

• PostHog - product analytics for extension usage events.
• Supabase - authentication and audit report storage for signed-in users.
• OpenAI / Anthropic - AI analysis of audited page facts and generation of scores and recommendations.
• Vercel - hosting and edge functions.

These providers process data only as needed to provide the extension and ModelReady.app service. They do not receive data from the extension for advertising.

6. Data retention and deletion

Local extension data, including recent audit history, the anonymous analytics ID, in-progress audit state, and session data, remains in chrome.storage.local until you clear it, sign out, remove the extension, or your browser removes extension data.

Server-side audit results may be retained to provide reports, support signed-in account history, prevent abuse, and improve the audit system. Anonymous analytics events are retained according to PostHog retention settings. You can request deletion of your ModelReady.app account data and audit records by emailing privacy@modelready.app.

7. Security

We use HTTPS, access controls, and service-level safeguards to protect data handled by the extension and ModelReady.app. No system is perfectly secure, but we take reasonable measures to reduce unauthorized access and misuse.

8. Changes

We may update this policy. Changes are effective when posted with an updated effective date at the top.

9. Contact

Questions about this policy: privacy@modelready.app

Website privacy policy: modelready.app/privacy