A little clarity.

Your email

The guestbook stores your email, your consent and the story or channel that brought you here. It is separate from your sign-in account. We use it for the stories and release updates you ask for.

Your sign-in account

When you choose Google or Apple sign-in, Supabase stores the identity information supplied by that provider, such as your account identifier, email address and, when available, name and profile image. We use this to authenticate you, manage your trial allowance and check membership access. Apple may provide a private relay email address. We do not request access to your mail, files or contacts. Your provider profile is not sent to our AI provider or included in analytics. Signing in does not subscribe you to marketing emails.

Your account information is retained while your account is active. You can request deletion below. Signing out ends this browser session; it does not delete your account.

Your reflections

Your messages and recent conversation context are sent through OpenRouter to the configured AI provider. We request providers that do not collect prompts for training. We do not store your reflection text or include it in analytics. Conversation text stays in memory in this tab until you clear it or leave. A draft may be kept in this tab’s session storage for up to 30 minutes to restore it after sign-in. We store account-level usage counters to enforce the three-reply trial and member limits.

Optional analytics

With your permission, we measure page visits, story reading, guestbook interactions installation signals, conversation starts, sign-in prompts and collection interest. We use a random session identifier, not your email, for first-party events. We do not record your screen, keystrokes or reflection content. Browser limitations mean installation signals are incomplete.

Change your mind

Request to leave the guestbook or delete your data. Requests are reviewed by the ODD WITHIN team; submitting this form does not grant access to any account.

Essential security

Member sign-in uses session cookies. We use a keyed hash of the network address to limit abusive requests; the app does not store the raw address in its database. Hosting and authentication providers may keep their own security logs.