Trust, kept visible.

This is the current trust baseline for Harper Relay. It explains what the live stack stores today, which intake paths are open, what still routes through the company desk, and where a direct privacy owner still needs to be named.

Open the company desk About Harper Relay

Current build status

Search persistence may be enabled on the server through Supabase.

AI Visibility Audit runs a short public brief; Lead Manager and linked workflow pilots still route through the Harper Relay company desk.

The company desk is live for review requests, but broader privacy-owner handling still needs a dedicated public owner before launch-ready trust can be claimed.

Optional analytics, pixels, and profiling are controlled by the privacy choices layer and stay off in essential-only mode.

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.

What the current stack collects

Search queries, audit briefs, and routed workflow notes tied to the live linked surfaces

When someone runs a domain search, the app can store the query, normalized candidates, provider coverage, pricing fields, evidence, and generated timestamps so recent results can be reused instead of recomputed on every request.

Service intake status

AI Visibility Audit accepts a short public brief, while Lead Manager setup now starts through CRM onboarding

The AI Visibility Audit page now publishes a short public brief for full report requests. The site also exposes a CRM onboarding route at /crm-onboarding for Lead Manager setup packages and a contact-routing page at /contact for human follow-up. Lead Manager still stays clear that it is not a separate finished lead vault or client portal on the public site. The broader direct public owner still needs final approval before launch-ready handling can be claimed.

Storage and processors

Search snapshots, audit brief requests, and contact requests may be written to Supabase when server persistence is enabled

This build is configured to use Supabase on the server for optional search persistence, Market R queue governance, AI Visibility Audit brief capture, and contact-request storage when the storage layer is available. If the relevant table or credentials are not ready, the intake falls back to manual pilot handling without claiming the write succeeded.

Cookies and similar tech

Non-essential analytics, pixels, and visitor profiling are consent-gated

Harper Relay now ships a first-party privacy choices layer. Essential site functions can run without opt-in. Optional analytics can record page views and CTA clicks after consent. Marketing pixels and persistent visitor profiling stay off unless the visitor chooses them, and Global Privacy Control is treated as a do-not-sell/share signal where the browser exposes it.

Visitor profiles and exports

The tracking layer is built for portable events, not hidden surveillance

When analytics or profiling is allowed, Harper Relay can create a first-party visitor ID, keep a limited local event queue, and push consent-approved events into window.dataLayer so external suites such as GA4, tag managers, CRM pixels, or future customer-data tools can consume them. The current implementation does not turn on session replay, keystroke logging, or marketing retargeting by default.

Traffic intelligence signals

Hover, scroll, and section dwell are used as coarse interest signals, not eye tracking

With analytics consent, Harper Relay can record page path, source/referrer, UTM values, CTA clicks, scroll-depth milestones, hover dwell on labeled controls, and section exposure/dwell. These signals help identify which offer, industry, or handoff path is getting attention. They do not capture typed form content, passwords, payment data, keystrokes, screen recordings, or actual gaze/eye movement.

Industry selection and prediction

Visitors can self-identify an industry, and profiling consent controls persistent prediction

Industry selector buttons may record a visitor's chosen industry after analytics consent. A persistent prediction profile that scores industry fit, lifecycle stage, and likely follow-up path is only retained when profiling is allowed. Essential-only mode skips this layer, and Global Privacy Control disables marketing and profiling where the browser exposes that signal.

Enrichment boundaries

External matching should stay company-level, consent-aware, and reviewable

Harper Relay may later enrich declared company, domain, industry, or source data with customer-approved tools, but this policy does not authorize covert personal identity enrichment. Any CRM, ad platform, data warehouse, or customer-data platform connected later must respect the same consent state, Do Not Sell or Share posture, and export/delete review path.

Choice and opt-out

Visitors can choose essential-only, analytics, or broader marketing/profiling permissions

The cookie banner and Privacy choices control let visitors keep tracking essential-only, allow basic analytics, or explicitly allow marketing and profile-building. A Do Not Sell or Share posture disables marketing and profiling. If a configured third-party pixel is added later, it must remain behind the same consent gate rather than loading before the visitor chooses.

Currently In Scope

domain-search queries and generated comparison outputs

linked workflow and company-desk context used to keep Harper Relay trust paths attached

AI Visibility Audit brief submissions: website URL, first name, email, optional phone/company/service/market context, and preview notes for manual follow-up

contact message desk submissions: first name, last name, email, message, human verification status, optional phone, customer type, company, address, website or route, request type, quick-note seed, and optional discount or phone-follow-up preferences, but not passwords, payment card data, or private secrets

a Harper Relay Lead Manager page that explains lead capture, qualification, routing, and owner-digest handling, plus a CRM onboarding route that collects setup priorities without creating a separate public lead vault

a Harper Relay company desk that routes site-review and workflow-module requests to the clearest live surface

provider source URLs and evidence used to explain pricing

queue-governance metadata for internal lane work

Still Not Live

dedicated public intake forms on Local Service Front Desk or Member Concierge

a separate public login, lead vault, or file-upload flow on the Lead Manager page

a dedicated operator-owned public mailbox or verified privacy-request owner

session replay, keystroke logging, or advertising pixels that load before consent

Trust Routing

Trust requests need an owner, not a maze.

The policy route and company desk are live now. The last trust upgrade is simple and human: name the operator-approved mailbox or verified privacy-request owner so every sensitive question has a direct path.

Open the company desk Scenario Demos CRM Login