Privacy Policy for LinkScope Sourcing 05

This policy explains how LinkScope Sourcing 05 handles information submitted through the procurement form. The site is a sourcing desk. It is not a store account system and it does not ask you to create a password.

What you submit

The form asks for a name, work email, optional phone, company, and a requirement field. With JavaScript enabled you may also type a product interest, a target budget, a currency, a per-module or whole-order basis, and a supplier preference. Those extras are appended to the requirement text at submit time. They are not separate stored columns in a catalog.

Why it is used

The desk uses the text to see whether a factory packet is complete, to contact you about gaps, and to forward the technical rows to factories you ask the desk to approach. The work email is the reply path. The phone number, if you leave one, is optional and is not a published switchboard.

What is not collected on purpose

Do not send payment card numbers, government identity numbers, or passwords. The comparison does not need them. Do not send personal information about people who are not part of the buying team. A wavelength plan for a business network is the intended content.

How long the brief is kept

The desk keeps the correspondence long enough to finish the comparison you requested and to answer a follow-up about that same packet. It does not turn your company name into a public case study. If you want a brief deleted after the inquiry closes, say so in a reply to the same email thread.

Who else may see it

Factories that receive the packet see the technical rows needed to quote. They do not need your internal cost center notes if you leave those out. Service providers who host the form see the submission as part of operating the site. The desk does not sell the list of inquirers.

Public pages

Articles and static pages do not contain your form contents. A browser stores a local timestamp and a session flag so the sourcing-support notice can expire. That flag is not your specification.

Questions about a submitted brief should go back through the RFQ form or the email thread that answered it, so the module details stay with the request.