Concepts
How Buxmate Works
Organiser accounts, guest invite links, privacy, and the typical event workflow.
Two roles
| Role | Account? | Access |
|---|---|---|
| Organiser | Yes — email/password at app.buxmate.com | Full dashboard for your events |
| Guest | No | Private invite link only → guest hub |
Guests never create a Buxmate login. They get a session cookie after joining via their invite link.
Privacy model
- Each event is private — only people with an invite link can join
- Guest emails and phone numbers are visible to the organiser only
- The Who's coming list on the guest hub shows names and RSVP status, not contact details
- Event photos require an organiser or guest session to view (links cannot be opened in a browser without access)
- Buxmate does not process card payments — money moves directly between guest and organiser
Event structure
Event
├── Activities (itinerary + per-activity RSVP)
├── Guests (invite list + status)
├── Payments (activity costs + shared costs → per-guest splits)
├── Updates (announcements on guest hub)
└── Photos (shared gallery)Organiser workflow
Sign up → Create event → Add activities → Add guests
→ Set costs → Add payment details → Send invites
→ Track RSVPs → Record payments → Post updates
→ Archive when finishedGuest workflow
Receive invite link → Join (confirm details) → Guest hub
→ RSVP per activity → See what you owe → Pay organiser offline
→ Read updates → Upload photosNavigation (organiser)
Global: Dashboard · Events · Settings
Per event: Overview · Activities · Guests · Payments · Updates · Settings
On mobile, the bottom bar shows the first five — use Edit event on Overview for Settings.
What Buxmate does not do (yet)
- No Stripe or in-app card payments
- No automated organiser notification emails for every RSVP (you send reminders manually)
- No public event pages or searchable guest lists
See Payments explained for how cost splitting works.