Plain-language notice for the inbound inquiry form.
If you submit the inquiry form, the site stores the fields you provide: name, email, company, website, offer interest, budget range, urgency, challenge, consent version, timestamp, and a short hash derived from request forwarding metadata for basic abuse review.
The site also records minimal first-party operational events such as page_view, tool_open, pricing_view, request_form_view, and offer_click with path, optional UTM fields, referrer, timestamp, and a short request hash. These events are used for aggregate funnel debugging, not automated advertising or third-party resale.
The information is used only for manual follow-up about the audit or implementation offer you requested. The system does not send automated marketing email, does not process payment, does not buy newsletters, and does not post to social channels.
Do not submit passwords, API keys, private customer records, regulated data, or confidential material. Share only enough context to evaluate whether a distribution audit or sprint is relevant.
Lead records are stored locally in server files for manual review. Deletion/export requires operator action. This notice is operational, not legal advice.
The lead system is intentionally narrow: it accepts only consent-based inbound requests, uses a honeypot field to reduce spam, limits request size, and avoids automated marketing. Operators should review records, respond manually, delete irrelevant submissions, and avoid copying sensitive material into third-party systems unless the submitter has agreed.