Privacy policy
Last updated 30 August 2026
Draft pending legal review
The short version
We collect as little as we can get away with. The contribution form has no field for your name, address, or your contractor’s name, so we cannot collect them even by accident. We do not sell anything to anyone, we run no advertising and no remarketing, and the only place we ask for contact details is a form that says plainly that nobody will call you. We do use Google Analytics to see which pages get used, with advertising features switched off — the detail is below.
What we collect, and why
| What | Fields | Why |
|---|---|---|
| Estimate requests | ZIP code, the project details you enter, the resulting range and confidence score, and an opaque session identifier. | To show you an estimate, and in aggregate to work out which cities to add local data for next. |
| Quote checks | The quoted amount you enter, the project details, and the verdict. | To show the comparison, and in aggregate to measure how our modelled ranges compare with real market quotes. |
| Uploaded contractor quotes | The figures and scope read out of the document: total, line items, material, warranty, what is included or excluded. The file itself is never stored, and we do not record your contractor's name, licence number or your address. | To fill in the comparison for you, and in aggregate to build a picture of real local quote pricing. |
| Contributed project costs | ZIP code, amount paid, the month the work finished, and optional project characteristics. | To improve the pricing model with real prices. Reviewed by a person before use, and only ever published combined with other projects. |
| Interest registrations | Name, email, optional phone, ZIP code, timeline. | So we can tell you if contractor matching becomes available in your area. Nothing else. |
| Analytics events | Event name from a fixed allow-list, non-identifying properties, the page path, and the session identifier. | To see which parts of the product get used and where people give up. |
What we deliberately do not collect
- Your name, address, or your contractor’s name on a contributed project cost. The form has no such fields.
- The exact date of a project. Contributions store the month only, because a precise date plus a ZIP code starts to identify a specific property.
- The contractor’s name, phone number, licence number, or your property address from an uploaded quote. The reader is instructed not to return them, and the data structure we store them into has no field for them.
- The uploaded file itself. It is held in memory for the length of the request and then discarded.
- Anything from advertising or remarketing networks. Google Analytics is the only third-party script on this site, and it runs with Google’s advertising features explicitly disabled, so it cannot be used to build an advertising audience from your visit.
- Free-text that looks like contact detail in analytics. The event endpoint strips anything resembling an email address or phone number before storing.
Consent
Contributed project costs and interest registrations both require you to tick an explicit consent box, and we store which version of the consent wording you agreed to. The current version identifier is 2026-08-contribute-v2. If the wording changes materially, the identifier changes with it, so we always know what any given contributor actually agreed to.
Cookies and local storage
- Session identifier — a random string in your browser’s
sessionStorage. It is not a cookie, it is not a fingerprint, and it is discarded when you close the tab. - Contractor question checklist — your ticked items are saved in
localStorageon your own device and are never sent to us. - Admin session cookie — set only for staff signing into the admin console. It is HTTP-only and scoped to
/admin. - Google Analytics cookies —
_gaand a related per-property cookie, set by Google to tell repeat visits apart. We send Google a truncated IP address and we have turned off Google Signals, which is the setting that would otherwise link your visit to a Google account for advertising. These are the only cookies set by anyone other than us.
We set no advertising, marketing or cross-site cookies of our own, and we run no remarketing or ad-network tags.
Who we share it with
Nobody. We do not sell, rent or trade personal data. We have no contractor network, no lead buyers and no advertising partners today. If that ever changes, any sharing of your details will require your specific, separate consent at the point of collection — not a quiet update to this page.
We use infrastructure providers to host the application and its database. They process data on our instructions only.
Google is the one exception worth naming. Google Analytics receives your truncated IP address, the pages you view and basic device information, and Google acts as a processor for that under its own terms. We have disabled the advertising features that would let it be used to target you elsewhere. If you would rather not be measured at all, Google publishes a browser opt-out add-on, and any tracker blocker will stop it.
How long we keep it
- Analytics events — retained in a rolling window and pruned automatically.
- Estimate requests and quote checks — retained as aggregate demand and accuracy data. They contain no contact details.
- Contributed project costs — retained indefinitely as part of the pricing dataset, because their value is historical. They contain no contact details.
- Interest registrations — retained until you ask us to delete them, or until we decide not to launch matching in your area.
Your rights
You can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted. Because contributed project costs are stored without any identifier linking them to you, we may need you to tell us the ZIP code, amount and month in order to find a specific submission.
Depending on where you live you may have additional statutory rights, including under the California Consumer Privacy Act. A contact address and a response process must be added here before launch.
Children
This site is intended for homeowners and is not directed at children.
Changes
When this policy changes we will update the date at the top. Material changes to what we collect or how we use it will also change the consent version, and we will not apply new uses retroactively to data collected under older wording.
See also the terms of use and our data sources page.