Privacy and Data Handling

Cost or decision direction

Privacy choices do not change a sewer quote directly, but they do affect whether users feel safe enough to submit a credible request.

What SewerClarity collects

The site is built to keep forms short and routing-focused.

• Estimator and lead flows can store the role, ZIP or city, house age band, issue state, defect type, urgency, and the route the product recommended.
• Lead forms can store name, email, phone, optional notes, and explicit consent status.
• Attribution fields such as UTM parameters, gclid, wbraid, and gbraid may be stored when they are present.
• Basic event logging is used to understand estimator completion, CTA clicks, invalid submits, and summary-copy behavior.

Why that data is stored

The goal is routing quality and product improvement, not collecting extra profile data.

• Lead details help SewerClarity decide whether the user is better matched to inspection-first or quote-ready follow-up.
• Event data helps identify where users stop, submit, or drop out.
• Attribution data helps inspect which pages and channels produce commercially plausible demand.
• Source and routing context make submitted requests more usable than a bare contact form.

When information may be shared

Lead routing only works if the submitted details can be used for the next relevant step.

• If SewerClarity routes a request to an inspection or repair option, the practical details needed to make that request usable may be shared for that purpose.
• Do not assume every request is automatically forwarded. Routing still depends on fit, evidence state, and operational readiness.
• SewerClarity should not share more than the request needs to be actioned credibly.
• If a user does not want to be contacted, the lead form should not be submitted.

Questions, corrections, and requests

A trust-first site should make it easy to flag a data or source concern.

• Use the contact address shown on the site for privacy questions, correction requests, or source issues.
• Include the page URL or request context so the issue can be reviewed quickly.
• Avoid sending extra sensitive information that is not needed to resolve the issue.
• Privacy and correction handling are part of operating the product responsibly.

What commonly changes the answer

• Lead storage should stay short, practical, and consent-based.
• Routing quality is the main reason the site stores more than a pageview.

Questions to ask next

1. What details are actually needed to make this request usable?
2. Would I still submit this form if the site could not explain what happens next?

Keep moving with the right follow-up page

These pages usually answer the next decision users have after this one.

More in this topic

Use this topic cluster when you want the wider buyer, defect, cost, coverage, or trust context instead of only the next follow-up page.

FAQ