What happens to guest information
A guest can explore a live restaurant's configured event options before choosing whether to contact the venue. When the guest requests availability, EventQuote stores the event brief and contact details needed for the selected restaurant to respond. The guest sees that an estimate is not a reservation and that the restaurant controls final availability and pricing.
Saving an estimate and requesting availability are separate actions. A saved estimate does not silently create a restaurant sales lead.
What happens in the public demo
The EventQuote product sample uses a dedicated DEMO configuration with fictional venue data. Quote calculations run, but demo saves and availability requests are nonpersistent. They create no restaurant inquiry, send no operator notification, and record no production analytics event.
How venue access is separated
Restaurant dashboard routes require authenticated access. Organization and venue context travel with protected operations so one venue's requests and configuration are not intentionally exposed through another venue's account. Public guest routes receive only the configuration needed to render the selected venue's planner.
Where Square begins
EventQuote handles the guest estimate, qualification, manager review, and approved handoff. Square handles invoices, deposits, payment collection, and payment records. EventQuote does not collect or store raw card numbers. Square access tokens and other provider credentials are server-side secrets and are not sent to the public browser.
A guest estimate never triggers an automatic charge. The restaurant approves or revises the quote before an approved financial request moves to Square.
How operational email is used
A qualified live inquiry can immediately send an alert to configured venue recipients and appear unread in the dashboard. A timed escalation can notify the team when the inquiry remains NEW. Guest verification and confirmation messages are separate from operator alerts.
Controls designed into the launch
- Signed and replay-protected provider callbacks for sensitive purchase and provisioning events.
- Server-side verification of payment amount, currency, location, status, and related provider references before provisioning.
- An explicit manager-approval gate before a quote can advance toward Square.
- Demo records isolated from production persistence, notifications, and analytics.
- Authenticated venue operations and organization/location context checks.
- Production credentials kept out of public HTML and browser JavaScript.
No online service can promise perfect security. EventQuote does not currently claim a security certification, guaranteed uptime, or a formal compliance attestation.
Questions, access, or deletion requests
The Privacy Policy explains collection, use, retention, sharing, and privacy requests in detail. For a security question or data request, email support@eventquote.app. If the request concerns an inquiry already delivered to a restaurant, contact that restaurant as well because it controls its own copy.