Your space to think.
Guest and account history
As a guest, history stays in this tab unless you enable Save on this device. Signed-in conversations are saved automatically in the pilot's configured account database: SQLite for local testing, or Supabase when the hosted adapter is enabled. Account access is checked before a conversation can be read or changed. The sign-in page identifies local testing versus invited email sign-in. Do not use sensitive personal data in the pilot.
Delete or start again
Guests can turn saving off to remove the browser copy. Signed-in users can delete individual conversations from My space, or delete their account and associated conversations, sessions, feedback and activity records. New conversation starts a separate conversation and preserves earlier account history. Deletion removes active application records; secure erasure of filesystem backups or SQLite journal remnants is not guaranteed. No automated backups are configured yet.
Where messages go
Demo messages go to this application’s server to select a scripted example; no AI provider is called. In live mode, conversation context and approved retrieved passages are sent to OpenAI. We do not promise zero provider retention. Do not include secrets or sensitive personal information.
Minimal operational data
The account pilot stores email, profile, session records, conversations and request metadata for operation. The owner dashboard displays counts, access settings and feedback you deliberately submit, not private transcripts. An excerpt is shared only when you paste it and consent. Local test sessions expire after seven days and test codes after fifteen minutes; hosted authentication follows the Supabase project's session and code settings. Conversations remain until you delete them or the account. Signed-in request counts persist across restarts. There are no advertising trackers. Hosted retention, email delivery and backups must be configured and disclosed before launch.