DineGlobe

Subprocessors

Who else touches the service

The list is short because the service is deliberately small. Items in brackets are facts not yet recorded by the operator — we mark them rather than guess.

Current subprocessors

  • Hosting infrastructure

    The server DineGlobe runs on

    A single dedicated server operated for DineGlobe [hosting provider details to be completed]. Application databases, uploaded media and the documentation site all live on this machine — venue data is not spread across clouds.

  • Cloudflare

    Domain name service (DNS)

    DNS resolution for dineglobe.com. Cloudflare sees DNS queries only — it does not proxy application traffic or process guest data [DNS-only configuration].

Providers that will join this list

Payment, SMS and email providers are built into the product but none is connected — during the pilot, email delivery dead-letters visibly rather than routing through anyone, and no payment or SMS provider exists at all. When one activates, it appears on this page first, with its role and the countries it serves, before the first message or charge flows.

Guest-facing bookings run on DineGlobe itself; there is no analytics, advertising or tracking processor anywhere in the product. Questions about this list go to contact.