Privacy notePublic front, private operator stack

The client front is public. The editorial machinery is not.

This note reflects the Glorioous privacy posture on July 29, 2026. The public site now has a stronger runtime, but the separation between public presentation and internal operation remains intact.

Return to the homepageOpen the brief
Nopublic Strapi admin endpoint exposed.
Nopublic operator API opened on the front.
Yesclear boundary between front and back office.
Current scope

What the public surface does, and what it deliberately does not do.

The front is meant to feel more finished, but still behaves as a disciplined publication surface rather than an open platform.

Public surface

What is now visible

The site exposes a cleaner editorial shell, a page-builder rendering layer and standard metadata endpoints.

  • Homepage and intake pages share one runtime.
  • Preview and revalidation routes exist for future CMS integration.
  • The front remains publication-focused, not account-focused.
Still private

What stays behind the operator path

Internal editorial tooling and administration remain outside the public web surface.

  • No public CMS administration surface.
  • No public planning or production plane.
  • No reader submission or operator endpoint exposed directly.