Trust
Demo Status
This entire site is an interactive product demo. This page states plainly what is real, what is simulated, and what cannot happen here.
Everything is sample data
Emma & Noah, their 142 guests, every vendor, every dollar figure, and every phone number are fictional fixtures. No real couple's information appears anywhere in this demo.
Your edits stay in your browser
RSVPs, setup changes, intake answers, approvals, and registry previews are saved to your device's local storage only. They survive a refresh, and the Reset demo action in the demo banner restores the original fixtures. Nothing you enter is uploaded, synced, or visible to anyone else.
What cannot happen in this demo
- ✕ No RSVP is delivered to any couple or server
- ✕ No email, text, or reminder is ever sent
- ✕ No payment, purchase, or money movement is possible — there are no payment rails
- ✕ No gift is bought and no retailer is contacted
- ✕ No account is created and no personal data is collected
What the production product would add
Real accounts, authenticated couple-scoped storage, actual RSVP delivery, and (much later, after compliance review) couple-owned payment rails. None of that exists yet, and this demo does not pretend it does.
Known limitation in this release
The couple dashboard now includes an editable guest and household workspace, but the public RSVP lookup still uses the fixed sample households. Those two demo sources are not synchronized yet. The next product milestone is a hosted, authenticated wedding record that gives guest management and RSVP one shared source of truth.
What changed in this release
- ✓ Editable guest, household, budget, and timeline workspaces
- ✓ Venue review, packet versions, change history, and finalization
- ✓ Role-limited venue, DJ, and photographer handoffs
- ✓ Three distinct wedding themes, calendar files, maps, and travel utilities
- ✓ A dormant backend and tenant-isolation scaffold that is not connected to this demo