Privacy / Prototype notice

Understand what you share.

This notice describes the prototype’s data flows and their limits. It is not a claim that every integration is active.

Information used by the application

  • Search and analysis: entered addresses, selected coordinates, search radius, filters and roof assumptions are processed to find and compare properties. Selecting a place is not the same as granting continuous device-location access.
  • Saved leads: property identifiers, addresses, coordinates, opportunity scores, workflow status, notes, list names and creation times may be stored when you choose to save a lead. Keep private resident information out of notes.
  • Inquiries: contact details and the project information you choose to submit are used to respond. Do not include passwords, payment information, health information or confidential documents.
  • Imagery: where an image-analysis feature is enabled, permitted imagery and its source/date metadata may be sent to an AI provider. Submit only imagery you are authorized to share for that purpose.
  • Operations: the hosting platform and providers may process request metadata such as IP address, browser information, timestamps and error records to deliver and protect the service.

Where information may go

Configured Google Maps, Geocoding and Solar services may receive map requests, address queries or selected locations. Configured Earth Engine processing may receive an area of interest. If Gemini image analysis is enabled, the selected image and prompt are processed under the operator’s applicable Google service terms. Provider processing and retention depend on the selected service and account; we do not promise zero retention or a particular training-data policy here.

A fallback map may request OpenStreetMap-based tiles from its configured tile host, which can receive browser request metadata and the map area viewed. A hosted database may store saved leads and inquiries. Contact delivery, hosting and analytics depend on the deployed configuration; listing an integration here is not proof it is enabled.

Sessions, storage and analytics

The persistence contract allows an anonymous HttpOnly session cookie to separate saved records. That cookie is not a verified user account or a substitute for team authentication. Clearing cookies can break access to session-linked records; it does not necessarily delete server-side records.

Production persistence requires a configured database. Any temporary development fallback is not durable storage. Export only the records you need and protect downloaded reports and CSV files yourself.

Analytics events, consent requirements and provider settings require deployment review. Do not assume that the absence of a sign-in form means browsing is anonymous to infrastructure providers. Sensitive free text, full addresses, imagery and contact details should not be included in analytics events.

Retention, choices and requests

A verified retention and deletion schedule has not yet been published. No fixed deletion period, data-residency commitment or completed rights workflow is represented by this prototype notice. The operator must establish those controls before accepting production personal data.

You can explore synthetic Demo Data without entering a personal address or saving a contact inquiry. Avoid uploading identifying imagery and avoid recording owner or occupant details without a lawful purpose.

Use the contact page for a privacy inquiry if its delivery channel is available. Do not submit identity documents in an initial request. A verified operator contact and applicable access, correction, deletion and objection process must be provided before production use; this draft does not restrict rights available under applicable law.

Security and changes

No internet service can promise absolute security. Server-side credentials, access restrictions, validation and reasonable operational safeguards are required, but this notice is not a security certification. Review the notice when integrations change, especially before sending real lead records or imagery.

Read the terms and use limitations