ClientSite Check Privacy Policy

ClientSite Check Privacy Policy

Plain-English website checks for local business clients.

Active page website checks. Local settings only. No tracking.

Last updated: June 4, 2026

ClientSite Check is a Manifest V3 browser extension for Chrome. It helps users review a local business website page and create a plain-English website check and report. ClientSite Check is also compatible with Microsoft Edge when sideloaded.

Privacy Summary

ClientSite Check analyzes the active page only when you click the extension.

ClientSite Check does not send audit data to a server.

ClientSite Check stores optional report preferences locally in browser storage.

ClientSite Check does not track users.

ClientSite Check does not use analytics.

ClientSite Check does not use remote code.

ClientSite Check does not scan in the background.

Overview

ClientSite Check provides plain-English website checks for local business client conversations. It reviews common website signals on the active page, then shows a scorecard, top recommended fixes, business impact notes, evidence where available, copyable client messages, and a print-friendly report.

ClientSite Check is designed to run only after a user action. It does not monitor browsing activity in the background.

What ClientSite Check Analyzes

When you click the extension, ClientSite Check analyzes the current active page in your browser. It may review visible page content, headings, links, metadata, images, structured data, contact signals, trust signals, local relevance signals, findability signals, and basic technical hygiene signals.

This analysis happens locally in the browser for the purpose of creating the checklist-style website scorecard and report.

What ClientSite Check Stores Locally

ClientSite Check can store optional report preferences and settings locally in browser storage. These settings may include prepared-by name, contact email, website, theme preference, and last updated time.

These optional settings are used to customize the print-friendly report. They are stored locally in the browser and are not sent to a server by ClientSite Check.

What ClientSite Check Does Not Do

ClientSite Check does not sell data.

ClientSite Check does not track users.

ClientSite Check does not use analytics.

ClientSite Check does not send audit data to a server.

ClientSite Check does not use a backend service.

ClientSite Check does not use remote code.

ClientSite Check does not use ads.

ClientSite Check does not use affiliate links.

ClientSite Check does not include payment features.

ClientSite Check does not scan in the background.

ClientSite Check does not request host permissions.

ClientSite Check does not request access to all websites.

ClientSite Check does not request tabs, webRequest, history, or browser settings override permissions.

ClientSite Check does not scrape Google Maps.

ClientSite Check does not scrape Google Business Profile.

ClientSite Check does not scrape search results.

How ClientSite Check Uses Permissions

ClientSite Check uses only activeTab, scripting, and storage.

These permissions support the user-triggered active-page audit and optional local report settings.

activeTab Permission Explanation

The activeTab permission lets ClientSite Check access the current active page only after you click the extension. It does not give ClientSite Check ongoing access to every website you visit.

scripting Permission Explanation

The scripting permission lets ClientSite Check run its audit script on the active page after you click the extension. The script reviews page signals needed to create the checklist-style scorecard and report.

storage Permission Explanation

The storage permission lets ClientSite Check save optional report preferences locally in browser storage. This may include prepared-by name, contact email, website, theme preference, and last updated time.

ClientSite Check does not use storage for tracking, analytics, ads, or browsing history.

Data Sharing

ClientSite Check does not sell data, does not share audit data with a server, and does not send audit data to any backend service.

Audit results are created locally in the browser. If you copy text from the extension or print or save a report, you control where that copied or saved content goes.

Data Deletion

You can delete optional local report settings from the ClientSite Check options page by using Reset Settings.

You can also remove the extension from Chrome to remove extension-managed local data according to browser behavior.

Estimates and No Guarantees

ClientSite Check provides checklist-style estimates only. It does not guarantee search rankings, traffic, leads, revenue, sales, or business results.

The scorecard and recommendations are intended to support practical client conversations, not to predict future performance.

Remote Code

ClientSite Check does not use remote code. Extension code is packaged with the extension and runs locally in the browser.

Changes to This Policy

This privacy policy may be updated if ClientSite Check changes. Any updates should continue to describe what the extension does, what permissions it uses, what is stored locally, and how user data is handled.

Contact

For support or privacy questions, contact:

demarioland.extensions@gmail.com