Account, sync & data stewardship
Supabase-backed auth, what is stored, deletion/export expectations, and AI logging.
Signed-in Kanban AI relies on Supabase for authentication and data storage. This article summarizes what that means for ownership, retention, and what you should back up.
Authentication
- Sign-in flows are standard email/OAuth patterns provided by Supabase (exact providers depend on configuration).
- Sessions use secure cookies or tokens as implemented in the frontend—follow your org policy for password managers and 2FA on the identity provider if applicable.
Data stored
- Projects, tasks, and related records needed for the board.
- Profile fields required for billing, analytics segmentation, or account management (deployment-specific).
Deletion and export
- Account deletion and data export depend on hosted policies—check the live privacy policy and support channels for the production deployment.
- For self-hosted instances, your operations team controls retention in Postgres.
AI and logging
- Chat may go to server-side model APIs; content handling should be covered in your DPA / privacy docs.
- Analytics events may be aggregated for product improvement (see Analytics page for owner-visible summaries on supported deployments).