Security
Powerful work needs clear control.
Jiddu separates account credentials, project data, and risky actions so the operator can work without silently crossing important boundaries.
Credentials
Passwords are handled by Supabase Auth and are never stored in ordinary Jiddu project records.
Approvals
Destructive changes, publishing, payments, credentials, and system actions require explicit approval.
Sessions
Jiddu uses signed, HTTP-only session cookies and verifies the account before protected work begins.
Project data
Project storage is accessed from Jiddu's server and is not exposed through the public browser key.