Browser storage used by the enquiry flow.

Technology and purpose

When an enquiry submission starts, the site writes one opaque identifier under “orsenatas.sid” to your browser’s sessionStorage. The value is first-party, contains none of the name, email or business details entered in the form, and identifies the server-side enquiry session.

The identifier allows the requested submission and a safe retry to refer to the same server-side session. Together with a separate submission identifier, it supports submission integrity and prevents accidental duplicate records. Limited landing-page, referrer and permitted campaign context is recorded server-side at that point and is explained in the privacy notice; the commercial site does not use this identifier for page-view tracking.

Lifetime and control

The code does not set a persistent expiry for this value. sessionStorage is scoped to the browser tab or window session and is normally cleared when that tab or window session closes. Browser restore features can affect the exact timing, and you can clear site data using your browser controls.

Why no consent banner is shown

In the current implementation, this storage is created only when you request the enquiry-submission service and is used to provide, secure and retry that request. It is treated as strictly necessary for that requested workflow, so it does not require a consent banner.

The banner is not omitted to hide optional tracking: the commercial pages do not currently set advertising cookies, load third-party analytics or pixels, perform cross-site tracking, or write optional analytics identifiers before an enquiry submission.

If the technology changes

We will update this notice and introduce any required choice controls before enabling non-essential browser storage, advertising technology or third-party analytics. The privacy notice explains the related server-side enquiry records.

Read the privacy notice