Privacy and enquiry information
How Wirewalk handles contact details, optional visit attribution and public lab tools, with controls for same-tab source information.
Contacting Wirewalk
The contact form asks for your name/organization and email so I can reply. Topic, message and discovery source are optional. Please do not send credentials, sensitive research data or regulated material through the public form. We agree an appropriate access and handling arrangement before exchanging that information.
This site’s contact form submits to FormSubmit for delivery to Wirewalk’s email. That provider processes the supplied fields and normal network metadata associated with a request. Form delivery is separate from browser submission; a button changing to “Sending” does not establish delivery. The ordering page has its own purchasing process and terms.
Contact information is used to handle your request and any agreed engagement. This form does not subscribe you to a mailing list or authorize sharing your details with vendors or partners for marketing. Contact sales@wirewalk.com with a privacy question or request about information you submitted.
Optional visit context
The site can retain a small source record in this browser tab for optional attribution during a 30-minute window: the starting public page path, an external referring site’s hostname and supported campaign source/medium/campaign codes. Query strings, referral paths, email addresses and form message contents are not put into that record. No visitor identifier or fingerprint is created.
If “Include this visit’s starting page and campaign source” is checked when you send the contact form, the available source fields accompany the enquiry. Uncheck it to omit those fields. If browser storage is blocked or a Global Privacy Control signal is present, automatic source context is not retained. The record stays in this tab until it is cleared, replaced after expiration or removed when the tab closes. The ordinary form remains usable.
The site does not load a new advertising or analytics tracker as part of this implementation. Browser interaction hooks distinguish a service view, download click, contact click and submission attempt; they do not send an analytics request. Search Console reporting, when connected by the owner, is separate from these browser hooks. A confirmed enquiry, quotation or paid engagement must be verified in the actual business records.
Public lab downloads
The lab tools run locally. They do not upload results or contact Wirewalk. Review source and generated inventory before sharing it; operational information can remain sensitive even when hostnames, addresses and unique device identifiers are omitted. Illustrative fixtures contain invented data and are not customer records.
Return to contact · Read the procurement guide.
Hosted cluster labs and prepaid access
The interactive cluster, Kubernetes/Run:ai and switching labs use a hosted service, separately from the local downloads above. It uses your verified Wirewalk Institute account identifier and email for sign-in and purchases. The browser keeps its lab sign-in token in session storage for the current tab; signing out clears it. Account verification, sign-in and password recovery use the existing Institute account service.
Cloudflare stores the synthetic cluster and fabric state you submit or import, your time balance, recent session activity and purchase references so you can resume across visits. Stripe processes card details and supplies payment/refund status; the lab does not receive your full card number. No lab data is sent to an AI model. Keep passwords, credentials, identifiable inventories and sensitive research data out of lab inputs and exported session files.
Saved lab state is retained for returning users until it is replaced or removal is requested. Contact sales@wirewalk.com to request removal or ask about your account. Payment and usage records may be retained for reconciliation, disputes and required business records even after model-state removal. Lab data is separate from optional enquiry attribution; clearing visit context does not remove your account or payment records.