Inquiry handling placeholder
This is a temporary generated placeholder. Approved product, document, support-process, and company evidence photos can replace it after source review.
Inquiry data privacy
Clear privacy expectations make supplier inquiry review more trustworthy. This page explains what buyers may send, how the current email fallback works, and which data-handling changes still require approval.
This notice is operational guidance for inquiry preparation. It does not replace transaction-specific legal, regulatory, or contract review.
Trust boundary
Overseas buyers should understand what happens before they send requirements through the contact page. This notice connects inquiry data handling with the inquiry terms, supplier trust center, buyer FAQ, inquiry checklist, and the approved email-only RFQ handling boundary.
This is a temporary generated placeholder. Approved product, document, support-process, and company evidence photos can replace it after source review.
The public form submits to an approved Cloudflare Pages Function and sends an email notification to [email protected]. It is not a website database, CRM, or automated ticketing workflow.
Name, company, email, buyer role, product route, application, range, documents, destination, quantity, timeline, and questions are enough for a first supplier review.
Payment credentials, passwords, personal identity numbers, and confidential design files should stay out of the first public inquiry unless an approved review path is agreed.
Fast privacy scan
| Privacy topic | What buyers should know | What to prepare | Review boundary |
|---|---|---|---|
| Contact details | Used to reply and route the inquiry. | Name, company, email, buyer role, and destination market. | Do not send personal identity numbers or payment credentials. |
| Technical context | Used to judge which product route should be reviewed. | Application, tested product, electrical range, software/interface needs, and known model reference. | Final model fit and site suitability require review. |
| Document requests | Used to prepare datasheet, manual, calibration, certificate, packing, and warranty questions. | List required documents and audit context. | Document availability and wording require case-by-case review. |
| Commercial context | Used to understand quantity, timeline, destination, and quotation readiness. | Quantity, project stage, target timing, and delivery questions. | Price, delivery, payment, warranty, and available inventory require review. |
| Sensitive material | Should be limited in public first contact. | State that confidential files exist before sending them. | Use an approved path before sending regulated, confidential, or high-risk data. |
This privacy notice improves inquiry preparation. The current approved path is email-only RFQ notification plus Cloudflare Web Analytics; persistent website storage, CRM handling, analytics provider changes, transaction terms, or jurisdiction-specific obligations require separate review.
Data handling path
The approved contact form uses a Cloudflare Pages Function, Turnstile protection, and email notification to [email protected]. The contact page remains the public route for buyer questions.
The approved RFQ submission contract supports email-only notification. Persistent storage, CRM auto-write, analytics provider changes, and additional external services require approval before use.
Cloudflare Web Analytics is used to understand aggregate website visits and page performance. It is not used to store RFQ content, write to CRM, confirm quotations, or decide buyer eligibility.
Buyers should send enough context for product-route and document review, using the inquiry checklist or sample inquiries first when needed.
This page is an operational notice, not a universal legal compliance statement. Final obligations can depend on buyer location, seller workflow, and transaction path.
FAQ
Buyers can send name, company, email, role, product route, application, electrical range, document needs, destination, quantity, timeline, and inquiry questions for review preparation.
Yes. The contact form submits to an approved Cloudflare Pages Function protected by Cloudflare Turnstile, then sends an email notification to [email protected] without using a website database or CRM auto-write.
Inquiry details are used to review product route, technical context, commercial questions, document needs, export context, and follow-up requirements before any external commitment.
No. Buyers should avoid passwords, payment credentials, personal identity numbers, and confidential design data unless an approved review path is agreed first.
Yes. Buyer-supplied application, range, document, quantity, destination, and timeline details help prepare quotation review, but final terms remain case-by-case inquiry review items.
VoltBridge uses Cloudflare Web Analytics for privacy-focused aggregate website measurement. It is used for site performance and traffic understanding, not inquiry storage, quotation decisions, CRM writing, or buyer profiling.
Any future backend behavior, analytics provider, CRM write, persistent storage, or external service connection beyond the approved email-only inquiry path and Cloudflare Web Analytics should be approved and reflected in the public notice before use.
No. This is an operational privacy notice for inquiry handling; buyer and seller obligations can depend on jurisdiction, contract path, and approved processing workflow.
Buyers can use the contact page or email [email protected] with privacy, data, or inquiry-handling questions before sending detailed requirements.
Privacy question
Use the contact page if you need a safer path for confidential documents, regulated data, or internal project details before supplier review starts.