Cookie Policy
Zero cookies.
Azure Status sets no cookies at all — no session, no analytics, no advertising, and no cross-site tracking. The only browser storage is a small first-party history cache.
Last updated: September 16, 2026.
1. Operator
Azure Status (“the service”) 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 service codebase contains no cookie reads or writes, and the history API sets no Set-Cookie headers. That is the complete list.
3. First-party browser storage
The last viewed timeline is kept in first-party localStorage under the key azure-status-history-v1 so observations survive reloads. The cache holds the same anonymous state data the page displays and is never transmitted anywhere. Clearing site data removes it and the page simply refetches shared history.
4. Why there is no consent banner
Because the service sets no cookies and runs no optional tracking, no consent banner is required. Introducing any cookie or tracker in future requires updating this policy first and adding consent controls before the tracker loads. See the Privacy Policy for the full data picture.
5. Control
Browsers can clear this site data at any time; the dashboard keeps working with freshly fetched history. Nothing about the page depends on stored state.