Privacy and lead routing notice
BackflowPath stores contact requests so the team can review utility context, route sponsor coverage where it exists, and follow up on local compliance questions.
Plain language
What the form data is used for
Lead requests are used to review demand, understand the utility page that generated the request, and route follow-up when there is a clearly labeled provider path.
Stored request data
- Name, phone, email, city, property type, issue type, and notes from the form.
- Utility ID, utility name, page family, source page, and referring page when available.
- Delivery and assignment records when a request is routed internally.
Official guidance stays separate
- Submitting a request does not change the underlying utility rule.
- BackflowPath keeps official authority guidance and sponsor routing separate.
- The same request is not resold to multiple providers without user consent.
Storage and review posture
Lead requests are stored in the file-backed leads workspace used by this application. Access is intended for internal review, sponsor routing operations, and manual follow-up.
Questions about a stored request should be handled through the reply path used for the submission or through the utility-specific page that generated the request.