Open SEO Checker is a locally-run, open-source tool. It operates as a server on your own machine (localhost:7437) and stores all crawl data in a local SQLite database. The developer receives no telemetry, usage data, or personal information from your use of this tool.
All data produced by Open SEO Checker is stored exclusively on your local machine:
crawls/ directory in the project folder. Never uploaded anywhere.exports/ directory. Never uploaded anywhere.localStorage on the Settings page. Never sent to the developer's servers.Open SEO Checker collects no usage metrics, crash reports, or diagnostics. There are no analytics scripts, tracking pixels, or background callbacks to the developer. The tool has no knowledge of:
Open SEO Checker supports optional integrations with third-party services. When you enable an integration and trigger a request, your data is sent directly from your machine to that service — not routed through any developer-operated proxy.
All integrations are opt-in. None are enabled by default. You must provide your own API key for each service.
API keys you enter in the Settings page are stored only in your browser's localStorage. They are:
localhost:7437) except as part of direct API calls to the respective providerWhen you run a crawl, Open SEO Checker sends HTTP requests to the URLs you specify. Those target websites may log your IP address and request headers as part of their normal server logging. This is standard web behaviour and outside the scope of this policy. Ensure you have permission to crawl any site before doing so.
If you use JavaScript rendering (Playwright), a headless Chromium browser is launched locally. No data from the rendered pages is sent anywhere other than your local SQLite database.
Open SEO Checker is fully open source under the MIT license. You can inspect every line of code that handles your data at github.com/cuongquachc88/open-seo-checker.
If this policy is updated, the changes will be noted in the GitHub repository's release notes. The "Last updated" date at the top of this page will reflect the most recent revision.
Questions about this privacy policy? Contact: [email protected]