Terms of service

1. Provider and purpose

The Service is provided by Joan Sanfeliu Vilarrasa, tax ID 79279716G, based in Barcelona (Spain), email hola@taula.ai (the "Provider").

The Service is a cloud platform for managing bookings and serving the customers of hospitality businesses, available at app.taula.ai, comprising the booking engine and its public page, the QR digital menu, a website for the business published on a taula.ai subdomain —or, on the Pro plan, on the Customer's own domain— and the AI features described in the Privacy Policy. The WhatsApp messaging agent, which is separate from the WhatsApp reminder in section 2, is not part of any plan until the Provider announces its availability.

2. Sign-up, trial, plans and price

Contracting takes place by signing up at app.taula.ai. The Provider may offer a free trial period, whose length is shown in the account itself; during it no payment method is required and the Customer may stop using the Service at any time at no cost.

After the trial, the Service is provided by subscription on one of these plans:

• Basic: €9.99 + VAT (€12.09) a month, or €99 + VAT (€119.79) a year. Includes the website on a taula.ai subdomain, the QR menu, the full dashboard and up to sixty (60) online bookings a month (section 2 bis).
• Pro: €24.99 + VAT (€30.24) a month, or €249 + VAT (€301.29) a year. Everything in Basic, unlimited online bookings, your own domain (the domain itself is billed separately, at cost) and deposits for large parties.
• Custom: from €69 + VAT (€83.49) a month, at a price agreed in writing for each account. Includes everything in Pro and a website of your own, designed and built to order; the scope, price and terms of that commission are set out in a separate quote.

All prices exclude VAT; VAT is added on the invoice at the applicable rate (currently 21 %). The fee is billed in advance and the subscription renews automatically for periods of the same length, monthly or yearly. There are no setup fees, no per-booking or per-guest commissions and no minimum term. The plan and billing period contracted are shown in the Customer's account.

WhatsApp reminders. When the service becomes available, the Customer will be able to send guests their booking reminder by WhatsApp as well. It is switched off by default and the Customer switches it on under Notices, in the dashboard. The Basic plan includes none; Pro includes up to fifty (50) a month and Custom up to two hundred (200) a month, per account and calendar month. Where a reminder cannot be sent by WhatsApp —because the month's allowance is used up, the guest left no mobile number, that number is not on WhatsApp or the booking has no management link—, it is sent by email, if the guest provided one. The Provider will announce in the dashboard that the service is available; until then, reminders are sent by email and the WhatsApp reminder forms no part of the content or price of any plan.

Clarification (17 September 2026): the preceding paragraph describes how the WhatsApp reminder will work, for which Annex I already provided for Meta as a sub-processor; it adds no obligation or charge for the Customer and does not change the version.

The Provider may change the price on at least thirty (30) days' notice sent to the account's email address. The new price applies from the first renewal after the notice period; if the Customer does not accept it, they may cancel the subscription before it takes effect, with no penalty. Prices agreed in writing for the Custom plan change only by mutual agreement.

2 bis. Online booking limit on the Basic plan

The Basic plan includes up to sixty (60) online bookings per calendar month, counted in mainland Spain time. Bookings count when guests make them themselves on the restaurant's public booking page —including when they reach it from the restaurant's website or from the link on its Google listing— or through an integration connected to the account that receives bookings on the restaurant's behalf. Each booking counts in the month in which it is made, not the month of the visit. Bookings the Customer or its staff add by hand from the dashboard never count, nor do cancelled, rejected or no-show bookings.

When it starts. The limit is counted from November 2026, the first calendar month beginning once thirty (30) days have passed since the notice under section 10 was given to existing accounts. Bookings from earlier months do not count and cannot lead to any change of plan.

How it applies. The count is updated daily and the Customer can see it in the dashboard. When the month's online bookings reach eighty per cent (80 %) of the limit, the Provider notifies the Customer by email at the account address, once a month. If a month goes beyond sixty, the Provider tells the Customer by email, before the month ends, that the account will move to the Pro plan, at that plan's price, and on the 1st of the following month the account moves to the Pro plan on the same billing period (monthly or yearly). Nothing is charged that day: the Pro price is charged from the subscription's next renewal, with no proration of the period already paid. If the account is still in its trial, the change is made all the same, but nothing is charged until the trial ends. If the month only goes beyond sixty in its last hours and the Provider can no longer tell the Customer before the 1st, the account does not change plan for that month. While the move to Pro is scheduled, the Customer can only bring it forward by moving to Pro from the dashboard; once on Pro, the Customer can move back to Basic under section 4. The move to Pro for the limit does not cancel any change of plan or billing period the Customer had scheduled for renewal (section 4): that change applies at renewal as the Customer scheduled it.

