Booth privacy
Useful signal, without turning attendees into profiles.
Booth is built around a simple rule: the intelligence is in what was asked, not who asked it. Organizers get the question stream from their own event. Booth does not pool attendee data across customers.
What Booth keeps
The transcript record of calls, so organizers can understand what attendees asked, when they asked it, and where confusion formed. Booth’s retained event record is the transcript, not call audio.
What Booth does not do
Booth does not turn callers into attendee profiles. It does not pool one organizer’s event data with another’s. It does not benchmark events against other customers. Your event’s questions are yours.
One organizer, one data boundary
The question stream belongs to the organizer running that event.
Booth is designed around per-organizer data isolation. If data is deleted, it is deleted from that organizer’s store. Booth is not emergency, medical, or security dispatch — if a caller raises something it should not handle, the product escalates honestly or directs them to the event’s defined human process.
Transcripts, not recordings
The product is designed around transcript retention rather than stored recordings.
No cross-org pooling
One database per organizer. No benchmarking your event against other customers.
EU/UK data posture & retention
Data is handled with EU/UK posture in mind, with retention scoped to the organizer’s event record.
Emergency, medical & security boundaries
Booth is not dispatch. Out-of-scope calls are escalated or directed to the event’s defined human process.