Security & Privacy

Clear controls for your Glow workspace.

This page describes the product controls and technical safeguards currently implemented in Glow. It is written to be specific about what the product does—not to overstate provider or legal guarantees.

HTTPS deliveryHttpOnly session cookiesAccount-scoped authorizationRate-limited APIs

Account and conversation access

Glow uses Manus OAuth for sign-in. The application stores the resulting signed session in an HttpOnly cookie so browser JavaScript cannot read the session token. HTTPS is enforced for the published site.

Server procedures apply account ownership checks before returning or changing account-scoped content such as conversations, memories, and Sentinel settings. Public-facing conversation references use generated UUIDs where they are exposed; internal database relationships remain protected by authorization checks.

Information used to operate Glow

Glow processes the information needed to provide the workspace, including account details supplied by the sign-in provider, messages and replies in your conversations, Sentinel preferences, memories you create, and operational usage records such as message or token counts.

Payments are handled through Stripe when you choose a paid plan. Authentication and platform services are provided through Manus. Those providers operate under their own policies and may process the information needed to provide their respective services.

Your in-product controls

You can delete individual conversations and Sentinel memories from the relevant areas of the signed-in workspace. Glow also provides conversation export functionality so you can retrieve supported conversation data from your account.

Account-wide deletion is handled as a request rather than a self-service button at this time. Do not rely on this page for a particular retention period until the final commercial privacy policy and deletion workflow are published.

Application safeguards

  • HTTP security headers, including transport security and content security restrictions.
  • Rate limits for general API traffic, authentication, AI messages, voice requests, and checkout operations.
  • Input validation and size limits on user-supplied requests.
  • Authorization checks for account-owned resources.
  • Dependency-audit checks in the project release workflow.

Security controls reduce risk; no online service can guarantee that a security incident will never occur.

Privacy and deletion requests

If you want to ask for access, correction, export, or deletion of personal information associated with a Glow account, contact the privacy team with the email address tied to your account. Requests are reviewed under the final applicable privacy policy and law.

privacy@glowlabsplus.com

Security reporting

To report a potential security issue, use the contact information published in security.txt. Please avoid including sensitive personal data in an initial report.

Last updated: October 17, 2026 · glowlabsplus.com