Trust center / Privacy policy

Privacy policy for inquiry handling

Kanwer Polytex collects only the information needed to review, route, and retain a dyed-yarn inquiry within the website's operational workflow.

Privacy policy

What the site collects from a buyer brief, where the inquiry record goes, and how that data supports commercial review.

Security practices

How the lead-intake route validates payloads, filters abuse, and tracks delivery state for inbound inquiries.

Terms of use

How the published catalog should be used, what the website does not make contractual, and what use is prohibited.

Captured fields

Identity and requirement context

Name, company, email, optional phone, product qualifiers, and the buyer's commercial brief are collected through the form.

Workflow purpose

Qualification, routing, and recordkeeping

Submitted data supports commercial review, duplicate suppression, internal notification, and request traceability.

Operational processors

MongoDB, Resend, and Google reCAPTCHA

The live pipeline stores lead records, sends internal notifications, and verifies anti-abuse signals through named service providers.

Inquiry data received from the form

The website receives the information a buyer chooses to provide so the submitted brief can be understood without guesswork and tied to the right commercial context.

Identity details such as name, company, email address, and optional phone number.
Requirement fields such as product category, product sub-category, product type, reference denier or count, shade reference, estimated quantity, target timeline, and destination or routing context.
The free-text program brief that explains the commercial need in the buyer's own words.
Operational anti-abuse signals associated with the submission, including hidden-field checks, verification outcomes, request identifiers, and hashed network metadata used for review.

How inquiry data is used

Submitted data is used only to run the website inquiry workflow and support direct follow-up on the dyed-yarn brief.

Validate the request and confirm that the payload matches the accepted website form contract.
Route the inquiry to the internal commercial handling path with enough context for the first review.
Suppress repeated or abusive submissions using duplicate-detection and anti-abuse controls.
Maintain request-level traceability for operational follow-up and website governance.

Processing path and service providers

The current lead-intake implementation validates form data at the API route, stores the resulting lead record in MongoDB, and attempts internal notification delivery through Resend. Bot-verification checks rely on Google reCAPTCHA in the production intake path.

MongoDB stores the structured lead record together with operational fields such as request ID, notification status, and hashed IP metadata.
Resend is used for internal email delivery so the submitted brief reaches the notification inbox tied to the website workflow.
Google reCAPTCHA is used to verify browser-issued anti-bot tokens before a submission is accepted in production.

Retention, updates, and questions

Inquiry records are retained according to operational review and website-governance needs. If a buyer has a question about a submitted request, the official inquiry route should be used so the request can be reviewed against the correct request context.

Use the official inquiry email for policy or request-specific follow-up.
Reference the request ID from the submission response whenever available.
This policy can be updated as the website workflow or operating controls change.

Questions about a submitted brief?

Use the official inquiry route and include the request ID when available so the privacy question can be reviewed against the right inquiry record.

Open contact route

Trust center pages

Privacy policy

What the site collects from a buyer brief, where the inquiry record goes, and how that data supports commercial review.

Security practices

How the lead-intake route validates payloads, filters abuse, and tracks delivery state for inbound inquiries.

Terms of use

How the published catalog should be used, what the website does not make contractual, and what use is prohibited.

Operational facts

Official inquiry emailenquiry@kanwerpolytex.com

Official inquiry phone+91 7021872923

Operating company

TextileFairy Consultancy Pvt. Ltd.

Unit references

Bhiwandi Shelar Unit

Production-facing Shelar unit for routing, visit planning, and operational reference.

Get directions

Bhiwandi Katai Unit

Katai unit reference for routing, visit planning, and local coordination.

Get directions

Inquiry data received from the form

The website receives the information a buyer chooses to provide so the submitted brief can be understood without guesswork and tied to the right commercial context.

Identity details such as name, company, email address, and optional phone number.

Requirement fields such as product category, product sub-category, product type, reference denier or count, shade reference, estimated quantity, target timeline, and destination or routing context.

The free-text program brief that explains the commercial need in the buyer's own words.

Operational anti-abuse signals associated with the submission, including hidden-field checks, verification outcomes, request identifiers, and hashed network metadata used for review.

How inquiry data is used

Submitted data is used only to run the website inquiry workflow and support direct follow-up on the dyed-yarn brief.

Validate the request and confirm that the payload matches the accepted website form contract.

Route the inquiry to the internal commercial handling path with enough context for the first review.

Suppress repeated or abusive submissions using duplicate-detection and anti-abuse controls.

Maintain request-level traceability for operational follow-up and website governance.

Processing path and service providers

MongoDB stores the structured lead record together with operational fields such as request ID, notification status, and hashed IP metadata.

Resend is used for internal email delivery so the submitted brief reaches the notification inbox tied to the website workflow.

Google reCAPTCHA is used to verify browser-issued anti-bot tokens before a submission is accepted in production.

Retention, updates, and questions

Use the official inquiry email for policy or request-specific follow-up.

Reference the request ID from the submission response whenever available.

This policy can be updated as the website workflow or operating controls change.

Operational facts

Official inquiry emailenquiry@kanwerpolytex.com

Official inquiry phone+91 7021872923

Operating company

TextileFairy Consultancy Pvt. Ltd.

Unit references

Bhiwandi Shelar Unit

Production-facing Shelar unit for routing, visit planning, and operational reference.

Get directions

Bhiwandi Katai Unit

Katai unit reference for routing, visit planning, and local coordination.

Get directions