Skip to content

Privacy Policy

Interim notice. The full privacy policy is being finalized and will replace this page before paid plans open. Until then, this page states plainly what the service does with data today.

What happens when you check a site

  • You submit a domain. We fetch publicly accessible pages and discovery files of that site (for example the homepage, robots.txt, sitemap.xml, llms.txt) and store the resulting report.
  • We fetch robots.txt first and obey it. If a site disallows our scanner, or its robots.txt cannot be reached, we do not fetch its content.
  • We do not log in to sites, submit forms, or collect anything that is not publicly served.
  • When you submit a check, your IP address is used to rate-limit submissions and is kept only for a short time for that purpose.

Public reports

Reports produced by free checks made without an account describe public websites and may be listed publicly on this site. A report contains evidence taken from public pages only. Reports created under an account are private unless the account holder shares them, and a share can be taken back. Public report pages ask search engines not to index them.

If you control a site and do not want it checked, disallow geoready-scanner in your robots.txt. A site owner who verifies ownership with a DNS record can hide the site's reports from public pages; if you cannot verify ownership, you can ask us to hide them.

Accounts

If you create an account we store your email address, your name, and either a password hash or the identifier supplied by the sign-in provider you chose, plus session records needed to keep you signed in. A session record includes the IP address and browser identifier it was created from. A session expires after 30 days and is extended while you keep using the service; records of expired sessions are not yet removed on a fixed schedule.

Cookies

We set only the cookies the service needs to work: your sign-in session, your language preference, and your cookie choice. We do not use analytics or advertising cookies.

Service providers

Transactional email (such as sign-in and verification messages) is sent through an email delivery provider. When paid plans open, payments will be handled by a payment processor; we will not store card numbers.

Changes

This page will be replaced by the full policy. Material changes will be reflected here with a new date.

Last updated: 12 October 2026