Account access
Cloud save uses authenticated accounts so saved projects belong to the logged-in user.
Security
Built to protect shoot and client records.
The Clipboard uses account-based access, cloud database row-level security, and paid-access checks to keep each photographer's saved projects separate.
Cloud rules
Database row-level security is used so users can only access their own clipboard projects.
Paid gate
Founder access is designed to unlock only for approved paid emails once the production gate is switched on.
Current Security Checklist
Supabase project storage is separated from the older AI Hybrid Studio project.
Planner project table uses user-based row-level security.
OpenAI and server keys are kept out of public client code.
Paid access table exists in the codebase and is ready for production activation.
Public sales page no longer sends unpaid visitors straight into the app.
Before Public Sales
The final launch security step is to activate the paid-access switch in production after the founder access table has test buyer records. Until that switch is on, the raw app URL should be treated as a preview link.