Clear handling for every request.

What this policy covers

BuildVaro helps contractors respond to website leads, collect the important job details, and keep configured follow-up moving. This policy explains the information handled when a homeowner submits a public service request or when a contractor creates an account and uses the lead-response workflow.

BuildVaro is designed to support a clearer first handoff. It does not make the contractor’s pricing, availability, appointment, or revenue decisions.

Information collected

The public lead form collects the information a homeowner chooses to submit: name, email, phone, service needed, property or job context, area, description, an optional preferred appointment time, and answers to any questions configured by the contractor for that service type.

When a contractor creates an account, the current signup flow collects a business name, email address, and password, then creates the contractor workspace used to manage the lead-response workflow.

How the information is used

• Save and route a service request to the contractor account associated with the public form.
• Give the contractor the job context needed to review the request and choose the next step.
• Send the homeowner a transparent automated acknowledgment and notify the contractor when delivery is confirmed.
• Send configured first and second follow-up emails while a lead remains eligible for follow-up.
• Operate, secure, and improve the website, account, lead, email, and analytics workflows.

Who receives the information

A submitted lead is routed to the contractor account operating the BuildVaro service surface. The email address provided by the homeowner receives the acknowledgment and, when configured and still eligible, follow-up emails. The application also uses its hosting, database, email-delivery, and platform analytics services to operate these workflows.

BuildVaro does not claim that submitting a request creates a booking, a price, or revenue for the homeowner or contractor.

Acknowledgments, follow-ups, and opt-out

After a lead is saved, BuildVaro attempts to send a homeowner acknowledgment and contractor notification. The acknowledgment explains that no appointment or price was promised automatically. Configured follow-up work is intended to keep the conversation moving while the lead is still new; it stops when the workflow no longer considers the lead eligible or when the homeowner opts out.

Each follow-up email includes a “Stop receiving follow-ups” link. That link resolves to BuildVaro’s opt-out endpoint and updates the lead’s follow-up preference. This path is for stopping the configured follow-up emails; it is not a promise that the underlying lead record is deleted or that a request will receive a specific response time.

Analytics and browser technologies

BuildVaro’s public-site tracker records page views, visitor and session identifiers, traffic source information derived from UTM parameters or referrer data, CTA clicks, and form submissions. The current tracker stores its visitor identifier and source in localStorage and its session identifier in sessionStorage; it does not set a cookie for those events.

The app also includes a deploy-configured platform analytics beacon that uses a browser-stored visitor identifier for page-load measurement. Other parts of the site, including account and session features, may use cookies or similar browser technologies as needed to operate those features.

Questions

Questions about this policy can be sent to buildvaro@polsia.app. The owner-review items below identify details that still need to be confirmed before this policy is treated as final legal copy.