Privacy / Lead submissions

Clear data boundaries begin before collection.

This page describes the current lead form and server-side storage. It is not a substitute for counsel-reviewed privacy terms.

Current storage boundary
SERVER LOCALLead data saved as JSON
Information collection

What the form stores.

01

Fields collected

Name, work email, company, role, industrial segment, RFQ volume, optional typical RFQ size, optional response time, optional document languages, workflow bottleneck, and consent. A submission ID, UTC receipt time, and site identifier are added by the server.

02

Purpose and storage

We use these details to assess the request and follow up. Submissions are stored in a JSON file local to this site's server and retained long-term unless an administrator removes them.

03

No document upload

The site does not request or accept RFQs, drawings, credentials, customer records, or confidential technical documents.

04

Access and requests

The lead file is administered through SSH-only server access. The application does not record IP addresses and has no self-service access or deletion portal. No contact channel has yet been provided for privacy requests.

Do not submit

Keep sensitive technical material out of the public form.

Do not enter customer names, RFQ text, drawings, credentials, specifications, export-controlled information, or other confidential content. The initial form is intended only for general workflow context.

Administrative safeguards reduce risk but do not guarantee absolute security.

The local file is not public web content, but long-term retention and the absence of a request channel remain important limitations.

Return home