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.
It is passed to independent contractors in the matching category and territory, who contact you directly.
An internal notification is sent that deliberately excludes your contact details — it carries only the reference, the routing outcome, and the ZIP.
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.

Duplicate detection

A salted, one-way hash of your contact details and project is stored so the same submission is not delivered twice. The hash cannot be reversed to recover what produced it.

Analytics

Provider currently configured: none. 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.

Permitted in an event payload

tool
step
category
secondary_category
result_status
market
state
zip3
acreage_band
source_path
cta
dataset
asset
query_length
result_count
complete

Dropped, always

name
first_name
last_name
email
phone
address
zip
postal_code
notes
message
photos

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.

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.