Security approach
The product architecture includes authentication, role-based journey membership, event audiences, secure household tokens, row-level database policies, storage moderation and audit records. These controls must be deployed, tested and monitored before the service accepts paying couples at scale.
WHY THIS MATTERS
Review Sungano’s intended security controls for authentication, household access, database permissions, storage, audit logs and incident handling.
Production data is intended to use Supabase authentication and PostgreSQL Row Level Security. Couple owners, partners, coordinators, family leads, cultural reviewers and media managers receive different permissions rather than one shared administrative password.
Household invitation tokens should be unique, stored in hashed form, revocable and limited to the events and information assigned to that household. Private journeys carry noindex instructions but must still rely on authentication and authorisation rather than search controls.
Before general availability, the production environment should include tested database migrations, secure secret management, file-upload rules, rate limiting, backups, monitoring, incident response and an independent security review.
HOW SUNGANO HOLDS IT
Every ceremony, household, update and cultural detail has its own audience. Couples remain in control while families receive the clarity they need.
Explore the couple journeyFAMILY JOURNEY READINESS
Three decisions need attentionTHE NEXT CHAPTER
Send enough detail for the product team to investigate without publishing private couple or guest data.
Create your journey