Cookies
Cookie Policy
This policy explains the limited cookie and browser-storage behaviour used by the launch version of the website.
Launch setup
The launch site stays intentionally lightweight.
The public website avoids embedded booking widgets, advertising tags, and unnecessary third-party scripts. That keeps both page weight and cookie scope low.
Essential website behaviour
The MVP is built as a statically exported marketing site served by a lightweight C++ runtime. It does not include a login area, shopping basket, or user account cookies. Basic site behaviour should work without asking visitors to accept advertising or remarketing tools.
Analytics and measurement
Analytics are disabled at launch, so the public site does not load a live Google Tag Manager container, grant non-essential analytics storage, or set analytics cookies.
Advertising, remarketing, cross-site tracking, heatmap, and session-recording tags are not enabled in the launch configuration. If optional analytics cookies are ever introduced later, they must stay off until a real consent choice is offered and this policy is updated first.
The form-first launch flow may use session-based browser storage to carry UTM attribution from a tagged landing page to a later form submission. That storage is first-party, short-lived, separate from analytics cookies, and does not add an external analytics script by itself.
Third-party links and services
The launch fit-call flow is form-first and does not embed a booking widget. If you later follow an external link away from this website, the destination service may apply its own cookies under its own policy.
How to manage cookies
- Use your browser settings to clear or block cookies.
- Review browser privacy controls for cross-site and storage restrictions.
- Be aware that blocking all cookies may affect external sites after you leave this website.
Future changes
If Google Ads, remarketing, or additional third-party tools are introduced later, this cookie policy and any associated consent model must be updated before those tools are enabled.
Next step
Want to see the form-first fit-call flow?
The fit-call journey is the main interaction path described by this policy and shows the lightweight launch setup in practice.