Privacy Policy

The service's legal operator, business address, jurisdiction, and governing law have not been provided. The owner must supply those details before treating this policy as final.

Based on the current app fields, information can include:

• Company account and setup details, such as company and contact names, account email, phone, website, service area, ZIP codes, business hours, notification destinations, and a saved booking link.
• Homeowner service-request details, such as name, email or phone when provided, service needs, ZIP code, urgency, service category, preferred appointment time, and recorded consent choices. A public booking also records the selected appointment time and associated booking details.
• Workspace records associated with requests, including status changes and any message entries created in the app, configured follow-up email templates, and follow-up attempt statuses. Demo conversation entries are marked as simulated. Opt-out links are stored as token hashes.

The app receives HVAC service requests and makes them available in the associated company's private workspace for review and status management. The public booking page checks that company's configured availability; when a homeowner selects an opening, the app saves the request as a lead and creates an appointment record in that company's workspace. This does not create an external calendar event. It records a required service-response consent choice separately from an optional follow-up-email consent choice. When separately authorized by that choice, a configured follow-up sequence may be processed; automated email delivery is disabled app-wide by default. The app records whether an attempt was accepted by the email provider, failed, suppressed, or simulated. Provider acceptance does not confirm recipient delivery. Contractors can configure consent-aware email follow-up sequences. Each homeowner must separately choose email follow-up, and app-wide delivery remains disabled until the owner authorizes the Polsia email proxy and verifies the sender. Automated response and qualification workflows are available in simulation; live SMS requires an approved messaging provider to be connected and verified. Each contractor can share a ServiceNudge booking page with real openings from its configured schedule; external calendar sync is not available.

Any purposes beyond providing the current account and request-review features need company confirmation. The owner must identify any additional purposes before this policy is treated as final.

A service request is made available to the company associated with its intake form so that company can review it. The billing flow uses Stripe-hosted checkout and subscription-management pages. The information shared with Stripe and the roles of other hosting, analytics, email, or support providers need company confirmation.

• The owner must confirm the complete provider inventory and the information each provider receives before this policy is treated as final.
• The owner must confirm any sharing with HVAC contractors or other recipients beyond the associated company workspace before this policy is treated as final.

The app schema does not establish a retention or deletion schedule. The owner must confirm how long account and request records are kept and how deletion is handled before this policy is treated as final.

The owner must provide a privacy-request channel and response process. Contact Support is shown below for general support; it is not described here as a verified privacy-request workflow.

The owner must confirm security practices and any specific security commitments before adding them to this policy.

The app code alone does not establish a complete cookie, local-storage, analytics, or tracking disclosure. The owner must confirm the technologies used and their purposes before completing this section.

For general support, use Contact Support. The owner must add a verified privacy-request process before publishing final policy language.