Privacy policy
What LegitSonar collects, why, how long it is kept, and who else sees it.
LegitSonar has no accounts, no advertising and no analytics. It collects almost nothing about you, and this page describes exactly what "almost" covers.
The short version
- No account, no sign-up, no profile.
- No analytics, no advertising, no tracking cookies, no social plugins.
- Two cookies, both strictly necessary — see the cookie policy.
- Your IP address is recorded when you ask for a live scan, and kept for 90 days.
- Web fonts are loaded from Google, which means Google sees your IP address. This is the only third party the pages reach out to, and it is described below.
- Nothing is sold, and nothing is shared for anyone else's marketing.
What is collected
When you browse
The web server records the usual request log: the address requested, the time, the response status, the browser's user-agent string and the connecting IP address. This is what any web server writes and it is what makes it possible to see that the site is working.
When you search
Search terms are handled in the request and are not stored against you. The type-ahead endpoint answers from the domain index; it holds no session and writes nothing.
When you request a live scan
Pressing Re-run analysis, or opening a report for a domain not yet on file, queues a scan. The scan record keeps the domain, the outcome, and the IP address that asked for it. The address is kept because each scan makes this server send requests to a third party's site on your behalf — without a record of who asked, the feature is an open relay for generating traffic against other people.
What is not collected
No name, no email address, no payment details — there is nowhere on this site to enter any of them. Nothing is collected from your device beyond what your browser sends with a normal request. There is no fingerprinting.
Why, and on what basis
Under the GDPR the processing above rests on legitimate interests, namely:
- Server logs — operating the service and diagnosing faults.
- Scan requester IP — preventing abuse of a feature that generates outbound traffic, and enforcing the rate limits that keep it from being used against others.
- Session cookie — strictly necessary for the site to function; no consent is required for it and none is asked.
No consent banner is shown because nothing here requires consent. If that ever changes, the banner will arrive with it.
How long it is kept
| What | Kept for |
|---|---|
| Scan evidence (the raw signals behind a scan) | 7 days |
| Scan record, including the requester's IP address | 90 days |
| Session cookie | 120 minutes of inactivity |
| Rate-limit counters | 1 hour |
| Web server request logs | Rotated weekly, four weeks retained |
Deletion is automatic and runs daily. Nothing above is retained "just in case".
Who else sees it
Cloudflare
Traffic to this site passes through Cloudflare, which terminates the connection, filters abuse and forwards the request. Cloudflare therefore sees your IP address and the address you requested, and sets its own cookies for bot management. Cloudflare acts as a processor for this site under its own data processing terms.
Google Fonts
The typefaces are loaded from fonts.googleapis.com and
fonts.gstatic.com. Your browser therefore makes a request to Google when a page
loads, and Google receives your IP address and the referring page. No cookie is set by this
request, but the disclosure is owed to you regardless.
This is a dependency we would rather not have, and it is avoidable: the same fonts can be served from this domain, which removes the third-party request entirely. It is on the list.
Nobody else
There are no analytics providers, no advertising networks, no A/B testing services, no embedded video, no social buttons, and no data brokers. Favicons shown next to domain names are served from this domain, not fetched from the sites themselves, so browsing a report does not announce your visit to the site being reported.
Data about domains
Reports describe websites, and some of that public technical information — a registrant name in a WHOIS record, for instance — can relate to an identifiable person. It is published because it is already public, and because knowing who stands behind a site is central to judging whether it can be trusted.
Where a registrar redacts a WHOIS record, the report shows it as redacted; nothing is reconstructed or bought to fill the gap. If you are named in a report and believe the publication is unjustified, write to [email protected] and say so — this is assessed on its facts, not refused on principle.
Your rights
You may ask for access to, correction of, or erasure of your personal data, object to processing, or ask for it to be restricted. Write to [email protected].
In practice, the only data likely to relate to you is an IP address attached to a scan you requested. To find it we need that address and roughly when the scan was made; without them there is nothing to search on, and we will not ask you for more identifying information than the request requires.
If you are in the EU or the UK and are not satisfied with the response, you may complain to your national data protection authority.
Changes
This page is dated at the top. Changes that affect what is collected or how long it is kept will move that date, and the substance of the change will be stated rather than buried in a rewrite.