How we handle project inquiry information
Effective September 1, 2026. This notice applies to business information submitted through sucotondusa.com, email, phone or WhatsApp.
Information we collect
We may collect your name, company, work contact details, product category, target volume, project requirements and the contents of messages you send us.
How we use it
- Evaluate manufacturing feasibility and prepare quotes or specifications.
- Coordinate with our factory and service providers when needed for your inquiry.
- Respond to questions, manage a potential or active business relationship, and maintain business records.
- Protect our website, communications and business from misuse or fraud.
Sharing and retention
We share information only as reasonably needed to operate our inquiry channels, evaluate a project, provide requested services, comply with law or protect legal rights. Project information may be shared with our factory's overseas production team. We retain inquiry records for as long as reasonably needed for these purposes.
Source and conversion measurement
We use privacy-limited first-party measurement to understand whether a visit reached us through broad channels such as organic search and whether a visitor used a contact link, downloaded a public buyer resource, successfully used a browser-only buyer tool, started the project form, made a valid submission attempt, encountered a broad delivery error or completed it. The event payload we send contains random session-scoped and event identifiers, page and landing paths, broad first-touch channel, attribution confidence, an external referrer hostname when available, contact method, a controlled public-resource or tool identifier, a controlled buyer-interest code on successful forms, a broad `provider rejected` or `network or invalid response` category on failed delivery attempts and site release version. A tool-use event does not contain supplier names, prices, quantities, rates, timelines, calculator inputs or calculated results. A form-attempt or error event does not contain field values, validation details or the provider's response message. We do not put workbook or dataset contents, names, contact details, message contents, full referrer URLs or search terms into that payload. Our hosting provider, Netlify, may automatically attach the visitor's IP address, browser user-agent and referring page as server-side submission metadata for platform operation, security and abuse prevention. The random session identifier is stored only in your browser's session storage, is not a cookie and is not designed to follow you across browser sessions. We do not send these events when a browser signals Global Privacy Control or Do Not Track.
Our inquiry form uses Web3Forms for delivery. Each Web3Forms submission includes an opaque receipt ID plus technical website-channel and release labels. After that provider confirms a successful submission, our hosting provider records a separate privacy-limited receipt carrying the same opaque ID together with landing and submission paths, broad first-touch channel, attribution confidence, campaign labels when supplied and an allowlisted buyer-interest code when the form was reached through a supported project route. The separate receipt does not duplicate your name, email, phone, company or message. The shared opaque ID lets authorized staff reconcile a provider-delivered website message with its anonymous success receipt without copying contact details or message contents into the receipt record. We use this reconciliation to measure marketing sources and diagnose form-delivery gaps.
When your browser does not signal Global Privacy Control or Do Not Track, an email link addressed to our public inquiry mailbox may add a non-personal website marker, the current public page path and a random email reference to the draft subject. You can edit or remove that draft subject before sending. If the email is sent with the reference intact, authorized staff can match it to the privacy-limited email contact-click record without copying your identity or message into the analytics record. The marker does not add other pages visited, search terms or form contents.
When your browser does not signal Global Privacy Control or Do Not Track, a WhatsApp inquiry link may add an editable website marker, the current public page path and a random WhatsApp reference to the draft message while preserving the project prompt already shown in the link. You can edit or remove the draft before sending. If the message is sent with the reference intact, authorized staff can manually match it to the privacy-limited WhatsApp contact-click record without copying your identity or message into the analytics record. Our WhatsApp inbox content is not connected to website analytics, so a recorded click is not treated as a delivered or qualified inquiry.
Confidential information
Do not submit proprietary formulas or other trade secrets through the public form. Contact us to arrange an NDA before sharing confidential technical details.
Your choices
You may ask us to correct or delete inquiry information, subject to legal and business-record requirements. Email info@sucotondusa.com with the subject “Privacy Request.”
Contact
Sucotond USA
7624 17th Ave
Brooklyn, NY 11214
info@sucotondusa.com