Privacy, in plain language.

Public-site measurement

We use Vercel Web Analytics for aggregate public-page views, device and traffic-source information, main button clicks, and broad project-form progress. We use Google Ads tagging to measure advertising and a successfully saved project request. A submission is not the same as a qualified lead, contractor match, or completed job.

Information kept out of event data

Our measurement events use a fixed list of page paths and action labels, not names, email addresses, phone numbers, street addresses, typed answers, chat contents, uploaded documents, passwords, or authentication codes. We strip query strings and fragments from the page URLs we explicitly send. We do not use session replay or keystroke recording.

Advertising cookies and providers

Google’s tag may use first-party advertising cookies and ad-click identifiers to connect a visit with an ad. Google and Vercel also receive technical request information, such as IP address and browser information, when their services are contacted. Browser privacy settings and blockers can limit measurement. See how Google uses information from partner sites and Vercel’s analytics privacy information.

Private areas and testing

Sign-in, password reset, authentication callbacks, dashboards, contractor work areas, and admin screens do not load our analytics or Google Ads tags. Crossing between public pages and those areas opens a fresh page so an already-loaded tag does not carry into a private screen. Visits marked as test traffic are excluded for the rest of that browser-tab session.

Information needed to handle a request

Project answers, contact details, and uploaded files are operational records, separate from public-site measurement. They are used to review a request and arrange contractor participation. Please do not include payment information, passwords, or unrelated sensitive documents in forms or website help messages.