Privacy

What is collected, what happens to it, and the things this site deliberately does not record.

Published by the Land Clearing Authority editorial team · Last revised 2026-07-29 · Editorial policy · Corrections

The planning tools collect nothing

All five tools run entirely in your browser. Your answers are not transmitted, not stored, and not visible to anyone but you. Closing the tab discards them. The same is true of site search: the index is compiled into the page and scored locally, so no query text leaves your device.

What the project submission form collects

Only what a contractor needs in order to understand and respond to your project: the answers to the five gates, a five-digit ZIP code, an optional approximate location, your name, email, phone, preferred contact method, and any notes you add.

What happens to a submission

• It is validated again on the server — the browser’s validation is never trusted — and routed to a contractor category using the published rules.
• It is stored in a database provisioned for this platform, with row-level security enabled and no public read access.
• No contractor is engaged in any territory yet, so it is recorded and reviewed by Land Clearing Authority rather than passed to anyone. Where a territory has an independent contractor engaged, a matching project is passed to them and they may pay for the introduction. Until then nobody is standing by to call you, and this page will not pretend otherwise.
• An internal notification is sent to this platform’s own inbox once the submission has been stored. It contains what is needed to act on your inquiry, including your name, email, and phone. It goes nowhere else.
• Consent is logged with the version of the text you agreed to, so what you consented to is recoverable rather than asserted.

It is not published, not sold, and not shared outside the matching contractor category.

Where you arrived from

If you reached this site from a search result or an advertisement, the campaign parameters on that link and the address of the page that sent you are held in your browser for the tab you are using, and are attached to a submission if you choose to send one. No cookie is set, and nothing is transmitted anywhere unless you submit the form. Close the tab without submitting and it is discarded.

Duplicate detection and abuse control

A salted, one-way hash of your contact details and project is stored so the same submission is not delivered twice. A second salted hash, of the network address and browser your request arrived from, is stored so a single source cannot flood the form. Neither hash can be reversed to recover what produced it, and the address itself is never stored.

Analytics

Provider currently configured: ga4. With no provider configured, no third-party analytics script is loaded at all — the loader renders nothing.

When a provider is configured, event payloads are filtered against an allow-list before dispatch. Anything outside it is dropped at the call site rather than relied on not to be sent.

Geography is reported at three-digit ZIP prefix only — enough to know a project was in a region, not enough to know where.

Cookies

This site sets no cookies of its own. If an analytics provider is configured, that provider may set its own; which ones depends on the provider, and the choice is disclosed above.

If you are a contractor who applied

A contractor application is a separate record from a homeowner submission, with its own consent wording and its own version stamp. It is not stored in the same place, it is not governed by the same consent, and it is never mixed into the homeowner pipeline.

• What is collected. Your business name and contact details, where you operate and how far you travel, the services and equipment categories you report, the project sizes and site conditions you will and will not take on, and your operating answers — insurance status in categorical form, response window, capacity.
• Why. To assess whether your services and service area fit a territory that might be opened. That is the only purpose it is used for.
• What it is not. Submitting is not acceptance, does not create a partnership, and does not assign a territory. Nothing you send is published, listed, or shown to homeowners — there is no contractor directory on this site.
• Documents. The form takes no attachments of any kind. Insurance, licensing, and identity documents are requested directly if a review goes further, and are never held in this platform’s source control.
• Analytics. Nothing identifying you reaches analytics. What is recorded is categorical: whether an application started, how many capability groups were selected, a bucketed band for coverage interest, whether residential or commercial work is accepted, and whether the submission succeeded or failed.

Two things are worth stating plainly rather than glossed. There is no published retention schedule for applications yet, and no automated deletion workflow — asking is a conversation, not a button, and pretending otherwise would be describing a system that does not exist. And no timeframe is promised for reviewing an application, because coverage is opened when a territory is ready rather than in the order applications arrive.

To ask what has been stored about your business, to correct it, or to have it removed, contact the editorial team.

Your details

To ask what has been stored about you, to correct it, or to have it removed, contact the editorial team. Note that once a submission has been passed to a contractor, that contractor holds their own copy under their own privacy practices, and this platform cannot delete it on your behalf.