Privacy policy — launch draft
Updated October 9, 2026. This is a description of the implemented service, not a legally reviewed policy. The legal operator identity and jurisdiction-specific notices must be finalized before a public paid launch. No physical address or contact inbox is represented here.
What we collect
If you request an installer review, we save your name, email, phone, address, state, ZIP code, homeowner confirmation, timeline, any available estimate context, exact consent text/version and submission time. An inquiry starts unqualified; an operator must review it before referral.
When a roof estimate is available, your inquiry includes the selected system-size scenario and planner settings: electricity usage, utility and rates, your confirmation choices, assumed installation price, financing, maintenance, replacement and long-term financial assumptions. Incomplete monthly readings are retained as a draft, not verified usage. These are visitor-selected scenarios, not verified bills or installer quotes. Editing the property address in the inquiry form removes the previous roof’s estimate. Separate supported-layout and manual proposal-calculator drafts—including entered prices, capacity and production—remain in page memory and are not submitted. Planner settings are never sent to optional analytics.
Allowlisted campaign parameters and advertising click identifiers from your landing page are held in memory for attribution when you submit an inquiry. Without optional analytics consent, we do not create an analytics session reference or store this attribution in browser storage. If you allow analytics, session storage remembers a random per-tab reference and inquiry attribution. These are used only by our first-party operational reports and inquiry records, never sent to Umami. Attribution is not an automatic ad-platform conversion upload. Do not put personal data in advertising campaign labels.
The server uses connection information for abuse prevention. Hosting and infrastructure providers may maintain access logs. This application does not log inquiry contact details or full request bodies. Server records of submitted inquiries and their review, referral and sale outcomes remain available whether or not you allow optional analytics.
Optional analytics and browser preferences
Analytics is off by default. Use the always-available “Privacy choices” button to allow or decline it, or withdraw your choice later. Declining does not affect estimates, inquiries or installer access. Do Not Track and Global Privacy Control override an opt-in. We remember your versioned preference in local storage for 180 days, then ask again. This preference contains a choice and timestamp, not a tracking identifier; if browser storage is unavailable, it lasts only for the current visit.
After opt-in, our first-party event log and self-hosted Umami collect visits to a small allowlist of public pages and named interactions such as opening the inquiry form or completing an estimate. Umami receives only those public paths, restricted campaign source/medium/name labels, referring website origins without their paths or searches, and browser metadata such as language, screen size and browser/operating-system type. It does not receive contact details, property addresses, roof-image URLs, lead IDs, our per-tab references, estimate or financial values, arbitrary query strings, URL fragments or full referrer URLs. Installer portal pages are excluded. We do not use session recordings, heatmaps or advertising pixels.
Umami runs on infrastructure shared with our FretReady service, with a separate solar website and restricted solar account; the other site’s reports are not combined with solar reports. The server processes your IP address and user-agent metadata to derive short-lived analytics identifiers and approximate location rather than storing a raw IP address in Umami event records. An opaque Umami session/cache token is held only in page memory, not cookies or browser storage. Optional analytics records are retained for 90 days; analytics upgrade backups are retained for seven days.
Withdrawal stops new analytics requests, cancels in-flight browser requests where possible, clears analytics session storage and in-memory tokens, and applies across tabs. Browser signals and preference expiry also stop collection. Cancellation cannot retract events that the server already received. It does not delete an inquiry you asked us to save; use the data-request form below for that.
Providers and installer sharing
New Orleans address suggestions use a local copy of the city’s public building address points. When that index has no match, the search text is sent to Photon / OpenStreetMap. Local matches do not require a third-party search request. Our server downloads public USGS LiDAR and Microsoft building footprints and reconstructs the requested building. Weather requests send location coordinates to the European Commission Joint Research Centre’s PVGIS service. Aerial-image requests send a geographic viewport to Louisiana DOTD / NORPC. Those external services process requests under their own terms. The planner displays attribution for its imagery and data sources; your contact details are not needed for these requests.
Analysis jobs and reusable geospatial results are cached by coordinates, not by your selected address label or contact details. The worker can reuse a completed analysis for 30 days; this cache period is not a promise that source downloads or expired job records are immediately erased. Stopping browser polling does not delete or cancel a shared server-side job.
With your explicit consent, one approved installer may receive your contact details, property information and estimate for a solar discussion. We may receive a referral fee when that installer purchases the inquiry. Approval is an internal access decision, not a warranty of workmanship, credentials or suitability. Installer availability is not guaranteed. Payment services process installer payments; homeowners do not pay through the inquiry form.
If configured, an internal signed notification webhook receives an inquiry reference and status, not your name, email, phone or address. Operators can review the saved inquiry locally. We do not automatically email you or promise an installer has been contacted.
Storage and retention
Inquiries, consent and review history are stored in server-side files. The configured retention operation removes inquiry and first-party event records older than 90 days; this requires the operator to run or schedule it. Privacy request records are also purged after 90 days. Service operators must restrict file access and handle backups on the same retention schedule. An inquiry older than 30 days is not offered for a new sale.
Installer payment and ownership records may be retained separately for accounting, disputes and legal obligations. An installer that already received an inquiry may hold its own copy; we must forward verified withdrawal or deletion requests to that recipient. Removing a record here does not erase an external recipient’s copy or an independently retained financial record.
Deletion and withdrawal requests
This form saves a real local request for operator review. It does not send an email or delete someone’s records based only on an unverified email address. An operator must verify authority through the submitted contact, stop further sharing, process deletion and contact any prior recipient as applicable. Do not submit sensitive documents here.