Legal
Privacy Policy
Effective 2 October 2026
This policy describes what the DineGlobe platform collects and why, in the terms the system actually implements. Where a fact is not yet established, it is marked in brackets rather than invented.
Who is responsible
[Legal entity name — to be completed], operating the DineGlobe reservation platform at dineglobe.com [registered address — to be completed], is the controller for the data described here. Venues using DineGlobe decide their own booking terms and guest policies, and act as controllers for the guest data they collect through their venue pages.
What the platform collects
Operator and staff accounts: name, sign-in email, password hash, role assignments, session and authentication records, and two-factor secrets where enabled. Guest bookings: the name and contact details a guest enters, party size, booking and service times, and any notes a venue records against a visit — notes are encrypted at rest with AES-256-GCM, purpose-limited, and excluded from routine exports. Security telemetry: audit events record which fields changed, never their contents.
What the platform does not do
No advertising, no analytics trackers, no profiling, no sale or sharing of data, and no automatic cross-venue profile sharing or identity merging — a guest known to two venues stays two separate guest records unless a human merges them on purpose. There is no marketing email anywhere in the product.
Security
Encryption protects data in transit (TLS) and sensitive data at rest (AES-256-GCM for guest notes; Argon2id hashing for passwords; hashed one-time codes, recovery codes and check-in secrets — the system stores hashes, so a leaked database yields no usable credentials or passes). Tenant isolation is decided server-side from verified membership; cross-tenant access fails closed and is indistinguishable from not-found.
Retention and controls
Booking history is retained per venue policy and legal obligation; deleted guest data is handled through documented export and erasure workflows rather than ad-hoc deletes. Guests may request a copy of their data or its erasure through the venue they booked with — venues can locate any booking by its DG confirmation code. Operators can export their venue's data at any time from the console.
Where data lives
The platform runs on a single dedicated server. Third parties involved in running the service are listed on the Subprocessors page, and a provider appears there before it starts processing anything. DNS resolution is the only third-party touch during the pilot.
Contact
Privacy questions and requests go through the contact page. Related reading: Subprocessors and the compliance posture.