Last updated: July 12, 2026
Bookler uses a small number of providers to run the service. This page lists who they are, what they do, and where they process data. It forms part of our Data Processing Agreement.
When a restaurant uses Bookler, the restaurant is the controller of its guest and reservation data and Bookler acts as processor. The providers in the first table process that data on our instructions and are our sub-processors under Article 28 of the GDPR. The second table covers providers that support this website, where Bookler is itself the controller.
These providers process account, reservation, and guest data on behalf of restaurants using Bookler. Each is bound by a data processing agreement and may use the data only to deliver its service to us.
| Provider | Purpose | Location | Transfer safeguard |
|---|---|---|---|
| Vercel Inc. | Hosting and content delivery for the website and application | United States, with EU hosting region | EU–US Data Privacy Framework and Standard Contractual Clauses |
| Supabase Inc. | Database, authentication, and file storage for account, reservation, and guest data | EU hosting region, United States parent company | Standard Contractual Clauses |
| Stripe Payments Europe, Ltd. | Subscription billing and payment processing | Ireland (EU) | Processed inside the EU |
| Postmark (ActiveCampaign, LLC) | Delivery of transactional and reservation email | United States | EU–US Data Privacy Framework and Standard Contractual Clauses |
| OpenAI Ireland Ltd. | Classifying reservation messages and drafting reservation actions | Ireland (EU) and United States | Standard Contractual Clauses |
| Google Ireland Ltd. (Gemini) | Classifying reservation messages and drafting reservation actions | Ireland (EU) and United States | Standard Contractual Clauses |
These providers support bookler.online itself, for visitors rather than restaurant guest data. Analytics and support chat load only after you accept them in the cookie banner.
| Provider | Purpose | Location | Transfer safeguard |
|---|---|---|---|
| Vercel Inc. | Hosting and content delivery for the website and application | United States, with EU hosting region | EU–US Data Privacy Framework and Standard Contractual Clauses |
| Google Ireland Ltd. (Analytics) | Website analytics, loaded only after you accept it | Ireland (EU) and United States | Standard Contractual Clauses |
| Tawk.to Inc. | Website support chat, loaded only after you accept it | United States | Standard Contractual Clauses |
| Google Ireland Ltd. (Fonts) | Delivery of website fonts | Ireland (EU) and United States | Standard Contractual Clauses |
Reservation messages may be sent to OpenAI or Google to be classified and to draft reservation actions inside the rules a restaurant configures. Both providers process this data only to return a result to Bookler and do not use it to train their models. Restaurants that prefer not to use AI features can ask us to switch them off for their account.
Stripe handles subscription payments through hosted checkout, so full card numbers never reach Bookler. For fraud prevention and legal obligations such as anti-money-laundering checks, Stripe acts as an independent controller rather than as our sub-processor.
We update this page before a new sub-processor starts processing restaurant or guest data, and we aim to give at least 30 days notice. A restaurant that objects to a new sub-processor can contact us at app@bookler.online before the change takes effect.
For questions about this page, email Bookler at app@bookler.online.
Practical context
These pages are here so restaurants, guests, applicants, and partners can find the right policy and contact route without searching through the product or guessing which team to email.
Use this information when you need to understand Bookler’s legal, privacy, cookie, deletion, or company-contact position before using the website or service, signing up, or sharing operational details.
Send enough context for us to find the relevant account, restaurant, booking, or website interaction. For most requests, app@bookler.online is the right starting point and keeps the conversation traceable.
Policies may change as the product, providers, or legal requirements change. The date near the top of the page shows the latest published update, so teams can check whether guidance changed.