Privacy Policy — SearchScope by Khalid Elsemary

Data collection

The extension does not collect, sell, transmit or store browsing history, page content, scan results, personal information or usage analytics on servers operated by Khalid Elsemary or third parties.

How page data is used

When the user starts a scan, the extension reads links, anchor text, headings, image metadata, structured data, social tags, page text, raw HTML, the rendered DOM, hreflang annotations, robots and snippet directives, accessibility semantics, loaded-resource metadata, current-tab performance observations and related SEO information from the page selected by the user. It may send direct HTTP requests from the user’s browser to the page’s robots.txt and sitemap locations, canonical target, hreflang alternates and link destinations covered by the selected scan access. Those requests are made only to provide the requested audit and are subject to the destination websites’ own server logs and privacy practices.

Page content and scan results are processed locally. They are not sent to Khalid Elsemary.

Local storage

The extension uses Chrome’s local extension storage to save:

• User-selected scan settings.
• Up to 15 compact scan-history entries when local history is enabled.

This information remains in the user’s Chrome profile. Users can disable scan history in the extension or clear saved history at any time.

The current scan’s bounded raw and rendered source snapshots may be held temporarily in Chrome’s in-memory extension session storage so the user can open the full source comparison. They are not added to compact scan history. The extension retains only the latest source-comparison payload, replacing the previous one, and Chrome clears session storage when the browser session ends.

Because page source can contain private or page-specific values, the source viewer masks common password, token, session and API-key fields by default. Users can deliberately turn masking off for local inspection. Source copies and downloads use the currently selected masking state and remain local.

Website permissions

The extension requests optional website access only after a user action. On the first scan it offers one all-website permission so Chrome can remember the choice across different websites. A user who declines can choose access only for the current website. All-website access remains optional, can be revoked from the extension, and is removed when the extension is uninstalled.

Website access and scan scope are separate. The default scan scope requests only internal and subdomain destinations even when all-website permission is enabled. Unrelated external destinations are requested only when the user explicitly selects the all-links scan scope.

Website access is used solely to:

• Read links, page copy and page-level SEO information from the selected page.
• Read headings, images, structured data, social metadata and locally available performance/resource entries.
• Compare bounded raw HTML and rendered DOM snapshots locally.
• Request link destinations and inspect their responses.
• Verify canonical, hreflang and sitemap targets already covered by the selected scan access.
• Observe status events for the extension’s own audit requests so redirect paths can include exact HTTP codes.
• Highlight or locate audited links on the selected page.

Spreadsheet exports neutralize values that spreadsheet applications could otherwise interpret as formulas. Generated HTML reports use a restrictive content-security policy and create clickable links only for standard web, email and telephone protocols.

The extension does not use its network-observation permission to block, redirect or modify requests, and it ignores requests not initiated by the extension’s own audit process.

Remote code and third parties

The extension does not load or execute remotely hosted code. It does not use advertising networks, analytics platforms, tracking pixels or external AI services.

Data retention

Khalid Elsemary does not receive extension data and therefore does not retain it. Locally saved settings and history remain until the user clears them or removes the extension.

Changes

If future features change how information is handled, this policy and the Chrome Web Store disclosures will be updated before those features are released.

Contact

Privacy or support questions can be submitted through khalidsemary.com.