Glow
Sign in

Privacy

This page describes how the Glow prototype/app handles information. It is provided for transparency and is not legal advice.

What Glow is

Glow is an AI support tool for reflection and conversation. It is not a human therapist, not emergency care, and not a medical or diagnostic service.

Account and session data

  • Account information you provide (such as email/display name) is used to sign you in and manage your account.
  • Authentication uses server-issued tokens. The app may also use an HttpOnly auth cookie where supported for session persistence.
  • Conversation/session data handling depends on your consent choices and deployment configuration. In this codebase, message storage is designed to be consent-aware and encrypted at rest when transcript retention is enabled.

Journal and mood entries

If you use journaling or mood check-ins, those entries are stored for your account so you can view them later. Journal content is designed to be encrypted at rest by the backend. You should only write what you are comfortable storing.

AI processing

When an external AI provider is configured, text you submit may be sent to that provider to generate responses. Deployment operators are responsible for selecting providers, reviewing their terms, and configuring data processing appropriately. When using the local development fallback, responses are generated by a rule-based engine in the app process.

Security

  • Use HTTPS in production and set secure cookie/CORS settings for your deployed domains.
  • Secrets (auth keys, master keys, provider tokens) must be stored in environment variables or a secret manager, never in source control.
  • No system can guarantee absolute security. Report suspected issues to the deployment operator.

Your choices

Depending on the deployed features, you may be able to manage consent, review saved entries, and request account/data actions. Availability depends on the specific deployment and applicable laws.

Last updated: 2026-11-09 (prototype documentation). Production deployments should provide operator contact details and jurisdiction-specific notices.

Urgent help: contact local emergency services