Final count. On the 1st, before applying the change, the Provider counts the whole month's online bookings again. If, leaving out the bookings cancelled, rejected or marked as no-shows up to that moment, the month has ended at sixty or fewer, the move to Pro is cancelled, the account stays on Basic and the Provider tells the Customer by email. Bookings cancelled, rejected or marked as no-shows after the final count no longer undo the change; the Customer may move back to Basic under section 4.

Review of the change. The Provider may review a move to Pro scheduled because of the limit and, where appropriate, cancel it, on its own initiative or because the Customer tells it at hola@taula.ai, before the 1st, that a booking was counted that should not have been. If the Provider cancels it, that month's bookings no longer lead to a move to Pro.

The limit never blocks the guest: the booking page keeps accepting bookings even after the month has passed sixty, and the Provider charges nothing per booking or for those beyond the limit. The Pro and Custom plans have no online booking limit.

Clarification (17 September 2026): this section is completed with how bookings are counted, the month from which the limit is counted, the 80 % notice, the date and manner of the move to Pro, the final count and the review of the change. The version of 16 September 2026 already provided for the limit and the move to Pro, to be put into operation with the notice under section 10; this clarification sets out the detail in the Customer's favour (notice before the change, no charge on the day of the change, the final count, no blocking, and the option to return to Basic without conditions) and does not change the version.

3. Payment and non-payment

Payment is made through Stripe, by card or by SEPA Direct Debit. The Customer undertakes to keep a valid payment method on file and to provide accurate, up-to-date billing details.

Direct debit. When choosing it, the Customer accepts on Stripe's payment page a SEPA Direct Debit mandate under the Core scheme, authorising the Provider and Stripe, its payment service provider, to send instructions to the Customer's bank to debit each fee from the account given, and the bank to debit it. Debits are presented with the mandate's unique reference and the creditor identifier shown on it, and the Customer may request a copy of the mandate at hola@taula.ai. Stripe sends the Customer a notice of each debit, with the amount and date, which may arrive as little as two (2) calendar days before the debit; the Customer accepts this period instead of the fourteen (14) days the scheme provides by default. The Customer may ask its bank to refund a debit without giving a reason within eight (8) weeks, and up to thirteen (13) months if the debit was unauthorised, under the terms of its agreement with its bank. A returned debit does not cancel the subscription or discharge the fee owed. The Customer may revoke the mandate with the Provider or with its bank; if it does, it must set up another payment method before the next debit.

In the event of non-payment —including a returned direct debit—, the Provider will notify the Customer and may suspend the Service seven (7) calendar days after the first failed charge. Suspension means the public booking page stops accepting requests and the business website stops being published; the Customer's data is retained as set out in section 8.

4. Term and cancellation

The subscription runs indefinitely and renews automatically for periods equal to the one contracted: month by month or year by year. The Customer may cancel at any time from the dashboard or by written notice; cancellation takes effect at the end of the period already invoiced, with no refund of the unused portion, unless applicable law provides otherwise.

On yearly billing, the year's fee is earned in full in advance and no part of it is refunded if the Customer cancels before the year ends: the Service continues until the end of the period paid for, and renews for another year at the yearly price then in force unless the Customer cancels or moves to monthly billing beforehand.

Plan and billing-period changes. The Customer may change plan (Basic or Pro) and billing period (monthly or yearly) from the dashboard, which asks for confirmation before applying any change. An upgrade from Basic to Pro on the same billing period applies immediately, with proration: the remainder of the current period at the Pro price, less the unused part of Basic, is added to the subscription's next invoice, and the Pro price is charged from then on.

A downgrade from Pro to Basic and a change of billing period (monthly to yearly or yearly to monthly, including when combined with a change of plan) apply at renewal, at the end of the period already invoiced: so that the renewal already runs on the new plan and billing period, the change is applied within the thirty-six (36) hours before the renewal date. Until then the current plan, billing period and price remain, with no refund for the rest of the period. On a downgrade, the Basic price is charged from the renewal. On a change of billing period, when it applies the first period of the new billing period is invoiced, less any unused part of the previous one. The scheduled change is shown in the dashboard and, until it applies, the Customer may cancel it by writing to hola@taula.ai or, where the dashboard offers the option, from the dashboard itself.

