Back to Azure home
LegalCookie Policy

Zero cookies.

The Azure portal sets no cookies at all. Analytics is cookieless, fonts load with the page build, and interface state never leaves component memory.

Last updated: September 16, 2026

1. Operator

The Azure portal page at azure.cx (“the portal”) is operated by [OPERATOR LEGAL NAME — PLACEHOLDER]. The legal operator name is still to be confirmed; it is shown as a placeholder until then.

Questions about this policy can be raised in the Azure Discord community.

2. Cookies used

None. The portal codebase sets no cookies: the only cookie-writing code in the repository belongs to an unused sidebar component that is never mounted, so no cookie is ever emitted.

Vercel Analytics (the single measurement script) sends aggregate page-view events without cookies or persistent identifiers — verified by inspection of the installed package, which contains no cookie or browser-storage calls.

Fonts (Instrument Sans, JetBrains Mono) are loaded through next/font, which bundles them at build time: no request to a font provider happens at runtime and no third-party cookie can result.

3. First-party browser storage

None. Menu-open and scroll state live in transient component memory and disappear on reload. The portal reads and writes no localStorage, sessionStorage, or cache entries of its own.

With no cookies, no storage, and no optional trackers, there is nothing to consent to — a banner would be consent theatre. Introducing any cookie, storage use, or optional tracker in future requires updating this policy first and adding consent controls before the new mechanism loads. See the Privacy Policy for the full data picture.

5. Control

Nothing needs clearing, because nothing is stored. Blocking the analytics endpoint changes nothing about how the page works; every section remains fully readable with scripts disabled.