Interactive demo · Sample data. Edits save only on this device — no RSVPs, messages, payments, or purchases are ever sent anywhere.

Demo data on this device

Trust

Data & AI Boundaries

AI in EverAfter suggests, explains, and flags. It never acts on its own, and it never sees what the couple hasn't approved.

The assistant's rules

  • · Suggests, never decides. Seating charts, timelines, and drafts are proposals; the couple approves everything.
  • · Never sends. No reminder, thank-you, or message goes out without an explicit human action — and in this demo, nothing goes out at all.
  • · Approved content only. The guest FAQ assistant answers exclusively from questions and answers the couple marked as approved; anything else gets “I'm not sure — ask the coordinator.”
  • · Explains itself. Every seating grouping and timeline choice comes with the reasoning, so the couple can override it confidently.

Data boundaries by role

  • · Guests see the public website and their own RSVP.
  • · The venue sees couple-approved logistics: counts, meals, accessibility, timeline, vendors. Never budgets or private notes.
  • · The DJ and photographer see only their role's packet.
  • · Private seating notes (family dynamics) stay with the couple, full stop.

In this demo those boundaries are design conventions with sample data. In production they will be enforced server-side with authenticated, per-wedding access controls before any real data is accepted.

In this demo specifically

The “AI” responses are scripted mock outputs demonstrating the intended behavior — no live model is called, and nothing you type is sent to any AI provider.