Privacy overview

Introduction

What the current website does.

Opus Mods is a public informational website for modular building systems, representative models and application planning. Enquiry delivery and optional analytics are separate, environment-controlled services; analytics remains subject to the visitor’s explicit choice.

Enquiry information

The project and partner forms ask for business contact details, organisation information and project or capability information needed for preliminary review. They do not request identity documents, payment details or file uploads. Final online delivery remains disabled until the owner configures and verifies a secure destination.

Purpose and delivery

When activated, submitted information is validated on the server and delivered to an owner-approved HTTPS webhook. The destination and access secret are server-only configuration. A submission starts human review; it does not produce an automated quotation, availability decision or partnership approval.

Accounts and storage

Submitting an enquiry does not create an account. The current workflow does not add a public lead database, browser-stored form archive or customer portal. Temporary edge controls may retain hashed abuse-prevention and duplicate-request keys for a short operational window; raw IP addresses and full submissions are not written to those controls.

Necessary website operation

Core pages remain available without analytics. The site may store a versioned privacy preference on the visitor’s device so the selected analytics choice can be respected on later visits.

Optional analytics

Analytics is disabled by default. If the owner configures an approved provider, its script can load only after the visitor explicitly accepts analytics. Declining analytics does not restrict access or enquiry delivery, and form acknowledgements do not include analytics consent.

Google Analytics

Google Analytics 4 may be enabled later with an owner-provided measurement ID. When configured, it is intended to receive page paths, safe campaign fields and defined interaction events only after analytics consent. Names, contact details, company names, free text and enquiry references are excluded.

Microsoft Clarity

Microsoft Clarity may be enabled later with an owner-provided project ID. When configured, it is loaded only after analytics consent. Provider-side masking and retention settings require separate owner review before production activation.

Consent choices

Visitors can accept or decline analytics from the initial notice and can reopen Privacy preferences from the footer. Necessary operation remains active. Revoking a previous acceptance updates the stored choice and stops future site analytics initialization.

Local and session storage

The device-local consent record contains only a schema version and an accepted or rejected analytics state. After consent, supported UTM campaign fields may be kept in session storage for the current browser session; unsupported query parameters are ignored. Full form submissions are not stored in browser storage.

Third-party services

No analytics provider is contacted when its identifier is absent, malformed, the site is outside production, or analytics consent has not been granted. When configured, Turnstile is contacted only for form spam verification and the delivery webhook receives the validated enquiry.

Retention and owner review

Specific enquiry and provider retention periods, legal-controller details and a verified privacy contact method have not yet been approved for publication. They require owner and appropriate legal review before delivery is activated.

Contact details

Verified privacy and general contact details are pending owner confirmation. No temporary email address, telephone number, postal address or legal entity detail is presented as an official contact channel.

Policy updates

This operational overview will be updated when enquiry delivery is activated, verified contact ownership changes or analytics provider settings materially change.