Privacy
This is the current trust baseline for Harper Relay Lead Manager. It explains what the live desk stores today, what stays route-attached at the handoff, what still does not exist as a separate lead-vault surface, and where a direct privacy owner still needs to be named.
Current build status
Policy Scope
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
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
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
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
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
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
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
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
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
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
Still Not Live
Trust Routing
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.