Sub-processors
The providers that process data on our behalf to run Dinebase.
Version 1.0 · Last updated 2026-07-27
Draft: the bracketed company details must be filled in before these documents are relied on.
We use the providers below to operate Dinebase. Each is bound by a data processing agreement and may only process data to deliver the service. We give at least 30 days' notice before adding or replacing a sub-processor.
Current sub-processors
| Provider | Purpose | Data processed | Hosting region |
|---|---|---|---|
| Lovable Cloud (application platform) | Application hosting, managed database, file storage, authentication | All account, workspace and reservation data | EU, with edge delivery worldwide |
| Resend | Transactional email delivery | Recipient name and email address, message content, delivery status | EU / US, Standard Contractual Clauses |
| Twilio | SMS delivery, where the restaurant enables SMS | Recipient phone number, message content, delivery status | EU / US, Standard Contractual Clauses |
| Stripe | Subscription billing, and card holds where a restaurant enables them | Billing contact, card details (held by Stripe, never by us), payment and payout status | EU / US, Standard Contractual Clauses |
| Google Maps Platform | Address autocomplete and map display on booking pages | Search text entered by a restaurant user, and technical data when a map loads | US, Standard Contractual Clauses |
| Lovable AI Gateway | Optional assistant features inside the application | Only the text a user submits to the assistant | EU / US, Standard Contractual Clauses |
Guest data is never sold and is not used to train third-party AI models.
Changes
Restaurant customers can object to a new sub-processor on reasonable data protection grounds within the notice period, as set out in section 4 of the Data Processing Agreement. Write to [PRIVACY EMAIL].