Beacon · Privacy
Privacy, explained plainly
Last updated October 30, 2026
Beacon is an early-stage property-damage assistance and research platform. This notice describes information the current website and its forms ask for or record. The product is still being tested, and its features may change.
Information you provide
The public /get-help pilot asks for damage category, safety and utility concerns, property type, city/state or ZIP code, timing, severity, occupancy, desired help, name, email and optional phone. It does not ask for a street address or documents. Answers stay in page memory until you choose to save a request in this tab’s session storage. No contact details or request answers are sent to Beacon or providers by this pilot.
If you submit the provider-interest form, it asks for company and contact details, service categories and area, and responses about provider capabilities, availability, preferences, or interest. Some fields, such as phone number and notes, are optional.
Please keep notes relevant to the question. The current forms do not ask you to upload photos, insurance documents, or other files.
Website activity and browser storage
The public pilot records funnel events such as intake starts, category choices, essential-detail completion, safety escalation, contact-stage completion and local request saving. Custom events contain category and flow version, not names, email addresses, phone numbers, location or form answers. Other existing forms may record research-market context, experiment assignments or selected research responses. A random intake session identifier and campaign or source information may also be used to understand how people reach and move through the forms. The new /get-help pilot saves requests only in browser session storage, not the application database. Older separate campaign and provider-interest forms may store submissions in the application database; those are not the public pilot flow.
The site uses session storage for intake session identifiers, experiment choices, and campaign attribution values. When the PostHog analytics key is configured, the site also initializes PostHog page-view and interaction analytics. Its current configuration uses browser local storage and cookies for analytics persistence. Analytics availability depends on the site configuration.
How the information is used
Information submitted through the forms is used to receive and review help requests or provider-interest submissions, and to learn which questions, guidance, and product steps are useful. Funnel and analytics events are used to understand site and form activity and evaluate product changes.
Saving a request at /get-help does not send it for Beacon’s review and does not schedule a reply. It stays in this browser tab’s session storage. No service provider is contacted or matched. You can delete the saved request from the confirmation screen; closing the tab ends its storage session. Reloading starts the form again and does not restore the saved record. Avoid using a shared device for contact details.
Current limits
The local pilot provides a delete/start-again action on its confirmation screen. Existing backend submissions from other forms do not have a self-service deletion page or a published retention period. A dedicated privacy contact and backend retention policy remain to be established before broader operational use.