Almost nothing to protect.

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.

The fastest contact route is the Azure Discord community.

No personal data is collected. The service has no accounts, no sign-in, no contact form, and no analytics. Nothing on the page asks for a name, email address, or any other identifier.

Availability observations: each probe records only a service state, observation timestamps, affected-route and total-route counts, and a latency sample. Observations describe Azure endpoints, never visitors.

On-device cache: the last viewed history is kept in first-party localStorage under the key azure-status-history-v1 so the timeline survives reloads. See the Cookie Policy.

Observations are merged at the edge into shared per-service history stored in the service database (Cloudflare KV) and served read-only through GET /api/status-history. Every visitor sees the same global history.

Scheduled probes run from the service backend (Cloudflare Workers on a one-minute schedule) against the public Azure endpoints listed on the page. The on-device cache never leaves the browser.

Data is never sold, never shared with advertisers, and never used for marketing. No marketing emails exist and no marketing consent is requested.

Shared history is a rolling window: each service keeps the most recent 60 observations, and samples recorded within the same minute are merged into one. Older observations are discarded automatically as new ones arrive.

The on-device cache persists until the browser site data is cleared. Clearing it removes the local copy only; shared history is unaffected.

Because no personal data is stored, there is nothing to view, correct, export, or erase. Removing the on-device cache is self-serve through the browser clear-site-data control. Anything unclear can be raised in the Discord community above.

The history API accepts read-only GET, HEAD, and OPTIONS requests only; every other method is rejected. Cross-origin access is restricted to the status domain, failures resolve to generic state labels, and no stack traces are exposed.

Material changes are noted with a new update date at the top of this page. Continued use of the service after the posted update date constitutes acceptance of the revised policy.