Trust, kept visible.

This is the current trust baseline for Harper Relay Context Relay. It explains what the live desk stores today, what stays route-attached at the handoff, what still does not count as a separate agency portal or analytics suite, 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.

Context Relay handoff reviews now route through the live Harper Relay desk with /agency-knowledge-bot attached and workflow-pilot context already selected.

This remains a governed context-review path, not a separate agency portal, hidden analytics suite, or autonomous support console.

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 this rollout path collects

Only the narrow handoff details needed to review stale answers, escalation gaps, and multi-account drift

The live Harper Relay desk collects first name, last name, email, message body, human verification status, optional phone, optional customer type and address, the attached route, request type, an optional quick-note seed, and optional discount or phone-follow-up preferences so an operator can review stale support answers, escalation rules, cross-account drift, or rollout ownership gaps.

What this route does not create

Context Relay stays honest about portals, analytics walls, and autonomous support

The public note is for the freshness break, escalation gap, or account boundary, not for passwords, payment data, or client secrets. This route does not create a private client login, hidden ticket queue, always-on support dashboard, or unsupervised answer-publishing lane.

Storage and processors

Contact requests may write to Supabase and notify handlers when email is configured

When the contact-request storage layer is available, the Context Relay desk can write the note to Supabase on the server. When storage is unavailable, the desk returns a truthful pilot-mode receipt and queues manual follow-up instead of claiming the write succeeded. Search snapshots, AI Visibility Audit briefs, and queue-governance metadata may also use the same server-side Supabase setup.

Cookies and similar tech

Optional tracking stays behind the privacy choices layer

On Harper Relay, optional analytics, marketing pixels, and visitor profiling are controlled by the privacy choices layer. Essential-only mode keeps non-essential tracking off. The current route does not use session replay, keystroke logging, or automatic marketing retargeting by default.

Currently In Scope

the route-attached Context Relay handoff at /contact?from=agency-knowledge-bot with workflow-pilot context already selected

shared-desk submissions: first name, last name, email, message, human verification status, optional phone, customer type, company, address, route, request type, quick-note seed, and optional discount or phone-follow-up preference

a public note that stays high-level and asks for the stale source, escalation gap, or account boundary instead of passwords, payment data, or client secrets

route-aware privacy and about pages that keep the Context Relay story attached instead of dropping into a generic Harper Relay trust page

pilot-mode manual-follow-up receipts when contact storage is unavailable on the current run

AI Visibility Audit briefs, domain-search queries, and generated comparison snapshots elsewhere on the site

queue-governance metadata used for internal lane work

Still Not Live

a separate agency portal, client login, or hidden analytics wall on the Context Relay route

unsupervised support autonomy or automatic answer publishing without human escalation

a dedicated public privacy-request owner approved for broader site handling

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 message desk Scenario Demos CRM Login