Conveyor operations software for industrial teams worldwide
BeltLabs

Legal

Cookie policy

Effective 6 September 2026. BeltLabs currently uses first-party cookies for access, security and interface preferences.

Conveyor infrastructure at an industrial port
Secure sessions support controlled operational access

1. Scope

This Cookie Policy explains how the service operator identified in your BeltLabs order, checkout record or invoice uses cookies and similar browser storage on beltaxis.com and the BeltLabs platform. It forms part of our Privacy Policy. A cookie is a small data value stored by a browser and returned to the relevant service with later requests. Similar technologies may store a limited preference or security state in the browser.

2. Technologies currently used

BeltLabs currently uses first-party technologies required to authenticate users, preserve secure session state, complete Google or Microsoft OAuth flows, operate authorised customer and administrative access, prevent cross-site request abuse, and remember the selected interface theme. These technologies are used to deliver functionality requested by the user and protect the Service. We do not currently deploy third-party advertising cookies or cross-site behavioural tracking on our websites.

3. Authentication and security cookies

Account and customer-portal session cookies identify an authenticated session after successful sign-in. They are configured with protections appropriate to their function, including HTTP-only access for authentication tokens, secure transmission in production and SameSite restrictions. Standard account and customer-portal sessions ordinarily expire within 14 days and may end earlier when the user signs out, the account becomes unavailable or the server invalidates the session.

4. OAuth and verification cookies

Short-lived cookies preserve encrypted or signed state while a user moves between BeltLabs and an identity provider. They help bind the callback to the initiating browser and defend against request forgery and replay. OAuth flow and pending-signup cookies ordinarily expire within approximately 10 minutes and are not used for advertising or unrelated profiling.

5. Preference cookies

A first-party theme cookie remembers whether an authorised user selected a light or dark interface. It ordinarily expires within 30 days and may be replaced when the preference changes. Removing it resets the interface to its default until a new preference is saved.

6. Authorised administrative support

Where a properly authorised support or administrative workflow uses a separate session, a strictly necessary cookie may preserve the scoped support session and its expiry. Such access is controlled by server-side authorisation and audit records. The cookie does not itself grant access beyond the corresponding valid server record and expires when the support session ends or is revoked.

7. Third-party transaction and identity sites

When you choose an external identity provider or open Paddle checkout or buyer support, the third party may set cookies on its own domain under its own policy. BeltLabs does not control those cookies. Review the relevant provider's notices and controls before using that service. Returning data is handled as described in our Privacy Policy.

8. Controls and consequences

You can delete or block cookies through browser settings. Blocking strictly necessary cookies will prevent or materially impair sign-in, security checks, checkout continuity, portal access and saved preferences. Because the technologies we currently set are required for requested functionality or security, disabling them may make the Service unavailable. Browser privacy controls do not erase server-side account or transaction records.

9. Consent and future technologies

Where applicable law permits technologies that are strictly necessary to provide a requested service without consent, we rely on that exception. If we introduce optional analytics, personalisation or advertising technologies, we will update this Policy and provide any notice, consent and refusal controls required before non-essential storage or access occurs. Continuing to browse will not be treated as consent where an affirmative choice is legally required.

10. Changes and contact

We may update this Policy prospectively when technologies, providers or legal requirements change. The effective date identifies the current version. Questions about our use of cookies or a privacy request may be sent to support@beltaxis.com.

See the Privacy Policy for information about purposes, disclosures, retention and individual rights.