During the trial, as long as nothing has been charged, plan and billing-period changes apply immediately and involve no charge. If the Customer sets up payment with less than forty-eight (48) hours of the trial left, the first period is charged at that moment and, from then on, changes follow the preceding paragraphs. The Custom plan, and subscriptions taken out at a per-account price before the Basic and Pro plans, are not changed from the dashboard: the change is requested in writing. The move to Pro for going over the booking limit is governed by section 2 bis.

Clarification (17 September 2026): the three preceding paragraphs set out how the upgrades, downgrades and billing-period changes already provided for in this section apply, and how the yearly plan renews. They do not change the version.

The Provider may terminate on thirty (30) days' notice should it decide to discontinue the Service; and immediately in the event of material breach by the Customer, in particular use of the Service for unlawful purposes or repeated non-payment.

5. Customer obligations

• Use the Service lawfully and in accordance with these Terms, and not for unlawful purposes.
• Safeguard its credentials and be answerable for activity carried out from its account.
• Ensure it has a valid legal basis and provides adequate information for processing the personal data of its own customers entered or managed on the platform, in particular allergies and intolerances, which may constitute health data.
• Ensure it holds the rights to the content it supplies (text, photographs, logos, menu).
• Review and approve the website before it is published, and keep its information up to date (hours, prices, allergens, contact details), as set out in section 9.
• Not attempt to access other customers' data or do anything that compromises the security or availability of the Service.

6. Service availability

The Provider will use reasonable means to keep the Service continuously available but does not guarantee any particular level of availability nor the absence of errors or interruptions. The Service may be interrupted for maintenance, by incidents affecting its infrastructure providers, or by force majeure.

The Service is provided "as is", without express or implied warranties of merchantability, fitness for a particular purpose or commercial outcome. The Customer is responsible for maintaining reasonable fallback procedures for its business.

7. Liability

The Provider shall be liable only for direct damage actually caused by wilful misconduct or gross negligence in providing the Service. Indirect damages, loss of profit, loss of custom, lost bookings or revenue and reputational harm are expressly excluded.

In any event, and save for wilful misconduct, the Provider's total aggregate liability to the Customer on any ground is limited to the amount actually invoiced to the Customer in the three (3) months preceding the event giving rise to the claim.

The Customer shall hold the Provider harmless against third-party claims arising from its use of the Service, from the content it supplies, or from breach of its data protection obligations towards its own customers.

8. Customer data and return

The data the Customer enters into the platform —bookings, guest records, menu and configuration— belongs to the Customer. During the term it may export it or request a copy at any time.

On termination, the Provider will retain that data for thirty (30) calendar days to allow recovery and, after that period, will delete it, except for data it must keep by law (in particular, invoicing records).

9. Intellectual property and the Customer's website

The Service, its software, its design and its trade marks belong to the Provider. The subscription grants the Customer a non-exclusive, non-transferable right of use limited to the term of the contract.

The website is a rental. The website the Provider builds, publishes and maintains for the Customer within the Basic and Pro plans is provided on a rental basis(a licence to use), and not as a sale, a commissioned work or the delivery of a product. The Provider is its sole owner, and holds all intellectual property rights in the template, the source code, the design (structure, style and layout), the texts generated by the Provider —with or without the help of artificial intelligence— and the taula.ai subdomain on which it is published. None of these elements is ever transferred to the Customer, neither during the subscription nor when it ends.

Licence to use. While the subscription is active, the Customer holds a non-exclusive, non-transferable, non-sublicensable and revocable licence to use the website, tied to the subscription, for its business without any restriction on use and paying nothing for hosting, certificate or content changes, all of which the Provider bears in full. The licence ends automatically when the subscription ends, for any reason. The Provider may revoke it and unpublish the website, notifying the Customer at the account email address, if the site is used for purposes contrary to the law or to these Terms, or if content that infringes third-party rights is published on it and the Customer does not remove it when asked.

Subdomain. The Customer's website is published on a taula.ai subdomain bearing the business name (for example, yourname.taula.ai). The subdomain belongs to the Provider and is licensed for use for as long as the subscription lasts: the Customer acquires no rights over the taula.ai domain or the subdomain, and may not assign or transfer it. Where two businesses ask for the same name, the Provider assigns it in order of sign-up, and may require a different one where it matches a third party's trade mark or is misleading.

The Customer's content. The content the Customer supplies —its own texts, photographs, menu, logo and brand— is and remains the Customer's. The Customer only grants the Provider a free, non-exclusive licence, limited to the term of the subscription, to reproduce that content, adapt it to the site's format and display it on the website and on the booking page. The business information (hours, prices, dishes, contact details) belongs to the Customer; the texts the Provider writes from that information belong to the Provider.

