Information we collect
Dine Out Booking collects information needed to operate a hospitality dining coordination platform. Depending on how you use the service, this may include:
- Contact details submitted through hotel or restaurant application forms, such as name, email, phone, business name, address, website, and application notes.
- Account information for Platform Admin, hotel staff, and restaurant staff users, including name, email address, role, organization, invitation status, password reset status, and login/session records.
- Hotel, restaurant, setup, invoice, and billing contact details entered by staff or administrators.
- Guest booking information entered by hotels, including guest name, guest email, stay dates, party size, included dinners, private booking-link status, reservation choices, and reservation notes.
- Operational records such as reservation statuses, invoice records, Outbox email records, delivery metadata, audit-log activity, and security or error information.
How we use information
We use this information to provide and protect the service, including to:
- Review partner applications and onboarding setup.
- Create and manage staff accounts, invitations, password resets, and authenticated sessions.
- Create private guest dining links, process reservation requests, notify guests and partners, and show current booking status.
- Generate and issue invoices for served dinners.
- Send operational emails that are necessary for the platform workflow.
- Maintain audit history, investigate support issues, prevent misuse, and keep the service reliable.
How information is shared
Information is shared only where needed for the service workflow. For example, reservation details may be visible to the relevant hotel, restaurant, and Platform Admin users. Guest contact details are used for operational booking emails. Invoice details are visible to the relevant hotel, restaurant, and Platform Admin users.
We may also use service providers for hosting, database storage, email delivery, logging, and other operational infrastructure. We do not describe the current service as selling personal information.
Security and access
The application uses authenticated staff access, role-based screens, CSRF protection for protected actions, private guest booking links, password reset tokens, and operational audit logs. No public page should be used to share passwords or sensitive authentication tokens.
Retention
Operational records are kept as long as needed to run the platform, support partners and guests, maintain billing and audit history, and meet legitimate business or legal needs.
Your choices and contact
If you need to correct information, ask a question, or request review of information associated with you or your organization, contact Dine Out Booking at bookings@dineoutbooking.com.