Privacy

How check-up requests are handled.

This page explains what is collected when you send a check-up request, what it is used for, and what is not needed for the first answer.

What is collected

The request form asks for a website, public page or business name, the messy workflow, an optional note on what would make it worth fixing, optional workflow frequency, optional current website or workflow tools, optional business type and area, a hidden service-interest value based on the page or offer button used, a reply email, session preference, and optional name and phone number.

The request may include the page used to submit it so the reply can match the right context.

Pilot contact

Sending a request does not create an account, subscription, booking or commitment.

To ask not to receive future pilot contact, use the check-up form and write "No further pilot contact".

What it is used for

Details are used to reply about the AI Business Check-Up, judge whether the £500 session looks useful, and explain the next step if it makes sense. Check-up requests are usually replied to within two working days.

If you add an optional phone number, it is only used when a quick call looks easier than a long email thread. The request still needs a reply email.

Request details are not used to add you to a newsletter or sold to another business.

What is not needed first

No passwords, tool access, private customer records or payment details are needed for the first answer.

Sending the request does not change your website, send customer messages or switch on automations. Those steps are agreed separately if you choose to book.

Customer-facing AI work should start as a draft, template or reviewed step unless you separately approve an automation that sends or changes something.

If a paid working session later needs access to a website, form, inbox or other tool, that is discussed separately before anything is shared.

Lead capture and analytics

The form is designed to send requests to a configured lead destination. If that destination is unavailable, the site reveals a copyable request draft so the text can be retried without being rewritten.

The site records simple first-party event counts such as form views, button clicks, selected workflow shortcuts and successful request submissions. These events use a temporary browser-session ID so the pilot can understand which parts of the page lead to requests.

The site does not load a third-party analytics script. Phone numbers, reply emails, names, website or business names and free-text form contents are not included in analytics events.

Retention and deletion

Check-up requests should only be kept for as long as needed to reply, handle the pilot, and keep a practical record of enquiry outcomes.

To ask for details to be corrected or deleted, use the check-up form and write "Correct or delete my details".