MaterialAxis Procurement Privacy Policy

This policy explains the information requested through the MaterialAxis Procurement sourcing inquiry form. The form collects the contact details you enter, including name, company, work email, phone if supplied and procurement requirements. Optional material, budget and supplier preference controls are combined with the requirement text for submission.

We use the inquiry information to understand the application, clarify specifications and coordinate a sourcing response. Please include business information relevant to the request and avoid unnecessary personal or confidential data. Product details, quantities and destinations may be needed to ask proposed suppliers for suitable options and comparable quotation scope.

When supplier coordination is appropriate, relevant material requirements may need to be shared with proposed providers. The exact transaction and any further confidentiality arrangements should be clarified before sensitive records are exchanged. We do not claim that submitting this form establishes an approved supplier, completed order or confirmed production schedule.

The sourcing-benefit notice uses a browser local-storage timestamp to retain the initial display date and enforce a maximum seven-day display window. A session-storage flag remembers when the ticker is dismissed during a session. Refreshing or opening another session does not restart the original window. These browser entries support notice behavior and are separate from the inquiry text.

You can clear browser storage through your browser settings, although doing so affects stored interface preferences. Optional budget controls describe a buying preference rather than a verified supplier rating. With JavaScript disabled, place budget and preference information directly in the requirement field because helper controls cannot merge that information.

Use the contact form to ask about the information associated with an inquiry, identifying the work email used. Access, correction or removal questions require enough context to locate the record and assess any applicable retention obligations. No fixed retention period or automated deletion schedule is asserted here without a confirmed operational policy. Review any transaction-specific data arrangements before sending sensitive documentation.