AI-assisted generation. The Provider builds the site from the public information on the business's Google listing, the menu and the photographs the Customer supplies, using artificial intelligence models to draft the texts and arrange the menu. The result is a draft that the Provider does not review before showing it, and the Customer reviews and approves it before it is published; afterwards the Customer can correct any content from the dashboard. Generated texts may contain inaccuracies: the Customer is the one who knows their business and who answers for what is published.

Responsibility for content. The Customer warrants that it holds the rights to the photographs, texts, logo and menu published, and that the information (hours, prices, allergens, contact details) is accurate. Photographs taken from Google, social networks or other websites may not be published without the rights holder's permission; the Provider may remove them on receiving a complaint. To publish the site, the Customer provides the business owner's details (name or company name, tax ID and address) that the law requires for the site's legal notice and privacy policy; until they are provided, the site may be kept unpublished or unindexed.

End of the subscription. When the subscription ends, for any reason (cancellation, non-payment or termination), the Provider unpublishes the website. The Customer has no right to any compensation, to a transfer of the site, to delivery of the source code, the template, the design, the generated texts, the site files or any other material, or to go on using the subdomain: nothing is transferred. The Provider will supply a copy of the content the Customer supplied if requested within the period in section 8.

Editing policy. The Customer freely changes the site's content from the dashboard, at no cost: hours and holidays, phone number, menu and prices, photographs and notices. The design (template, structure and style) is fixed and is not customised within the Basic and Pro plans. If the Customer wants a different design, the Provider can regenerate the site at a fixed price quoted in writing, or the Customer can move to the Custom plan.

Custom plan. The Custom plan website is produced under a separate written quote and is governed by its terms, including as to ownership of what is delivered; this section applies to it only where the quote is silent.

Your own domain. On the Pro plan, the Customer may publish the site on its own domain name. The domain is registered in the Customer's name and its registration and renewal cost is billed separately, at cost; the Provider manages its technical configuration. A domain registered in the Customer's name belongs to the Customer: when the subscription ends the Customer keeps it and may point it wherever they wish. Where the Provider registered the domain name on the Customer's behalf, the Customer may request its transfer into their own name at any time, including when the subscription ends, bearing only the applicable transfer and renewal costs. If no such request is made within thirty (30) days of the end of the contract, the Provider may let the domain lapse or cancel it.

Where the Provider registers the domain on the Customer's behalf, it does so in its own account with a registrar, with the Customer as registrant and using the registrant details the Customer provides, which must be accurate; the Provider acts only as technical manager and acquires no rights in it. While the subscription lasts, the Provider renews it before it expires and passes the cost on to the Customer. When the Customer requests a transfer, the Provider gives it the authorisation code and removes the transfer lock within ten (10) business days, unless the registry's rules prevent it (for example, in the days following a registration or a previous transfer). Before letting a domain lapse or cancelling it at the end of the contract, the Provider notifies the Customer by email fifteen (15) days in advance.

10. Changes

The Provider may amend these Terms on at least thirty (30) days' notice. If the Customer does not accept them, it may cancel the subscription before they take effect. Continued use of the Service after that date constitutes acceptance.

11. Governing law and jurisdiction

These Terms are governed by Spanish law. For any dispute, the parties submit to the Courts of Barcelona, expressly waiving any other jurisdiction that might apply.

Annex I. Processing of personal data (Art. 28 GDPR)

This Annex forms an inseparable part of the Terms and governs the processing of personal data carried out by the Provider on behalf of the Customer.

Roles. The Customer is the controller of the personal data of its own end customers (guests). The Provider acts as processor.

Subject matter, duration and nature. The processing consists of hosting and managing bookings, guest records and associated communications, through collection, recording, storage, consultation, modification, disclosure to the Customer itself and erasure. Its duration matches the term of the contract, plus the retention period in section 8.

Types of data and categories of data subjects. Identification and contact data (name, phone, email, language), booking data (date, time, party size, table, visit history and no-shows), internal staff notes and, where the Customer chooses to collect them, food allergies and intolerances, which may constitute health data (Art. 9 GDPR). The data subjects are the Customer's end customers.

Provider's obligations as processor. The Provider undertakes to:

