Cookies and browser storage

Language is determined by the URL; a language cookie is not needed. Server forms use an HttpOnly, SameSite=Lax session cookie named elite_form_session to bind signed form tokens to the same browser session. It contains no form entries. An accepted receipt ID is saved in sessionStorage to prevent duplicate measurement; names, emails and messages are not stored there.

Once measurement accounts and approvals are complete, preferences may be remembered in localStorage under elite_measurement_consent_v1 for up to 180 days. External analytics and advertising tags remain disabled locally. The live cookie/provider inventory requires separate verification.

WordPress administrator session and preference records differ from normal visitor use. A scan performed while signed in as an administrator is not, by itself, a visitor cookie inventory.

Test signed-out visitors, administrators and any relevant preference states separately in production.

A Microsoft Clarity ID exists in the configuration; the local environment measurement protection prevents the tag from loading. That does not establish identical behaviour in production.

No claim that “only necessary cookies are used” is made before production analytics, advertising and other third-party tools are defined. Providers, data flows and any required preference management must be reviewed before launch.

• Exact cookie or storage name and provider.
• Purpose, category, duration and first/third-party status.
• The action or preference that causes it to be created.
• Recipients, countries and any transfer assessment.
• How relevant preferences can be changed or withdrawn.

You can review or remove records through your browser’s site data settings. Those controls do not replace any separate preference mechanism required on the website.

Update the inventory and this page when a measurement tool or feature changes. This draft does not claim consent has been collected or legal review completed.