Privacy Policy

SEO Readiness Chrome Extension  ·  Last updated: April 11, 2026  ·  Effective immediately

1. Who We Are

SEO Readiness ("the Extension", "we", "us", "our") is a Chrome browser extension developed by Owais Ahmed Sheikh. The extension is published at seoreadiness.netlify.app and distributed through the Google Chrome Web Store.

For privacy-related questions, contact us via WhatsApp: +92 315 264 8247 or email: owaisahmed591@gmail.com.

2. Data We Store Locally on Your Device

The Extension uses chrome.storage.local — Chrome's built-in local storage API — to save the following data exclusively on your device. This data never leaves your browser.

Data Item	What it contains	Why it is stored
Scan history	Domain name, SEO score (0–100), timestamp of each scan	To display your recent scan history in the extension popup
Auto-check setting	A boolean (true/false)	To remember whether auto-scan is enabled or disabled
Daily scan counter	A number (scans used today) + reset date	To enforce the free tier limit of 20 scans per day
Pro license key	Your license key string (e.g. SRPRO-XXXX-XXXX-XXXX)	To unlock Pro features after purchase — validated locally
Cached scan results	Last known score and signal breakdown for a domain	To display results instantly without re-fetching

3. Network Requests the Extension Makes

To compute the SEO Readiness Score, the Extension makes outbound GET requests to publicly accessible URLs on the website you are analysing. These are standard browser fetch requests — identical to typing a URL in your address bar.

Request target	Purpose	Data sent
sitemap.xml on the analysed domain	Check sitemap freshness (lastmod dates)	None — standard HTTP GET
robots.txt on the analysed domain	Read crawl directives and sitemap pointer	None — standard HTTP GET
RSS / Atom feed on the analysed domain	Check content activity (last published date)	None — standard HTTP GET
Google Search (www.google.com/search)	Check SERP indexing recency and page count (only when a scan is triggered by you)	A search query for the domain — same as a manual Google search

No data from these requests is transmitted to us. The Extension reads the responses locally in your browser and computes the score on your device.

4. Data We Do NOT Collect

• ✗ We do not operate any server that receives your browsing data
• ✗ We do not use analytics tools (no Google Analytics, Mixpanel, Amplitude, or similar)
• ✗ We do not use cookies or any cross-site tracking
• ✗ We do not collect your name, email, or any personally identifiable information
• ✗ We do not sell, rent, or share data with third parties
• ✗ We do not transmit your scan history anywhere
• ✗ We do not fingerprint your browser or device

5. Chrome Permissions Explained

The Extension requests the following Chrome permissions. Each permission is used only for the functionality described:

storage

Used to save your scan history, settings (auto-check toggle), daily scan count, and Pro license key locally on your device via chrome.storage.local. Data never leaves your device.

tabs

Used to read the URL of the currently active browser tab so the Extension knows which website to analyse when you open the popup or when auto-scan triggers. Tab URLs are not stored or transmitted.

notifications

Used to display a local desktop notification when a background scan completes (when auto-check is enabled). No notification content is sent anywhere.

scripting

Used to inject a lightweight annotation script (serp-annotate.js) into Google Search results pages. This script reads the SERP HTML on your device to extract indexing signals. It does not modify, transmit, or log any data.

webNavigation

Used to listen for tab navigation events. When auto-check is enabled, the Extension detects when you navigate to a new page and may trigger a background scan of that domain. No navigation history is stored or transmitted.

Host permission: <all_urls>

Required to fetch publicly accessible files (sitemap.xml, robots.txt, RSS feed) from any domain you choose to analyse. Without this permission, the Extension could only scan a predefined list of websites. The permission is used strictly to read public URLs on the site you are actively analysing — not to read page content silently in the background.

6. Pro License Key

If you purchase a Pro license, your license key is stored locally in chrome.storage.local. License validation is performed by contacting our key-validation service. No other personal data is transmitted.

7. Children's Privacy

SEO Readiness is not directed at children under the age of 13 (or 16 in the EEA). We do not knowingly collect any personal information from children. If you believe a child has provided personal information, please contact us immediately.

8. Data Retention and Deletion

All data stored by the Extension remains on your device for as long as the Extension is installed. You can delete all locally stored data at any time by:

• Clicking "Clear all" in the History panel within the Extension popup
• Uninstalling the Extension from Chrome — this removes all locally stored data immediately
• Using Chrome's built-in extension data management (Settings › Privacy and security › Site settings › Your device › SEO Readiness)

9. Third-Party Services

The Extension does not integrate with, send data to, or load scripts from any third-party analytics, advertising, or tracking services.

The landing page (seoreadiness.netlify.app) is hosted on Netlify and uses Google Fonts for typography. Netlify may collect standard server access logs (IP, browser, requested URL). Google Fonts may log font requests. These services have their own privacy policies.

10. Your Rights

Since we do not collect or store personal data on any server, there is no centrally held profile to access, correct, or delete. All your data is on your own device and is fully under your control. You can delete it at any time as described in Section 8.

If you are an EEA / UK resident and believe we hold any personal data, you have the right to request access, correction, erasure, restriction of processing, data portability, and the right to object. Contact us using the details below.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The most current version is always published at seoreadiness.netlify.app/privacy-policy.html with the "Last updated" date at the top. Material changes will be highlighted in the Extension update notes on the Chrome Web Store.