Your details are for your service request. Not a mailing list.

Drafted November 6, 2026. This is a working template, not legal advice. The business owner and counsel should review and approve the final policy, consent language, vendor disclosures and retention schedule before launch.

1. Who handles your information

The intended business is Operator identity pending, using the working brand Hearth & Rain. The actual legal operator and any separate service partners must be named before launch.

Address: Address coming soon
Email: Use the callback form (placeholder—replace with a monitored address)
Phone: Phone number pending — use the callback form
Service partners: Fluevia is the proposed lead-gen brand; its legal operator and any contractors must be identified by role or name and disclosed before launch — TODO.

2. Information the live form requests

The short form asks for your name, phone number, property ZIP, requested service and best callback time, plus your consent to be contacted. These are collected to respond to your request, discuss a suitable service, verify service coverage and coordinate an appointment. Do not send financial information, sensitive health information or full payment details through this form.

3. Calls, text messages and campaign information

In the live form, you may agree to calls or texts from the operator and specifically identified service partners about your request, including through automated technology. Consent is not a condition of buying a service. Message and data rates may apply. You can withdraw this consent, and you may reply STOP to texts; you may also contact the business using a valid phone or email provided before launch. Honor opt-outs and do not subscribe requesters to a separate promotional list merely because they asked for a callback.

Technical and campaign information may include UTM parameters, ad platform click IDs, the page visited, referring page, submission timestamp and standard device/browser logs, where collected by the eventual host. UTM parameters and click IDs are currently kept in the browser's session storage, not sent in preview mode. Production hosting and logs should be reviewed for confidentiality, access and retention.

4. Where requests go

The intended live destination is a business-controlled lead-delivery endpoint and CRM. [TODO: document the actual endpoint, CRM and processors, who receives the information, storage locations, transfer conditions and notification systems.] The operator should disclose sharing needed to route the request or deliver the chosen service; service providers must not receive more access than required.

5. Retention, access and deletion requests

[TODO: specify a real retention period for requests, spam and unsuccessful leads, consistent with recordkeeping and dispute obligations.] The owner should establish a secure process to review access/deletion or opt-out requests, verify the identity of the requester, and stop unnecessary contact. Washington and federal rules may apply depending on the operating entity and communications used.

6. Security

The live form should use HTTPS and a business-controlled backend with validation, restricted access, rate-limiting, server-side logging minimization, and incident response. No method of transmission is guaranteed secure. The source code uses no third-party tracking or outbound lead delivery in preview mode.

7. Analytics and advertising pixels

The Facebook Pixel snippet is commented out; no real pixel ID is present. Before activation, review cookie/analytics notice and consent requirements, vendor sharing and consumer choices. Activate only a real, business-owned measurement setup after approval, and document it here.

8. Children

These services are for homeowners or authorized property contacts, not children. The form is not designed to collect information from children under 13. Any inadvertently supplied child information should be reviewed for deletion.

9. Updates and contact

The finalized policy should show its effective date and material updates. Requests may be sent to Use the callback form, once replaced by a monitored email, or to the actual business address. A generic placeholder address must not appear on a production page.