Security practices
Security practices for the contact form
We check enquiries for missing or invalid information, reduce spam and repeated submissions, and keep a request ID so our team can follow up on an accepted requirement.
Checking your enquiry
The contact form checks the information received before accepting an enquiry. These checks help us receive usable requirements and reject invalid submissions.
- Empty, unreadable or oversized submissions are rejected.
- Required contact and product details are checked, including fields that depend on the selected yarn.
- Checks also run when the submission reaches our server.
- A hidden field helps identify automated spam.
Reducing spam and repeated submissions
We use several checks to reduce automated abuse and repeated enquiries while keeping the form available to buyers.
- Google reCAPTCHA helps check for automated submissions in the production enquiry service.
- Limits on repeated attempts help reduce spam bursts.
- Email addresses and a derived identifier for the requirement help identify exact repeats.
- Brief duplicate checks reduce accidental repeat submissions and allow another attempt if an enquiry could not be saved.
Keeping track of an accepted enquiry
We keep the information needed to find your requirement, check whether our team was notified and review possible abuse.
- Each accepted enquiry has a request ID. Include it when following up about a submission.
- Stored IP addresses are converted to hashes, rather than kept as raw addresses, for abuse review.
- A consistent form of the email address and a derived requirement identifier support duplicate detection.
- The record shows whether the internal notification succeeded or failed.
Reporting a concern
Report a security concern or unexpected form behaviour through our official email or contact page. A request ID helps us locate the relevant enquiry and review what happened.
- Use the contact page or official email for security-related questions tied to a live request.
- Include the request ID when referencing a specific submission.
- We update these practices as the website and its safeguards change.
Your next production run
Need help with a submission?
Email our team or use the contact page. Include your request ID, if available, and describe what happened so we can review the issue.