domain8.me

Search first

Back To AI Site Optimizer

Privacy

Trust, kept visible.

This is the current implementation baseline for Domain8 and its pilot pages. It explains what the app stores today, how outbound registrar clicks are routed and logged, which audit intake path is live, what is still not launch-ready, and why the site should not be treated as fully complete until the broader public contact owner is finalized for general privacy requests.

Current build status

Search persistence may be enabled on the server through Supabase.
Registrar quote clicks can pass through /api/outbound so approved, provisional, or direct-source routing stays auditable without changing ranking order.
AI Site Optimizer runs a short public brief; Member Concierge and Local Service Front Desk route through the shared contact desk.
Lead Manager is now a public workflow preview, but lead-flow requests still route through the same message desk instead of a separate live portal login.
A contact-routing page now exists, but the direct operator-owned public contact owner for broader privacy requests is still the main trust blocker before launch.

Policy Scope

Keep the collection story honest and narrowly described.

This page is written to describe current functionality, not a hypothetical future stack. If the app later expands intake beyond the current audit brief or adds tracking, the policy needs to move with it.

01

What this optimizer brief collects

Only the short brief and routed desk details needed to decide the next honest move

The AI Site Optimizer route can collect the website URL, first name, email, optional phone and company, optional service or market context, and the preview-backed brief needed to review whether the next step is a full ranked report, a bounded repair lane, or the generator plan. If someone uses the route-attached desk instead, the note keeps /ai-visibility-audit attached instead of flattening the question into generic contact.

02

What this route does not create

AI Site Optimizer still avoids dashboard, guaranteed ranking, and hidden-report claims

The public flow does not promise ranking lifts, does not open a hidden client dashboard, does not create always-on live chat, and does not pretend every report request is already stored or instantly approved. The quick read is a preview, and the next human step stays explicit.

03

Storage and processors

AI Site Optimizer briefs may write to Supabase on the server, with the route-attached desk falling back honestly when storage is not ready

When the AI brief storage layer is available, full-report requests can write to Supabase on the server. When it is unavailable, the audit flow stays in pilot mode and queues manual follow-up instead of pretending the brief was saved. If someone messages the route-attached desk instead, the note uses the same contact-request storage and truthful fallback used elsewhere on the site.

04

Cookies and similar tech

Optional tracking stays behind the privacy choices layer

Optional analytics and marketing pixels should stay behind consent before this AI Site Optimizer route is treated as launch-complete. The current route does not use session replay, keystroke logging, or automatic marketing retargeting by default.

Currently In Scope

the AI Site Optimizer quick read stays in the browser until someone asks for the deeper report
AI Site Optimizer brief requests can collect the website URL, first name, email, optional phone and company, optional service or market context, and preview-backed notes for manual review
the route-attached audit desk at /contact?from=ai-visibility-audit#message-desk keeps the quick-read, ranked-report, or generator-path question attached instead of dropping into generic contact
pilot-mode manual-follow-up receipts remain in place when either the AI brief storage layer or the contact-request storage layer is unavailable on the current run
route-aware privacy and about pages now keep the audit story attached when someone checks storage, tracking, or who is behind the work
domain-search queries, generated comparison snapshots, and queue-governance metadata may still exist elsewhere on the site

Still Not Live

guaranteed ranking lifts or answer-engine placement promises on the public AI Site Optimizer route
a hidden client dashboard, separate login, or stored-report library
an always-on live chat or instant human audit queue
a dedicated public privacy-request owner approved for broader site handling
session replay, keystroke logging, or advertising pixels that load before consent

Current Limitation

Privacy requests still need a dedicated public owner before launch.

This repo now exposes both the policy route and a public contact-routing page, but it still needs an operator-approved direct mailbox or verified privacy-request owner before the site can honestly call the trust path complete.

Review Contact PathsReview Domain8 WorkflowsAbout Harper Relay