Cookies and similar technologies
Cookies are small browser records associated with a website or provider. Local storage is a separate browser mechanism that can remember a preference across page visits. Their purposes and lifetimes depend on the implementation and provider.
Preferences and website delivery
The website uses a local-storage record named elevatex.analytics-consent to remember an analytics grant or denial, its policy version and expiry. The current implementation expires that record after 180 days. It does not contain inquiry details.
If preference storage is blocked or cleared, a previous choice may be unavailable and optional analytics default off. Cloudflare delivers and protects the site; whether it sets a security cookie depends on the enabled hosting features. No account, shopping basket or payment session is implemented here.
The contact form uses Cloudflare Turnstile for a security check before sending. Its verification token is used for submission protection rather than optional analytics. These necessary security checks do not require accepting Google Analytics or Clarity.
Optional Google Analytics storage
After valid analytics consent, Google Analytics may use cookies to distinguish browsers and understand page use. Google documents names such as _ga and _ga_<container-id>. Cookie expiry may depend on the property and tag configuration; it is different from retention of analytics reports.
The website does not load Google Analytics before an analytics grant. Advertising storage and personalization remain denied. Our selected interaction events exclude form content and personal contact details.
After permission, Enhanced Measurement can also collect interaction events such as scrolls, outbound clicks, downloads and form interactions, depending on the stream settings. These events are usage measurements, not proof of a delivered inquiry or completed sale.
Optional Microsoft Clarity storage
After valid analytics consent, Clarity may use first-party cookies such as _clck to associate a browser with its Clarity preferences and _clsk to connect page views within a session. Microsoft also documents third-party cookies; their use depends on consent, provider behavior and browser controls.
The integration grants analytics storage only, keeps advertising storage denied and marks inquiry/editable regions for masking. Cookie denial alone is not relied on to prevent transmission: the Clarity script is blocked before a grant.
Manage or withdraw permission
Use Cookie Preferences in the footer to accept or reject optional analytics, or to change a previous choice. Neither option is preselected as permission. Website content remains available when you reject.
Withdrawal disables optional event collection, updates provider consent, attempts known first-party cookie cleanup and reloads the document after saving denial. It cannot recall data already received by providers or delete cookies owned by unrelated domains. Browser settings can also remove or block storage.
Do Not Track and Global Privacy Control keep these integrations off. Without JavaScript, neither optional provider loads; the policy text remains readable. If optional analytics are operationally disabled, the preferences area states that instead of suggesting collection is active.
Further questions
The Privacy Policy explains the wider information-handling context. For a privacy question, contact ElevateX Lab in Pakistan on WhatsApp.