Pilot website notice

Privacy, in plain language.

This notice covers the Recover acquisition website and Lead Leak Test request form. It does not replace the customer-and-lead privacy terms required before a live pilot processes real service-business leads.

What we collect

If you submit the form, we collect the contact and business details you provide: business name, work email, website, role, service region, inbound-call volume band, missed-call handling, changeable phone paths, routing constraint and outcome-tracking capability. If you separately request a call, we also collect the business phone, preferred time window and exact call-agreement evidence.

We also record limited first-party funnel events such as a page visit, CTA click, form start, and accepted submission. Those records use a random session identifier. The funnel record does not include your IP address or browser user-agent string, submitted email, phone, business name or region value.

Why we use it

We use the information to respond to your request, evaluate whether the Lead Leak Test fits your business, improve the acquisition flow, and measure interest in Recover. We do not use submitted information to train unrelated models or sell it as a contact list.

Service providers and location

The pilot stack uses hosting and database providers to operate the form and store requests. Depending on final deployment configuration, information may be processed outside Canada. The production subprocessor inventory and customer-lead terms remain a separate launch gate.

Your choices

Submitting the form asks Recover to contact you about that request. You may withdraw the request, ask what information is held, or request correction or deletion through the contact below. Withdrawal does not affect processing already completed before the request was received. The confirmation screen also provides an opaque withdrawal control; withdrawal revokes that exact request. Because a public form does not prove control of an email address or phone number, an unverified request cannot add destination-wide suppression for somebody else. If control was independently verified, withdrawal may retain only a hashed channel-level suppression so that destination is not contacted again.

Contact

Public contact details are not configured because production intake is disabled. A real contact address is required before this form can accept production requests.

Last updated: August 25, 2026