Privacy

Last updated July 24, 2026. Buyer-introduction and provider-listing forms collect the contact, broad location, project, company, and request details shown on each form so the editorial team can review and respond to a request.

Technical data

Like most websites, hosting and security infrastructure may process routine request information needed to deliver and protect the site, such as network and device information, timestamps, requested paths, and diagnostic records. Final production providers and retention practices will be documented before launch.

Analytics

Microsoft Clarity may load in production only when a valid project identifier is configured and the configured consent state is granted. Form regions are masked. Names, email addresses, phone numbers, street addresses, postal codes, and free-text messages are not analytics event properties.

Inquiry processing

Valid requests are stored in Supabase before Resend is used for operator notification and, when enabled, visitor confirmation. Cloudflare Turnstile checks submissions for automated abuse; its token is not stored in the lead record. Permission to contact a buyer and optional permission to share an inquiry with suitable providers are presented separately. No inquiry is automatically forwarded to a provider.

Minimization and attribution

The forms do not request an exact home address. Stored attribution is limited to the page path, allowlisted campaign and click identifiers when present, and the referring site origin—not its path or query. Raw IP addresses are not stored merely for analytics. Retention and deletion schedules must be finalized before public production launch.

External links

External websites have their own privacy practices. Review their policies before providing information.

Contact

Use the site contact channel for privacy questions. Do not place sensitive personal information in a request. This page should not be read as a claim of compliance with every law in every jurisdiction.