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
Privacy notice for VoltBridge Global inquiry data.
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.
Before sending
Share useful inquiry context, not unnecessary sensitive data.
- Use the contact route for product, company, application, range, and document needs
- Avoid passwords, payment credentials, personal IDs, and confidential designs
- Wait for an approved path before sending regulated or highly confidential material
Current form
Email draft fallback until backend approval
Data purpose
Product route, technical, document, and quotation review
Sensitive data
Do not send credentials, payment, or personal ID details
Future systems
Backend, analytics, and CRM changes require approval
Trust boundary
Clear privacy expectations make supplier inquiry review more trustworthy.
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 future backend approval gate.
Email draft instead of live database
The public form prepares a buyer email draft to [email protected]. It should not be treated as a live database, CRM, or automated ticketing workflow before backend approval.
Only send what review needs
Name, company, email, buyer role, product route, application, range, documents, destination, quantity, timeline, and questions are enough for a first supplier review.
Keep sensitive data out of first contact
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 review map before sending inquiry data.
| 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. It does not confirm backend storage, CRM handling, analytics processing, transaction terms, or jurisdiction-specific obligations before approval.
Data handling path
How privacy fits the current supplier inquiry workflow.
Email fallback is deliberate
Until backend implementation is approved, the form opens an email draft. The contact page remains the public route for buyer questions.
Backend changes stay gated
A future RFQ submission contract exists, but endpoint, storage, anti-spam, analytics, and CRM behavior require approval before use.
Inquiry content should stay relevant
Buyers should send enough context for product-route and document review, using the inquiry checklist or sample inquiries first when needed.
Legal scope is not overclaimed
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
Privacy questions before sending an electrical test equipment inquiry.
What information can buyers send to VoltBridge?
Buyers can send name, company, email, role, product route, application, electrical range, document needs, destination, quantity, timeline, and inquiry questions for review preparation.
Does the current public form submit to a live backend?
No. The current public form opens an email draft to [email protected] until an approved backend, storage, and notification path are configured.
How is inquiry data used?
Inquiry details are used to review product route, technical context, commercial questions, document needs, export context, and follow-up requirements before any external commitment.
Should buyers send sensitive personal or payment data?
No. Buyers should avoid passwords, payment credentials, personal identity numbers, and confidential design data unless an approved review path is agreed first.
Can inquiry data be used for quotation review?
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.
Will future backend or CRM handling change this notice?
Any future backend endpoint, analytics, CRM write, or external service connection requires approval and should be reflected in the public notice before use.
Does this notice confirm legal compliance in every country?
No. This is an operational privacy notice for inquiry handling; buyer and seller obligations can depend on jurisdiction, contract path, and approved processing workflow.
Where can buyers ask a privacy question?
Buyers can use the contact page or email [email protected] with privacy, data, or inquiry-handling questions before sending detailed requirements.
Privacy question
Ask before sending sensitive or unusual inquiry data.
Use the contact page if you need a safer path for confidential documents, regulated data, or internal project details before supplier review starts.