Current prelaunch behavior
The form is available for preview but will not send entered contact details while delivery is disabled. Entries remain in the page while it is open; this site does not save them to browser storage. Closing or reloading the page clears them. Direct requests to the disabled intake endpoint are rejected.
The local server may process ordinary technical request information needed to serve pages. No live receiving service or analytics processor is connected by this build. The lead inquiry number is configured; call routing has not been independently tested.
Information an enabled inquiry would use
A future enabled form would use your name, phone, email, property address, city, ZIP code, driveway status, main issue, and any optional length, contact-time, or notes you provide. Required consent would authorize contact about that particular inquiry.
Do not include payment details, identification documents, medical information, or other sensitive information. Photo uploads are not supported.
Potential sharing and purpose
After a reviewed launch, inquiry details may be shared with a potential driveway professional to discuss location, project fit, and possible work. A receiving-service processor may handle delivery. The operator must identify the actual operator, recipients or recipient categories, processors, and contact method before collection begins.
Inquiry information is intended for responding to and routing your request. This preview does not enable unrelated marketing, sale of lead data, or automated advertising tracking. Any future changes require a clear, accurate policy and applicable consent.
Analytics and cookies
Conversion hooks use only the fixed names call_click, quote_click, and quote_delivered. With analytics disabled, these hooks transmit no data. No names, addresses, phone numbers, form notes, or other inquiry details belong in analytics events.
If delivery is later enabled, a short-lived, HTTP-only receipt cookie would allow the confirmation page to verify a successful delivery. It contains no inquiry details. Optional analytics providers and any consent controls must be reviewed before use.
Retention, requests, and operator review
Because live collection is disabled, this build establishes no live lead database or retention schedule. Before launch, the operator must publish an accurate retention period, data-request contact, processor arrangements, and procedures for access, correction, deletion, and withdrawal of consent where applicable.
This policy needs final operator review before live lead collection. Do not enable collection until the missing operator and data-handling details are completed.
