Know how inquiry information is handled.

The secure RFQ may collect company and contact name, business email, product, application, finished size and unit, quantity and unit, processing and packing requirements, destination, optional order notes, language, source page and limited campaign attribution. Submission time, notice version and consent time are recorded. File upload and purchaser telephone fields are not part of the P0 form.

• Use business contact details, not private household details
• Do not send identity documents, bank or card data, health data or other sensitive information
• Optional notes and destination detail should not contain a home address

Information is used to understand the requirement, contact the business buyer, qualify and assign the lead, prepare a quotation or sample discussion, record follow-up in the approved CRM, measure source attribution, prevent abuse and maintain a limited operational audit. It is not collected for unrelated consumer profiling.

Authorized sales, operations and privacy personnel may use the website RFQ for the stated purposes. Website hosting, database, notification relay and Feishu CRM providers are expected to support the workflow, but their final roles, regions and contractual terms still require pre-launch verification. Inquiry information is not sold. Direct email and messaging channels are also subject to their providers' own privacy and retention rules.

The responsible business contact is in China, but the actual storage and processing locations for Sites/Cloudflare, the relay, Feishu, email and messaging depend on service configuration and contracts that are not yet confirmed. This notice therefore does not claim that every overseas inquiry is necessarily transferred to or processed only in China. Applicable roles, locations, notices, consents and transfer terms must be reviewed before the form is enabled.

The website D1 record, pending notification data and corresponding Feishu CRM copy must share this deadline; production deletion or anonymization schedules must be configured and tested before launch. Direct email and WhatsApp/telephone use the same 365-day governance target, but provider copies, mailbox/message-account cleanup, retention and handoff procedures are not yet verified and must not be described as automatically enforced. A verified formal order moves to the applicable contract, finance and records policy.

The application enforces size limits, rate limits, one-time submission identifiers and restricted access. It stores HMAC-derived anti-abuse and duplicate-detection values instead of the raw network address in the RFQ database. Referrer query strings and fragments are removed before storage. Infrastructure providers may maintain separate limited security logs under their own terms. No system can promise absolute security.

Subject to applicable law and identity verification, you may ask about inquiry information, request correction or deletion, withdraw consent, object or restrict certain processing, or raise a complaint. jiangguowei666888@gmail.com is the proposed temporary routing address for a “Privacy request”; its legal suitability, access controls, retention and handoff process must be verified before production launch. Withdrawing consent does not invalidate processing already lawfully completed.

This content site does not intentionally use advertising cookies in the current build. Technically necessary hosting or access controls may still operate. If analytics, advertising tools, new data uses or new recipients are introduced, this notice and its version will be updated before the form accepts the new version. This B2B site is not directed to children.