Overview
CheckLinks is a Chrome extension that checks hyperlinks on web pages for broken links. This policy explains what data the extension accesses, how it is used, and what permissions are required.
Data collection
CheckLinks does not collect browsing data for the developer or an analytics service. Specifically:
- No analytics, telemetry, or tracking
- No cookies or identifiers created by the extension
- No user accounts or sign-ins
- No scan results sent to a developer-operated or third-party processing backend
How the extension works
When you click the CheckLinks icon on a page, the extension reads unique HTTP/HTTPS links in the current main document at that moment, groups duplicate occurrences, and displays results on the page and in a floating panel. It does not inspect frames or shadow roots, and links added later require a new scan. Fragment-only links and mailto:, tel:, and javascript: links are skipped and not tested.
Requests use HEAD with GET fallback for 403, 405, and 999 responses. They omit credentials, follow redirects, and report the final response and URL. 401 and 403 appear as Needs access, while 429 appears as Rate limited, under Other because those responses are unverified.
Link-check requests go directly from your browser to the linked destinations. Those destination servers may receive normal request information under their own privacy policies; CheckLinks does not proxy or process the requests through a separate service.
Data storage
CheckLinks does not write scan data to persistent storage. The visible report is held in memory for the current page; Clear results removes the visible report and overlays, and a new scan or navigation replaces the current in-memory scan state. A CSV you save locally may contain the source page URL, link text, URL, response, and status details. The optional Chrome Web Store review link is not tracked by the extension.
Permissions explained
<all_urls>(host permission) — Chrome grants broad website access so the service worker can check destinations across domains. The permission is for link checks; it does not create an account or a developer backend.activeTab— Lets CheckLinks read the current page after you click the extension icon. A page scan runs only when you activate it.scripting— Allows the content script to be injected on demand into an eligible tab so it can read links and display the panel and overlays.
Third-party services
CheckLinks has no analytics provider, telemetry service, or third-party processing backend. The extension does make direct requests to the websites whose links you check, as described above.
Changes to this policy
If this policy is updated, the new version will be published at this URL and the effective date above will be revised.
Contact
If you have questions or concerns about this privacy policy, see CheckLinks support or open an issue on the GitHub repository.
You can install CheckLinks from the Chrome Web Store.