What we use and why
The form may collect your name and business email and, optionally, your company, phone, location, approximate area and technical requirements. Boundary files are uploaded only through the central calculator when you choose to attach them.
We use the data to answer your request, assess feasibility, prepare a quotation and take the steps you request before a possible contract. We do not sell the data or use it for behavioural advertising.
Our internal conversion-funnel measurement sends and aggregates only event type, language, page category, coarse campaign (“tagged”/“untagged”), action placement and coarse channel. First-touch attribution stores only coarse campaign and channel, for the current tab in sessionStorage; raw URLs, query parameters and referrers are neither sent nor stored in the analytics payload or state. The “no PII or identifiers” limitation applies strictly to that payload and aggregate state, not to form data, email or standard technical hosting logs.
After a valid analytics POST and its request-triggered cleanup, exactly the current UTC date and the preceding 119 UTC dates are retained; older files may persist until the next valid POST.
For form abuse protection, the rate-limit state uses a pseudonymous per-IP hash as the file key and stores only request timestamps; active records are limited to the 24-hour window. Inactive files older than 48 hours become eligible for cleanup and are deleted automatically during a later request (“lazy cleanup”). The state is used solely for security and rate limiting; the raw IP address is not written to it, and standard technical hosting logs remain separate.