Privacy.
Last updated:
We collect what we need to run private-event booking: proposals, contracts, payments, BEOs, and the day of. We disclose e-signature audit capture (IP, timestamps, device) and optional event-photo capture up front. We don't sell your data. You can request deletion — see Account deletion.
What we collect
Operators and captains: identity (name, email), venue and event records (spaces, menus, packages, staffing plans), device + push tokens, and event photos captains choose to capture (setup proof, close-out documentation). Event clients: contact details (name, email, phone), event details (date, headcount, selections, dietary notes), proposal and contract records, and payment records. E-signature audit: when a client signs a contract or accepts a proposal through the portal, we record the signer's name, email, IP address, device user-agent, and timestamps as an immutable audit trail attached to the legal record.
Why we collect it
To run the booking lifecycle — inquiry, proposal, contract, deposit, BEO, event night, invoice — to verify identity before signature or payment (a one-time code by email), to make signed agreements legally durable (the audit trail), and to compute per-event costs for the operator.
E-signature + verification disclosure
Before a client signs or pays through the portal, we email a one-time verification code to the address on the event. Signing captures the typed name, IP address, device user-agent, and timestamp into an append-only audit record. These records exist to protect both parties and are retained with the contract.
Photo disclosure
If a captain captures event photos in the app (room set proof, close-out documentation), the photos attach to that event's record in the operator's account. Photo capture is always a deliberate action — never automatic or in the background.
Cost + margin data
Estimated costs and contribution margin are operator-only. They are never shown on any client-facing surface — not in proposals, not in the portal, not in email.
Retention
Operational data is retained while the account is active. Signed contracts, their audit trails, payment ledgers, and published BEO snapshots are retained per legal and tax obligations even after deletion requests (see Account deletion for the exact deleted-vs-retained split).
Who we share it with
| Processor | Purpose |
|---|---|
| Supabase | Hosting and database |
| Stripe | Operator subscription billing and client event payments |
| Anthropic | AI proposal/BEO drafting (event + catalog content only; drafts are always human-reviewed) |
| Expo / APNs / FCM | Push notifications |
We don't sell personal data.
Your rights
Access, correction, and deletion requests — see Account deletion. Event clients may request through the venue that holds their event or directly from the email on their event record; operators and captains request from their account email.
Children
SavorBanquet is a business tool and is not directed to children.
Changes to this policy
Version-stamped; material changes are notified in the app and by email.
Contact: privacy@heardmgmt.com · Also useful: terms · support · account deletion