Public pages first
Most starting checks use pages anyone can visit. Private account data is considered only when it could answer a question public information cannot.
- We explain what each source can add before requesting access.
- Where account access is useful, we ask for an agreed, read-only scope. We do not ask you to send passwords.
- If information is missing or unavailable, the report says so instead of filling the gap with a guess.
How we keep decisions with you
- We treat website content as material to review, not instructions to follow.
- A person checks AI-assisted notes against their sources before making a recommendation.
- Website changes and customer-facing actions need separate approval. An agent does not publish or send them on its own.
Lessons from early testing
Separate drafts from live actions
Anything that could send or change something needs a human check and explicit approval before it happens.
Check tools before use
Tools and connections are reviewed before they are included in a business workflow. Unverified integrations stay out of scope.
Your information
Enquiry details are used to respond to your request. We do not publish client names or materials without written permission. Please do not include passwords, API keys or private customer information in the enquiry form.
Questions about access and safety
What access do you need for a website review?
We start with your public website. If another source would add useful evidence, we explain why and agree the access before requesting it.
Can an AI tool change my website or contact my customers?
No. Findings and drafts are reviewed by a person. Any website change or customer-facing action needs separate approval.
Is this a security certification or independent security audit?
No. This page describes practical safeguards used during search work; it is not a security certification or a full independent security assessment.
Ask what access your review would need
We will explain the sources and scope before you decide whether to proceed.