Information we handle
The configured deployment may store your account email, profile, workspace membership, support tickets, messages, uploaded knowledge, AI drafts, audit events, and contact inquiries in Supabase. Usage counters help protect generation endpoints.
How information is used
Information supports authentication, workspace access, knowledge retrieval, drafting, human review, and inquiry handling. Uploaded knowledge may be processed to provide AI features. Relevant knowledge excerpts and ticket content may be sent to the configured AI provider, Anthropic, for generation. Provider terms and retention depend on your deployment and provider agreement.
Keep sensitive information out
Do not upload API keys, passwords, authentication tokens, or other secrets. Minimize personal customer data to what is necessary for support. Application logs are designed to record operational metadata rather than full ticket or knowledge content.
Demo and browser data
The public demo uses fictional sample data and deterministic responses. It does not send demo conversations to Claude. Demo changes are held in the current browser tab’s application state and reset on reload. The app installs no third-party analytics by default. Supabase authentication uses session cookies.
Access, deletion, and retention
Workspace access is protected by server authorization and database row-level policies. You can request deletion of your account and workspace data through the contact form. Retention and deletion requests are handled by the deployment operator; the MVP does not offer a self-service deletion tool or a guaranteed deletion timetable.
Updates
This policy may change as the product evolves. Material changes should be communicated by the operator of the deployment.