What we collect
The MVP stores account email, mission titles and briefs, role configuration, run history, credit ledger entries, provider vault ciphertext, beta access state, and product analytics events needed to operate the workroom.
Privacy
MVP privacy notice.
Last updated May 22, 2026. This draft explains how the prototype handles account data, AI runs, provider keys, payments, and analytics.
Provider keys
Session-only provider keys stay in the browser session. Vault keys are encrypted in the browser before encrypted ciphertext is saved to Supabase. The vault passphrase is not stored.
AI providers
When live mode is enabled, mission prompts may be sent to the selected AI providers. Users should avoid submitting sensitive personal, medical, legal, or regulated data during the MVP.
Payments
Stripe checkout handles payment details. The app stores credit fulfilment records such as checkout session identifiers and purchased credit amounts.
Analytics
Local-first product events help measure mission creation, run completion, checkout flow, BYOK adoption, and failure patterns. Signed-in events may sync to Supabase.
Feedback
Beta feedback can include category, severity, trust rating, message, optional contact email, and source page. Feedback is stored locally first and may sync to Supabase for signed-in users.
Beta access
Closed beta invite codes are verified server-side. The app may store a signed access cookie so invited testers do not need to re-enter a code on every visit.
Deletion
During MVP testing, users can request account and workspace deletion through the operator. A self-serve deletion flow should be added before broader public launch.