Scope and contact
This policy applies to the spiraxsteam website, its member accounts, enquiries and shopping services. “We” means this website’s operator. Our published contact address is [email protected]. It covers the language sites at spiraxsteam.com, spiraxsteam.cn, spiraxsteam.ru and spiraxsteam.ae. External websites have their own policies.
Business contacts, projects and transactions
We respect the privacy of customers, prospective customers, suppliers and other business contacts. Mechanical-product enquiries may include contact name, company, department or role, business email, telephone and message. Project use, equipment model, quantity, specifications or operating requirements that you provide through agreed channels help us understand the request. Technical information is not necessarily personal data, but any identifiable contact details within it remain covered. Account records, access logs, orders and delivery records depend on the functions actually used; public browsing does not require registration.
We process the information needed for the features you choose to use: account identifiers, email, display name and a password hash if you set a local password; enquiry name, company, email, telephone and message; and, when you place an order, products, recipient, delivery address, contact details, payment status and shipment records. Requests can also generate IP address, browser/device information, visited page, time and security logs. Do not include sensitive personal information in free-text enquiries.
Product enquiries, selection and quotations
Information you send through the enquiry form, email or another agreed channel is used to respond, clarify models and specifications, discuss selection requirements, prepare quotations and follow up the purchase you initiated. We may request additional information directly relevant to that need. Relevant product, project or support personnel can handle the request. An enquiry does not automatically subscribe you to marketing. Requesting information, receiving a quotation and confirming an order are distinct business steps.
Purchasing, invoicing, delivery and after-sales data
When a purchase occurs, we process relevant product specifications and quantities, order references, contact and delivery details, payment status, tracking and communications. Invoice names, tax details or corporate payment information you provide are handled only as needed for that transaction and under applicable requirements. Repair, spare-part, replacement or warranty discussions can involve serial numbers, proof of purchase, fault descriptions and images or inspection records you choose to send. These records support fulfilment, delivery, service and disputes; this disclosure does not mean every application is available online.
Required, optional and third-party information
Public browsing does not require a member account. Registration needs the fields marked as required on the form; a Google-created account uses the verified identity information described above. An enquiry requires a contact name, email and message, while company and telephone are optional in the current form. Delivery details are needed when the selected fulfilment method requires shipping. If essential information is missing, we may be unable to provide that particular function; this does not prevent reading public pages. Information comes from your submissions, the identity provider you select and technical requests made by your browser.
Technical documents, confidential and third-party information
The public enquiry form is not a dedicated confidential-document channel. Agree an appropriate communication method and any necessary confidentiality arrangements before sending sensitive drawings, complete designs, production processes or trade secrets. Browsing the website does not itself create a non-disclosure agreement. Do not send unrelated identity documents, personal financial or health information. If acting for a company, ensure an appropriate basis for providing a colleague’s, recipient’s or site contact’s details and inform them of the relevant business purpose.
Business purposes and optional marketing
A business contact’s details can still be personal information. We use relevant records for requested enquiries, quotations, contracts, delivery, after-sales support, security and applicable legal duties on the grounds permitted by applicable law. Order, shipment or security notifications are distinct from optional product promotion. If we introduce consent-based marketing or another purpose, we provide the required disclosure and choices. Marketing consent is not a condition of responding to an ordinary enquiry, and Google sign-in data is not used for advertising profiles.
Recipients and international processing
Authorised personnel and service providers may process the minimum information needed for hosting, CDN/security, CAPTCHA, enquiry notifications, email, payment and delivery when those functions are used. Submitted enquiries can be forwarded to our configured business messaging service for handling. Payment or delivery providers receive data needed for the transaction, not your Google sign-in tokens. Google receives the technical information necessary for an authorisation request when you select Google sign-in; see Google’s Privacy Policy. If Facebook sign-in is later enabled and selected, we use its app-scoped user identifier and name for the same account purposes; its email is not used to match accounts. External messaging links are governed by their providers’ policies.
Service providers such as Google and Cloudflare can process information in other countries. Applicable transfer requirements and safeguards must be followed; using an international provider does not mean every record is stored in the visitor’s country. We do not sell personal information. Disclosure may also be necessary to meet a lawful request or protect legitimate security interests.
Cloudflare delivery, security checks and Turnstile CAPTCHA process technical connection and verification information. Our configured Feishu/Lark business notification service can receive submitted enquiry details so staff can respond. Email delivery is used only when the relevant email function is available. Payment and logistics providers receive transaction or fulfilment information needed for their roles; check their checkout or delivery notices. We do not add order addresses, enquiry messages or local passwords to a Google sign-in request. Opening an external chat link is your choice and sends a request to that provider.
Retention and security
Member information and provider links are kept while needed to operate your account, until an applicable deletion request or another valid retention requirement applies. Enquiries, orders, security records and backups are retained only as necessary for their purposes, disputes, required accounting or legal duties. Records that must be retained are restricted from unrelated use; backups are removed through their normal retention cycle. Revoking a third-party authorisation alone does not delete information already held by this site. We use HTTPS, password hashing, access controls and encrypted storage for OAuth client secrets. No internet service can promise absolute security.
Account profiles and identity links support ongoing membership; enquiry records support the relevant conversation; order, payment-status and shipment records support fulfilment, disputes and applicable recordkeeping; technical logs support security and troubleshooting. Each category is retained according to its purpose rather than assuming one universal period. OAuth transactions expire after 10 minutes and password-reset credentials after 30 minutes; expired credentials cannot be used, which is separate from the timing of physical database cleanup. An approved deletion request does not erase legally required transaction records or instantly rewrite every backup. Retained records remain restricted, and backups follow their retention cycle.
Cookies and browser storage
Necessary cookies maintain member sessions and protect sign-in; a member session can last up to 30 days and an OAuth transaction up to 10 minutes, unless ended earlier. Browser local storage retains shopping-cart items, language preferences and, where enabled, privacy choices; the latter currently have a maximum validity of 180 days. Cart and language entries remain until changed or cleared. Session storage can retain the return-to-shopping page until the browser session ends. Clearing storage can reset these features. Where a privacy-settings control is available, you can revisit optional choices there; browser controls also let you clear cookies and storage.
The site uses Cloudflare for delivery and security and currently loads its Web Analytics/performance beacon. This is distinct from Google sign-in. According to Cloudflare’s documentation, Web Analytics does not use analytics cookies or local storage to track individuals. Cloudflare security services may use necessary verification cookies. We do not use Google sign-in data for these metrics.
Your choices, requests and deletion
Subject to applicable law, you can request access, correction, a copy, deletion, restriction or objection to processing and withdraw optional consent by emailing [email protected]. For deletion, identify the account email, the site/domain and whether you want Google linkage removed or the shared member account deleted. We verify ownership using proportionate information and explain any legally necessary retention. Do not send your password or authorisation tokens.
You can manage linked identities in account security when signed in. Unbinding requires another usable sign-in method and affects the platform-wide binding. You can revoke Google access in your Google Account’s third-party connections. Revocation, unbinding and account deletion are separate actions. A shared-account deletion can affect access to other sites using that account; it does not require deleting legally retained order records. You may also complain to the competent privacy authority where applicable.
Email [email protected] with the affected account email, site/domain and requested action. We may ask you to confirm control of the account or provide limited supporting information; we do not need your password, Google verification code or sign-in tokens. We review the request, clarify its scope and explain any mandatory retention or reason a request cannot be fulfilled. Response timing follows applicable law; no unsupported fixed deletion deadline is promised. Before requesting shared-account deletion, keep any order information you need. Unbinding Google, revoking Google authorisation, clearing browser storage and deleting a member account each have different effects.
Purposes and shared member accounts
We use information to provide requested accounts, respond to enquiries, process orders and delivery, maintain security and comply with applicable obligations. Where required, we obtain consent for optional processing; other processing is based on the applicable grounds for providing a service, contractual obligations, security or legal compliance. The same linked Google identity uses one member account across this platform’s sites. Site memberships, permissions and orders remain scoped to the relevant site. This is not automatic cross-domain sign-in: each domain has its own browser session. Binding or unbinding a provider affects the shared account. Refusing Google sign-in does not prevent public browsing; other account methods depend on the available sign-in options.
Google sign-in and Google user data
Google sign-in is offered only when enabled. When you choose it, we request openid, email and profile. We receive your Google account identifier (sub), email address, email verification status and name. We store the identifier and account linkage, and use the verified email and name to create a member account when registration is permitted. The current integration does not import or store your Google profile photo. We never receive your Google password and do not request Gmail, contacts, Drive or Calendar access.
We use this information only to authenticate you, create or link your member account, provide account access and verify an already linked identity for password recovery. Google-issued tokens are handled on the server to verify the sign-in response; the current integration does not persist Google access or refresh tokens for subsequent Google API use. We do not sell Google user data or use it for advertising, profiling, credit decisions or training general-purpose AI models. Its use is subject to the Google API Services User Data Policy, including applicable Limited Use requirements.
Choosing Google takes you to Google’s own authorisation page. You choose an account and may approve or cancel. The server validates the returned response before looking up the linked member; when permitted, a new verified identity can register a new member. Matching email addresses alone do not silently merge existing accounts: an existing member must sign in through an available method and explicitly link the identity. An already linked identity can also verify a password-recovery request, without requesting access to your Google mailbox. Cancelling authorisation stops that attempt.
Children and changes
Our industrial product and business services are not directed at children. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action. We publish policy changes here with an updated date and provide additional notice or obtain consent before materially changing the use of Google user data where required. Please also read our Terms of Service.