Privacy Policy

The short version

• No accounts, no signup, no email collection anywhere on the site.
• Nothing is stored on your device unless you allow it. The site’s own visit counting sets no cookies at all.
• Google Analytics is available but off until you say yes. It sets cookies, so it is asked about in a banner, it stays unloaded if you decline, and you can withdraw at any time from this page.
• The domain or URL you submit is used as a cache key, kept for a published length of time — between one minute and 24 hours depending on the tool — and then expires automatically.
• Your IP address is used to enforce rate limits and is held only for the length of the rate-limit window.
• Nothing is sold, and nothing is shared with advertisers.

What you submit to a tool

When you run a check, the domain or URL is sent to this site’s server, used to perform the lookup, and stored as a cache key with the result so the next person checking the same target does not trigger a fresh query against public infrastructure.

That cache entry expires on its own. The lifetimes are per tool and are published in full on how we measure. Nothing extends them, and there is no separate log of submitted targets — no history, no saved reports, no database.

Cache entries are not tied to you. The key is derived from the target you checked, not from your IP, session, or anything else about you, so it is not possible to work backwards from a cached result to the person who requested it.

Your IP address

Every public endpoint here is rate limited per IP and per tool, which requires recognising repeat requests. Your IP is used as that identifier and is held in the rate-limit store only for the duration of the window — currently one minute — after which it expires automatically.

Beyond that, our hosting and edge providers keep standard server logs (IP address, timestamp, requested path, user agent) as part of operating the service and protecting it from abuse. Those are the providers’ logs, retained under their own policies, and are not used for analytics or profiling.

Cookies and analytics

There are two separate analytics systems here, and they behave very differently. The distinction matters, so they are described separately rather than merged into one reassuring paragraph.

Umami — always on, no cookies

This site runs Umami, a cookieless analytics tool, on its own server. It records that a page was viewed, and stores the path, the referring site, your browser, operating system, device type, screen size, language, and an approximate location — country, region and city — derived from your IP address. It does not set a cookie, does not read one, and does not store an identifier that can follow you to another site.

To count one visit rather than five separate ones, it derives a temporary hash from your IP address and browser details. That hash is never stored alongside the values it came from, it is not shared, and the salt behind it rotates, so the same visitor returning on another day is simply a new number.

Your IP address is not stored by it. It is used at the moment of the request to work out the approximate location and to group your page views into one visit, then discarded — there is no column for it anywhere in the database.

No data from Umami leaves this server. It runs on the same machine as the site, and the script that collects it is served from this domain rather than by a third party, so no analytics company receives anything from it. Because it stores nothing on your device, it is not gated behind the banner and runs for every visit.

Google Analytics 4 — only if you allow it

This site also offers Google Analytics 4, which does set cookies. That is why you were asked. Until you choose “Allow”, the Google tag is not loaded into the page at all — it is not merely inactive or set to a restricted mode, the script is absent from the document and no request is made to Google.

If you allow it, these cookies are written to your device:

• _ga — a randomly generated identifier used to distinguish one browser from another. Expires two years after your most recent visit.
• _ga_<id> — holds the session state for this specific property. Also a two-year expiry.

With those set, Google receives the pages you view on this site, the referring site, your device and browser, an approximate location, and your IP address, which is used to derive that location. IP anonymisation is enabled and advertising features, remarketing and ad personalisation are switched off, so this data is not used to build an advertising profile of you. That is a configuration choice on our side, not a promise about Google’s systems in general.

Google is the data controller for what it collects here, it processes that data on servers outside the UK and EEA, and its own terms govern what happens to it after that. This is exactly the transfer that declining avoids. Google’s privacy policy describes it in full.

Declining costs you nothing. No feature on this site depends on analytics, no tool behaves differently, and nothing is degraded or delayed. Visits that decline are counted by Umami exactly as before.

Your answer is remembered in your browser’s local storage rather than in a cookie — a cookie recording a refusal of cookies would be a poor joke — under the key sct-analytics-consent. It never leaves your device. Clearing site data forgets it, and the banner returns.

Withdrawing has to be as easy as allowing was, so the control is not in here with the rest of the prose — it sits at the bottom of this page, outside the collapsed section, where it is reachable without reading anything first.

Third parties involved in a check

Running a check necessarily involves other systems. These are the only ones, and each receives only what it needs to answer:

• Hosting. The site runs on a private server rented from Hostinger, which processes requests and keeps standard operational logs as described above.
• Cache and rate-limit store. Results and rate-limit counters are held in a Redis instance running on that same server, with the expiry times described above. They are not sent to any third-party service.
• Public data sources. Depending on the tool, the target you submit is sent to public resolvers, registries over RDAP, or the site itself. These services see the domain being checked and our server’s IP address — not yours.
• Google PageSpeed Insights. Used by the speed test. The URL you submit is sent to Google’s API to be analysed. It is sent from our server, so Google sees the URL being tested and our IP address, not yours.
• Anthropic. Used by the domain name generator. The keyword or description you enter is sent to the Claude API to generate name candidates. It is sent from our server, and it is not used to train models.
• Google Analytics. Only if you allowed it, and described in full above. This is the only third party on this list that receives anything about you rather than about the site you are checking, and the only one you are asked about.

Because checks run from our servers rather than your browser, the site you check never sees your IP address. It sees ours, identified honestly as our bot.

Affiliate links

Some results may include a link to a hosting provider or domain registrar. Following one takes you to that company’s own site, where their privacy policy and their cookies apply, not ours.

We receive only aggregate commission reporting from those partners — how many purchases were referred, never who made them. We do not pass any information about you to a partner, because we do not have any. Full affiliate disclosure.

If you email us

Messages sent to hello@sitechecktools.com are kept in an ordinary mailbox for as long as needed to deal with them. Nobody is added to a mailing list, and there is no mailing list to be added to.

Your rights

Under the GDPR and similar laws you can request access to, correction of, or deletion of personal data held about you. In practice there is very little of ours to request: no account exists, cache entries are not linked to you, and rate-limit records expire within a minute.

The realistic exceptions are provider server logs, any email you have sent us, and — if you allowed Google Analytics — the data held by Google. That last one is not in our database and cannot be deleted from here, so a request about it goes to Google under their policy. Withdrawing consent above stops any further collection immediately and removes the cookies from your device, which is the part we can act on directly.

Write to hello@sitechecktools.com with a request and it will be actioned.

Children

This is a technical tool for website operators. It is not directed at children and does not knowingly collect information from them.

Changes to this policy

Any change that affects what is processed will be made here before the change goes live, with the update date at the top of this page revised. Questions go to hello@sitechecktools.com.