CancelLoop isn’t connected to a database yet

The application code is in place, but it needs a dedicated Supabase project, an encryption key and a session signing key before it can store anything. These are owner steps: they cost money and create credentials, so they are never created automatically.

  1. 1.Create a new Supabase project for CancelLoop — never reuse another product’s project. Copy its connection string and keys.
  2. 2.Fill .env.local using the names in .env.example, generating the two keys with openssl rand -base64 32.
  3. 3.Apply the migrations with npm run db:migrate, then set a password on the restricted cancelloop_app role.

The full procedure, including the role password and the rollback path, is in docs/runbooks/database-setup.md.