• Process the data only on documented instructions from the Customer, including those arising from normal use of the platform, and not use it for its own purposes.
• Ensure persons authorised to process the data commit to confidentiality.
• Apply the technical and organisational measures of Art. 32 GDPR: encryption in transit and at rest, per-account access control and logical separation of each customer's data, authentication managed by a specialist provider, and activity logging.
• Assist the Customer in responding to data subject rights and in complying with Arts. 32 to 36 GDPR, insofar as the information is available to it.
• Notify the Customer without undue delay, and in any case within 48 hours of becoming aware, of any personal data breach affecting it, with the information available.
• At the Customer's choice, delete or return the data on termination, as set out in section 8, save where retention is legally required.
• Make available to the Customer the information necessary to demonstrate compliance with these obligations and allow reasonable audits, on request with sufficient notice.

Retention periods. While the contract is in force, bookings and customer cards are kept on the Customer's behalf for a maximum of twenty-four (24) months from the last visit, and are automatically deleted once that period has passed. On termination, the Provider keeps them for thirty (30) days so that the Customer can recover them and then deletes them, except for what it must keep by law.

Sub-processors. The Customer gives general authorisation for these sub-processors, which are also listed in the Privacy Policy:

• Amazon Web Services EMEA SARL (AWS): hosting, database, authentication, email and file storage; Amazon CloudFront, which delivers the public pages (the booking page, the menu and the websites); and Amazon Bedrock, with the artificial intelligence models that read and translate the menu and draft the website texts.
• Google Ireland Limited: the Google Places API, to find the business's public listing when the Customer signs up or builds its website from the dashboard. It receives only the business name or link that is typed, no guest data.Clarification (4 October 2026): the dashboard includes Google Maps features and content (the business listing search). Use of those features and that content is subject to the then-current versions of the Google Maps/Google Earth Additional Terms of Service and the Google Privacy Policy. The details the dashboard suggests from the listing only serve to fill in the sign-up form: the Customer checks, corrects and confirms them, and what is saved is its own business's details as it confirms them.
• Stripe Payments Europe, Limited (Ireland): collecting booking deposits from guests, where the Customer enables them; the Customer is the seller, with its own account connected to Stripe.
• Meta Platforms Ireland Limited (WhatsApp Business Platform): when the service becomes available and only if the Customer enables the WhatsApp booking reminder (section 2), to send it to the guest. It receives the guest's phone number, the language of the message, the restaurant's name, the date and time of the booking, its code (or, if it has none, the party size) and the booking's management link, with which it can be changed or cancelled; and it returns the message's delivery status and, if the guest replies, the reply, which is not read or stored.

In addition, for the Customer's own billing data, for which the Provider is controller and not processor, the Provider uses Stripe to collect the subscription and Holded Technologies, S.L. (Spain, data hosted in the European Union) as invoicing software; neither of these involves guest data.

The Provider will give at least thirty (30) days' notice of any addition or replacement of sub-processors, during which the Customer may object on reasoned grounds and, in that case, terminate without penalty. The Provider will impose on sub-processors obligations equivalent to those undertaken here. The Provider will not engage any other processor without this general authorisation and the notice indicated, and will remain answerable to the Customer for their performance.

Location and transfers. Booking, guest record and account data are processed and stored in the European Union: in the eu-west-3 region (Paris), together with outgoing email and the restaurants' websites; inbound email to the domain and the taula.ai website, with the booking page and the menu, are hosted in the eu-west-1 region (Ireland); and processing with Amazon Bedrock uses inference profiles that only route to AWS regions in the European Union.

The public pages are delivered with Amazon CloudFront, which serves them from the AWS point of presence that is fastest for the visitor: visitors in the European Union are normally served from Europe, and the restaurants' websites are only served from points of presence in Europe, North America and Israel. Where a visitor connects from outside the European Economic Area, their IP address and request may be processed at a point of presence outside it, solely to serve the page and without storing any booking data there. That transfer relies on the European Commission's adequacy decisions (such as those for the United Kingdom, Switzerland, Canada and Israel, and the EU-US Data Privacy Framework, to which Amazon.com, Inc., including AWS, adheres) and on the standard contractual clauses in the AWS data processing addendum. The other cases of data outside the Union are Google Analytics, described in the Cookies Policy, which is only enabled with the visitor's consent, and, when the service becomes available and the Customer enables it, the WhatsApp reminder: Meta may process that data outside the Union, relying on the EU-US Data Privacy Framework, to which Meta Platforms, Inc. adheres, and on the standard contractual clauses in its data processing terms.

Artificial intelligence. The model processing described in the Privacy Policy takes place within the European Union and, under the provider's terms, the data is not used to train models.

Customer instructions. If the Provider considers that an instruction from the Customer infringes data protection law, it will inform the Customer immediately.