Keep the static landing site separate from future monitoring data.

Guardus privacy language should stay precise while the managed backend is still a roadmap item.

Current static site boundary

The current landing site is static and does not need runtime product accounts, check execution, billing, or tenant storage to render.

  • No landing analytics are configured in the site definition.
  • No waitlist form backend is connected in this milestone.
  • No monitoring target data is collected by these static pages.

Future Console boundary

A managed Console will need a separate privacy review for account data, configured endpoints, alert contacts, integration credentials, check history, incidents, and billing records.

  • Document what is public status content versus private operator content.
  • Define retention for check history and incident events.
  • Explain how integration credentials are stored before launch.