SeatPilotby Sparkm4n DigitalSeatPilot privacy information
This page describes the SeatPilot sales and account-provisioning flow. Restaurant operators must separately provide their own guest-facing privacy information for reservation processing.
Sales, trial and account data
When you request a pilot or buy a plan, we process the contact and restaurant details you provide to create a lead, order, entitlement and hosted SeatPilot workspace.
Payment data
Payment is handled by the configured payment provider. SeatPilot does not intentionally store full payment-card data. Paid access is activated only after authenticated server-side payment confirmation.
Reservation data
The restaurant controls the guest information it collects through SeatPilot. SeatPilot processes reservation data to provide availability, booking management, notifications, source attribution and related service functions.
Security, processors and retention
We use access controls, tenant isolation, signed provisioning and operational logs. Infrastructure and service providers may process data on our behalf. Retention should be limited to what is necessary for the service, legal obligations and documented restaurant instructions.
Contact and rights
For privacy requests concerning the SeatPilot operator, contact the privacy address below. Guest requests relating to a particular restaurant may need to be handled by that restaurant as controller.
Operator
Sparkm4n