How the RFQ Workflow Handles Inquiry Information
The checked-in default remains local-only. Production submission is enabled only after the prepared live Turnstile and email configuration is deployed on the authorized domain and its delivery and privacy process are accepted end to end.
Current local-development behavior
The quote page submits to a same-origin Worker endpoint. The server bounds and validates the request, checks the Turnstile response and then attempts email delivery only when the delivery mode is valid. The checked-in configuration uses local-only hostnames and Wrangler's simulated email binding, so a complete local test can reach the confirmation page without sending the inquiry outside the development computer.
Information requested
The form asks for buyer and company context, country or region, email or WhatsApp, product direction, quantity, destination, requirement summary and an acknowledgement of this notice. Selection-help requests may add application, airflow, pressure, electrical, dimensional, material and operating-medium details. Do not enter confidential or export-controlled information beyond what is necessary for a quotation.
Processing and storage boundary
- The server verifies required fields and Turnstile before an email delivery attempt.
- The application does not add an inquiry database, file upload or attachment storage.
- Operational logs contain request status and a reference ID, not full contact details or message text.
- A successful screen is shown only after the configured email service accepts the message.
- Email retention and access follow the destination mailbox policy; that policy and its access owner must be approved before public launch.
Requirements before public submission
- Approve the business identity responsible for the inquiry and an accessible privacy contact.
- Deploy the prepared production configuration and connect the authorized domain to the intended Worker.
- Use the prepared production Turnstile widget sitekey and Worker secret only in their approved build and runtime locations.
- Activate the approved sender and verified Gmail destination through the restricted email binding.
- Run a real-delivery test and approve this notice, retention wording and rights-request process.
Contact and rights requests
No public privacy contact has been approved for this build. A working contact route and response owner must be published before the inquiry form is activated. Until then, this page records an implementation boundary rather than a complete production privacy notice.