Privacy policy

What we collect

When you run an audit we receive the website address you submit, and the standard information any web server receives about a request, including your IP address, the time of the request, and your browser user agent.

We do not ask for an account or a name. You can give us an email address if you want product updates; that is entirely optional and the audit works the same either way.

Saved reports and share links

Every completed audit is saved so it has a stable address you can return to and share. We store the report itself — the score, the checks, and the evidence gathered from the pages we fetched — along with the website address audited and the time it ran.

Each saved report gets a long random identifier that forms its share link. Anyone holding that link can view the report, so treat it as you would any unlisted URL. The identifier is not guessable and not sequential, so reports cannot be discovered by trying other addresses, and saved reports are excluded from search engine indexing.

Saved reports are deleted automatically 90 days after they are created. You can ask us to delete one sooner — send the share link to hello@example.invalid.

A report contains only information from pages that were publicly reachable at the time of the audit. We do not sign in, submit forms, or attempt to reach anything behind access controls.

If you give us your email address

We store the address, when you gave it, and which part of the site you gave it on. We ask you to tick a box to confirm you want the emails; we do not store an address without that confirmation, and the box is never pre-ticked.

We use it to send occasional product updates. We do not sell or share it, and we do not use it to build a profile of you. To be removed, email hello@example.invalid and we will delete the record.

If you ask us to monitor a website

You can ask to be told when a website’s AI readiness score changes. To do that we need the website address and an email address that the website itself publishes — in its footer, on its contact page, or anywhere else on the site.

Why we require a published address. Without it, anyone could point us at a business they do not own and receive ongoing reports about it. Requiring an address the site publishes means the reports reach the people the site says to contact.

When you submit, we fetch the site’s homepage and, if we can find one, its contact page, and check whether the address you gave appears in what those pages returned. We answer that single question and keep the answer. We do not collect, extract, or store any other address found on the site. There is no place in our records that could hold one.

If we cannot find the address, the request is not refused. Some sites publish contact details in ways an automated reader cannot see — inside an image, a form, or content assembled by scripts. Those requests wait for a person to check them.

Nothing is sent until you confirm. We email a confirmation link to the address you gave, and no monitoring begins and no further email is sent unless that link is followed. If someone submitted your site without your involvement, the confirmation email is the only thing you will receive, and ignoring it ends the matter.

We store the website address, the email address, whether we found the address published on the site, whether you agreed to the site being listed publicly, and the score we last recorded. Every monitoring email contains a one-click unsubscribe link.

How we use it

• To fetch the website you asked us to audit and produce a report.
• To apply rate limits. Your IP address is used to count recent requests so one visitor cannot exhaust the service for everyone.
• To diagnose errors and keep the service working.

We do not sell personal information, and we do not use what you submit to build a profile of you.

What happens to the site you audit

We request a small number of pages from the address you submit, in the same way any visitor or crawler would, and read the HTML those pages return. We only fetch publicly reachable pages. We do not attempt to bypass access controls, and we do not submit forms or take any action on the site.

Please only audit sites you own or are authorised to test.

How long we keep it

• Rate-limiting records are held in memory only and are discarded when their time window passes or the service restarts.
• Operational logs are kept only as long as needed to diagnose problems.
• Saved audit reports are deleted 90 days after they are created, or sooner on request.
• Email addresses are kept until you ask us to remove them.
• When you unsubscribe from monitoring, we stop sending immediately and keep a record that you unsubscribed. We keep it deliberately: a deleted record can be recreated by a later signup and start sending again, and a suppressed one cannot. If you want the record deleted rather than suppressed, ask us and we will delete it.
• Monitoring requests that are never confirmed are deleted when their confirmation link expires.

Third parties

The service currently loads no advertising or analytics scripts, and sets no tracking cookies. Web fonts are served by Google Fonts, which means your browser makes a request to Google to retrieve them.

If you ask us to monitor a website, we send the resulting email through Brevo, an email delivery provider, which processes your email address and the contents of those messages in order to deliver them. Brevo acts on our instructions and does not use your address for its own purposes.

We intend to add analytics and advertising on our editorial pages in future. When we do, this policy will be updated before those scripts are enabled, and the relevant consent controls will be in place.

Your rights

You can ask what we hold relating to your requests and ask us to delete it. Email hello@example.invalid. Because we do not require accounts, we may need details such as the approximate time and the address you audited in order to locate anything.

Changes

When this policy changes materially we will update the date above and describe what changed. The service is in beta and its data handling will evolve as features are added.