Privacy Policy

This policy describes how SEO Checks and Sende SEO Analyzer collect and use audit data.

The analyzer checks only public pages accessible on the internet.
It does not request passwords and does not access user accounts or admin panels.
It does not collect payment data or sensitive personal visitor data.
When the audit data provider is set to DataForSEO (`AUDIT_DATA_PROVIDER=dataforseo`), the URLs you submit for auditing are sent to the third-party processor **DataForSEO** to fetch and analyze pages (including JavaScript execution and browser rendering as configured). DataForSEO may apply its own caching and processing consistent with its service. Further details appear in DataForSEO’s documentation and policies.
To limit abuse, we apply a daily (UTC calendar day) cap on **new** audit submissions per client IP, tracked using a one-way hash of the IP (we do not store the raw IP as plain identifier text). The cap is configured per deployment via `AUDIT_RATE_LIMIT_PER_DAY_PUBLIC` (default **3** per IP per day; **0** disables the daily cap for non-bypass IPs on self-hosted installs).
If a completed audit already exists for the same submitted URL, the service may return that prior audit within **24 hours** via a Redis-backed cache instead of enqueueing a new job.
It stores the submitted URL, extracted domain, audit status, created time, start time, and finish time to generate and display the report by audit ID.
It stores the audited page URLs, HTTP status for each page, and technical SEO fields required for the report, such as canonical and noindex detection.
It stores detected issues such as issue type, affected URL, evidence, impact, suggested fix, and priority score.
It stores limited operational logs including audit ID, checked URL, duration, page count, and server resource usage such as load, memory, and swap.
It does not archive full page content, passwords, payment data, or private account content.