Current position
No advertising-cookie banner is shown because the current public landing pages do not set advertising, cross-site tracking, or browser-side analytics cookies. A consent banner should ask for a real choice, not appear merely as decoration.
The term “cookie” below also covers comparable browser storage, such as local storage, session storage, and IndexedDB. Storage that is strictly necessary to provide a sign-in, security, or checkout feature requested by the user does not serve advertising.
Current storage inventory
| Feature | Provider and storage | Purpose | Duration |
|---|---|---|---|
| Public landing and enquiry pages | Pagewrite | No advertising or browser-analytics cookie is set by the landing measurement described below. | No browser identifier is created for that measurement. |
| Account sign-in | Google Firebase Authentication may use IndexedDB, local storage, or similar first-party browser storage. A Google sign-in flow may also use Google-domain cookies after you choose to start it. | Keep the requested user signed in, return the authentication result, refresh an authenticated session, and protect account access. | Session or persistent, depending on the authentication flow and sign-out. Provider security cookies follow the provider’s stated duration. |
| Hosted checkout | Stripe Checkout may use cookies and comparable storage on Stripe’s hosted pages. | Operate checkout, prevent fraud, remember checkout state, and process payment securely. | Session or the period specified by Stripe for its necessary security and fraud-prevention storage. |
| Local developer override | Pagewrite session storage may store a local API endpoint override in a developer test environment. | Connect a locally served page to a chosen development API. It is not used to profile visitors. | Until that browser tab or session ends. |
Cookie and storage names can change when Firebase, Google, or Stripe updates its service. The purpose and provider are the more stable identifiers. The privacy notice explains the associated personal-data processing.
Cookie-less landing measurement
Some public Pagewrite pages send same-origin events such as landing_view and form_started. The event record is limited to the page route, offer, allowlisted short campaign tags, the referring site’s origin, landing version, and time. It does not include a cookie, IP-derived visitor profile, account ID, session ID, form answers, or workflow description.
These aggregate records expire after 90 days. When an enquiry is accepted, the server records an authoritative submission event without putting the enquiry content into the aggregate event.
Third-party services
Opening a link to another site places you under that site’s storage choices. In particular:
- Google’s sign-in pages are governed by Google’s privacy and cookie information;
- Stripe Checkout is governed by Stripe’s privacy and cookie information; and
- an external authority, official form source, or documentation link can use its own cookies.
The optional PostHog integration used by some deployments is server-side. It does not by itself install a PostHog script or cookie in your browser. Its data use, if enabled, is disclosed in the privacy notice.
Your choices
You can sign out to end the current authenticated use and use browser controls to delete site data. Blocking or clearing necessary authentication storage may sign you out or prevent an account feature from working. Blocking Stripe’s necessary checkout storage may prevent payment.
Because the current site does not deploy non-essential browser tracking, there is no separate advertising-cookie preference to withdraw. Marketing notification choices are separate from cookies and can be changed on the unsubscribe page. You can object to the personal-data processing described in the privacy notice by contacting contact@ml-boost.com.
If this changes
If Pagewrite later adds non-essential browser analytics, advertising pixels, session replay, or another non-essential identifier, it will update this inventory and, where required, ask for consent before that technology loads. Rejecting non-essential storage will be as easy as accepting it.