Cookie & Tracking Policy

1. Current status

The static pre-launch build does not deploy profiling cookies, non-essential analytics, advertising pixels or social tracking and does not use local storage for profiling or consent. Accordingly the current build does not require a consent banner; the live hosting/CDN environment must still be audited.

2. Strictly necessary technologies

The application code currently sets no first-party cookies. Hosting, CDN or security layers may deploy strictly necessary identifiers, which must be inventoried by name, purpose, duration and provider.

3. Future analytics and marketing

Before analytics, ad pixels, remarketing, heatmaps, A/B testing or tracking embeds are activated, UESE will inventory technologies, define roles/transfers, update this policy and implement compliant consent management.

4. Consent rules

Non-essential trackers must not fire before a valid choice. Consent must be freely given, specific, informed, unambiguous and demonstrable; accept/reject must be fair; withdrawal must be easy; scrolling alone is not consent.

5. Children

Behavioural advertising based on child profiling is not planned. Paid campaigns should primarily target adults and comply with child-protection rules.

6. Browser controls

Users can remove or block cookies/site data through browser settings. Blocking genuinely necessary technology may affect future functions.

7. Live-domain audit

Before final launch, run a cookie/tracker audit across all languages, forms, media, fonts, CDN and third-party services and align this policy with the actual deployment.

8. Controller and DPO