SiteMed analyzes pages and stores its workspace in Chrome. It does not include SiteMed analytics, advertising trackers, user accounts, or a SiteMed data server.

Data SiteMed handles

The Chrome Web Store groups data into categories, including information used only on your device. SiteMed's current data usage falls into these categories:

• Website content: SiteMed checks visible page text, links, form structure, image loading, and other page details to explain findings.
• Web history: SiteMed uses the address of the page you choose to check. Saved reports and optional audits can retain website addresses and page paths. It does not read your full Chrome browsing history.
• User activity: SiteMed checks page request results and loading times. If you enable monitoring, it also stores the time and result of each scheduled website availability check. It does not record clicks, typing, mouse movement, or scrolling.
• Personally identifiable information: Optional saved client names, project labels, notes, and report branding can contain names or other personal details you enter. They are kept in Chrome extension storage unless you choose to export them.
• Location: Public registration services receive your IP address as part of the domain-age lookup. SiteMed does not request GPS or precise device location.

SiteMed uses this information to provide the page check and the optional workspace, audit, monitoring, and report features. It does not use it for advertising, credit decisions, or lending. SiteMed does not read values typed into password or payment fields.

SiteMed's use of information received from Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. SiteMed uses the data only for its stated website-checking features. It does not sell the data, use it for personalized ads, or allow SiteMed staff to view reports stored in the browser.

Page scans

A page scan starts when the user opens SiteMed or selects Check again. The scan can handle:

• The page hostname and origin
• Counts of inspected and affected images, links, fields, controls, forms, media, and layout elements
• HTTP status codes exposed by Chrome
• Numeric positions used to highlight an affected element
• Page structure and search-setting counts or yes-or-no results
• Bounded loading times and a layout movement score
• The scan time, connection signal, detected site platform, and bounded trust signals
• A public domain-registration lookup status and registration date, when available

A saved scan does not retain page text, entered form values, image URLs, link destinations, request bodies, cookies, headers, or screenshots. While the popup is open, the Affected items sections can display short element names and addresses so the user can identify a specific problem. Query strings, unrelated URL fragments, embedded credentials, and data URLs are removed. These details exist only in popup memory and are discarded when the popup closes. They are not included in saved scans, workspace exports, copied reports, or network requests.

The current tab report is stored temporarily in Chrome session storage. It is removed when the tab navigates or closes and is rejected after 30 minutes.

Saved workspace

Selecting Save & compare copies the report into local Chrome extension storage. The saved workspace can contain:

• The website hostname and origin
• Up to 30 scan reports per saved website
• A user-entered display name, client or project label, and notes
• A selected baseline and the latest report
• Whole-site audit paths, response status, redirects, inbound link paths, and finding labels
• Robots and sitemap status, counts, and fixed finding labels
• Monitoring times, status, response time, and a short availability message
• Report branding text and an optional local logo image

Queries and fragments are removed from audit paths. Saved information remains until the user removes the website, clears extension storage, or uninstalls SiteMed. Export backup downloads this information as a JSON file chosen by the user.

Network activity

The page-content scan observes the already loaded page and makes no extra page requests. SiteMed separately sends the registered base domain, such as example.com, to the public RDAP bootstrap service at rdap.org to request its registration date. RDAP.org redirects the request to the registry responsible for that domain.

The page path, query, fragment, page content, form values, and saved workspace are not included in the domain-registration request. As with any web request, RDAP.org, the responsible registry, and their network providers can receive connection information such as the user’s IP address and browser request headers. A short-lived in-memory cache reduces repeat lookups.

Run audit requests pages from the same website after Chrome asks the user to allow access to that site. It follows same-site links and checks robots and sitemap files. Monitor hourly requests the saved website’s origin on a Chrome alarm. These responses are analyzed locally and are not forwarded to SiteMed or another service.

SiteMed has no reputation-list, malware-scanning, advertising, or analytics endpoint.

Clipboard, printing, and notifications

Copy report writes a plain-text report to the clipboard. Print or save as PDF opens Chrome’s print flow. SiteMed does not paste, upload, or send either report.

When monitoring is enabled, Chrome may show a local browser notification after a failed check or a recovery. The user can revoke notification or site access in Chrome.

Browser permissions

Active tab and scripting

Inspect the current page after the user opens SiteMed.

Storage

Keep temporary tab reports and the user-created local workspace.

Alarms

Schedule local availability checks.

Optional notifications

Show monitoring failure and recovery alerts.

Optional website access

Request a specific saved website when the user starts an audit or enables monitoring.

The RDAP domain-age lookup uses a normal public HTTPS request and does not grant the extension access to another website’s page contents.

This website

This informational website does not use SiteMed analytics, advertising trackers, cookies, accounts, or contact forms. It is hosted by GitHub Pages. GitHub may process basic request and security information under the GitHub General Privacy Statement.

Your choices

• Do not select Save & compare if you do not want a report kept locally.
• Remove an individual saved website from the SiteMed dashboard.
• Revoke optional website or notification access in Chrome.
• Clear the extension’s data or uninstall SiteMed to remove its local workspace.

Policy changes

This page will be updated when SiteMed’s data handling changes. The effective date at the top identifies the current version.

Contact

For privacy questions or product support, follow the instructions on the SiteMed support page. After publication, users can also use the Support section on SiteMed’s official Chrome Web Store listing.