Template — not legal advice
This page is template text provided with the software. It has not been reviewed by a lawyer and contains placeholders in [brackets]. The platform operator must have it reviewed and completed by qualified counsel before relying on it.
Terms of Service
Template — last edited [date]
These terms govern use of the [Platform name] restaurant software (the "Platform"), operated by [Operator legal name] ("we"). Restaurants ("Restaurants") use the Platform to run their websites, online ordering, reservations and operations. Guests ("you") use it to order from or book with a Restaurant.
1. Who you are dealing with
When you place an order or make a reservation, your contract for food, drinks and services is with the Restaurant, not with us. The Restaurant sets its menu, prices, taxes, fees, refund policy and allergen information.
We provide the software the Restaurant uses. We are not a restaurant, delivery company or payment processor.
2. Orders, prices and payments
Prices are calculated by the Platform from the Restaurant's current menu when you check out. Estimated ready and delivery times are estimates, not guarantees.
Card payments are processed by Stripe on behalf of the Restaurant. We never see or store your full card number. An order is confirmed only after the payment provider confirms payment (or the Restaurant accepts pay-later).
3. Allergens and dietary information
Allergen and dietary information is entered and maintained by each Restaurant. It is not a guarantee. If you have a severe allergy, contact the Restaurant directly before ordering.
4. Accounts
You are responsible for keeping your password secret. You can export your data or delete your account from your account page at any time. Restaurants may keep order and payment records they are required to keep.
5. Acceptable use
Do not misuse the Platform: no fraudulent orders, no attempts to access other people's data, no automated scraping or attacks, and no unlawful content in reviews or messages.
6. Liability
[To be completed by counsel: disclaimers, limitation of liability, indemnity, consumer-law carve-outs for your jurisdiction.]
7. Changes and governing law
We may update these terms; we will post the new version here with its date. [Governing law and venue to be completed by counsel.]
8. Contact
[Operator legal name], [postal address], [support email].
Service providers (subprocessors)
Each provider is used only when the operator or restaurant has configured it. Rows marked in yellow are placeholders the operator must complete.
| Provider | Purpose | Data | When used |
|---|---|---|---|
| Stripe | Card payments, payouts to restaurants, in-person terminals | Payment card details (entered directly with Stripe; never stored by us), name, email, amounts | When a restaurant has connected Stripe |
| Resend | Transactional and (opt-in) marketing email | Email address, name, message content | When email delivery is configured |
| Twilio | SMS order updates, reservation and waitlist messages | Phone number, message content | When SMS delivery is configured |
| Expo (650 Industries) | Push notifications to the mobile app | Device push token, notification content | When push notifications are enabled |
| [Hosting provider] | Application servers, database, file storage and backups | All data held by the platform | Always — the operator must name the provider and region here |
| [Maps / geocoding provider] | Turning delivery addresses into map coordinates | Delivery address | Only if a geocoder (e.g. Mapbox or Google) is configured |