Crawlseer

Privacy Policy

Last updated: · Version 1.0.0

In short: Crawlseer sends nothing to the developer or to any third party. The extension has no backend server. Every analysis runs in your browser and all data stays on your device.

1. What data is processed?

1.1 Website content

When you click the extension icon, the HTML of the page in the active tab is read: title, meta tags, H1–H6 headings, links, images and their alt text, structured data (JSON-LD, Microdata, RDFa), and Open Graph and Twitter Card tags.

This happens only when you click the icon, and only for the active tab (the activeTab permission). The extension does not watch your browsing in the background.

1.2 SEO score history (local)

A score history is kept for each page you analyse so you can see the change over time as a chart. Each record holds two values only: the SEO score (0–100) and the time of the analysis.

The page address is never stored in readable form. To tell records apart, the address is passed through a one-way SHA-256 digest and only that digest is kept — it cannot be reversed. At most 30 records per page and 500 distinct pages are retained.

1.3 Preferences

The theme you choose (light or dark) is stored.

1.4 The storage index

To enforce the 500-page limit, a list of record keys — the digests from §1.2 — is kept. When the limit is passed the oldest records are deleted automatically. This list contains no readable addresses either.

2. Where is the data stored?

All of it in chrome.storage.local, on your device only. Nothing is synchronised, backed up or exported.

You do not have to uninstall to clear the score history: the "Clear history" link under the trend chart in the Overview pane removes all stored history and the index in §1.4 at once.

To delete everything: chrome://extensions → Crawlseer → Remove. Uninstalling deletes all local data, including the theme preference.

3. Network requests

The extension makes only the requests below, and every one of them goes directly to the site concerned — none passes through any server belonging to the developer.

Every network request the extension makes, when it happens and where it goes
RequestWhenWhere to
Reading robots.txtAutomatically, during analysisThe analysed site’s own domain
Reading the sitemapAutomatically, during analysisThe site’s own /sitemap.xml or the sitemap URLs declared in robots.txt — a site may point these at another domain
Reading the page’s raw HTMLAutomatically, during analysisThe address of the page already open (same origin)
Reading HTTP headers (HEAD)Automatically, during analysisThe address of the page already open (same origin)
Link status checking (HEAD/GET)Only when you press the "Check broken links" buttonThe targets of links on the page (at most 50)
Redirect detectionOnly if you have granted permissionThe address of the analysed page

Why raw HTML and headers are needed: the extension compares the original HTML the server sent with the page the browser built after running JavaScript, so it can show which content exists only after JavaScript runs. Both requests go to the address of the page you are already viewing, need no extra permission, and the downloaded content is parsed as text — never executed as code.

3.1 Preview images

In the Images and Social panes, the analysed page’s own images (<img> sources and og:image / twitter:image) are loaded by your browser and shown as previews. This is the browser’s ordinary <img> loading behaviour, needs no extra permission, and sends no credentials.

Only two features ever ask for permission: the "Check broken links" button and redirect detection. The site access they need is optional, is requested the first time you use the feature, and declining leaves the rest of the extension fully usable.

4. What we do not do

  • We collect no data and send none to the developer
  • No analytics, no telemetry
  • No cookies, pixels or fingerprinting
  • No advertising and no ad injection
  • No selling or sharing of data
  • No remotely hosted code — everything ships inside the extension package
  • No third-party libraries — all code is first-party
  • No account, registration or sign-in

5. Chrome Web Store Limited Use commitment

Crawlseer’s use of user data, including any transfer, complies with the Chrome Web Store User Data Policy and its Limited Use requirements.

Concretely: the data processed is used only to show you the SEO analysis, never leaves the device, is not sold, is not used for advertising, and is not used for purposes such as credit assessment.

6. KVKK (Turkish Law no. 6698)

The extension collects, processes and transfers no personal data. Specifically:

  • The extension has no backend; no data reaches the developer.
  • Results and the theme preference are stored only in chrome.storage.local on the user’s own device. The developer cannot reach them.
  • No name, email, phone number or other identifier is requested, and no account is needed.
  • The addresses of analysed pages are never stored in readable form — only irreversible digests.
  • Every network request the extension makes goes straight to the analysed site; none passes through the developer.

For that reason the extension is not a data controller under KVKK with respect to the data you process. You can delete everything stored on your device at any time via chrome://extensions → Crawlseer → Remove. This section is informational and is not legal advice; your own site’s KVKK obligations are outside the scope of this extension.

7. Pricing commitment

Every analysis feature Crawlseer offers today is permanently free. That is a binding commitment, not a marketing line:

  • No existing feature will ever move behind a paywall.
  • No account, sign-in or email address will be made mandatory.
  • No usage quota, credit system or cap on the number of analyses.
  • No advertising and no sponsored placements.
  • Data collection will never be the revenue model.

If a revenue model is ever needed, only a genuinely new tier that does not exist today and carries a real cost could be charged for — and even then, everything that exists today stays free.

8. Children’s privacy

The extension is a developer and marketing tool. It is not directed at users under 13 and does not knowingly collect data from children.

9. Changes

Changes to this policy are published on this page and the "Last updated" date is revised. Updates that change data-handling behaviour are also noted in the extension’s release notes.

10. Contact

Sungur Kerem Gezergün
Email: iletisim@keremgezergun.com
Phone: +90 552 690 27 82
Back to the Crawlseer page