mee-table

mee-table lets you accept table reservations, manage prepayments (card/digital wallet), offer gift cards, and run no‑show protection, all from your WordPress site. The plugin works as a client for the mee‑table SaaS backend at api.mee-table.com, freeing you from server maintenance.

Main features:

• Table reservations with availability, opening hours, rules on the number of guests, a weekly closing day and a quick-block calendar for one-off closures.
• Guests manage their booking on YOUR site. The link in every email and message opens your own booking widget, on your own pages, in edit mode: the guest moves the date, the time or the number of guests, or cancels, inside the limits you set. A per-venue cap says how many people one booking may bring (the venue capacity is a separate number), and an optional notice window closes online changes some hours before the table, after which the guest is asked to call you.
• Move a booking instead of losing it. The guest can change the day, the time or the number of people from the link in their confirmation email, without calling: the free tables are re-checked live, and you decide how many times they may do it before they are asked to phone you. Your own staff can move any booking from the Waiter Dashboard, with no limit, the phone rings there.
• Your own time zone, so opening hours and reminders are right even when the venue and the server are in different countries.
• Prepayment by time band. An “Aperitivo” rate from 19:00 to 20:00 and a different one for dinner, each with its own days of the week and minimum number of guests. The guest is only ever offered the rate that covers the time they picked, and when a rate covers it the prepayment replaces the no-show card guarantee: nobody is asked to pay twice for the same evening.
• Choose which emails reach you. Everything that happens to a booking sends you an email by default, confirmed, declined, cancelled or moved, including what your own staff did from the dashboard. Untick the ones you do not want; your guests keep receiving theirs either way.
• No-show guarantee: the guest’s card is authorised, not charged. Nothing is taken unless they fail to turn up, and staff release or charge it from the Waiter Dashboard.

The full feature list continues in the “All the features” section below.

External services

This plugin relies on external services. Below is what each one is, when it is
contacted, and what is sent to it.

1. mee-table backend (https://api.mee-table.com): always required

The plugin is a client for the mee-table SaaS. Every page of the admin and every
booking talks to it. Data sent: reservation details (guest name, email, phone,
number of guests, date, notes), location configuration, prepayment and gift-card
records, staff accounts, and any photo you upload for a cooking class. Without
this service the plugin cannot show availability, take payments or store
bookings. Provided by mee-table.
Terms: https://mee-table.com/terms | Privacy: https://mee-table.com/privacy

Two calls to the same provider happen outside the admin pages, and are listed
here separately so it is clear when they occur:

• Activating the plugin sends nothing anywhere. The first contact happens
  when you enter your licence key and press Activate: at that moment, once,
  the plugin asks https://mee-table.com/api/provisioning whether this domain
  already has a mee-table account, so the site connects to its own restaurant
  without anyone typing a token. Data sent: the site URL (get_site_url())
  and nothing else. If it fails, the plugin simply carries on unconfigured.
  Until a licence key is entered, the plugin contacts no server at all.
• Once a day, a scheduled task asks https://api.mee-table.com/api/license/validate
  whether the subscription is still active. Data sent: the site URL, the
  licence key the site owner entered, and the name of the product asking
  (mee-table), so a key bought for mee-class does not unlock bookings.
  How that data is handled:
  https://mee-table.com/privacy This call does not happen at all until a
  licence key has been entered: with no key the task returns immediately.

No guest data is involved in either of these two calls.

2. Payment providers: only when you enable and connect them

Mollie, Stripe or PayPal are contacted to create payments, authorise no-show
guarantees and issue refunds. Data sent: amount, currency, reservation
reference, and the guest’s payment details entered on the provider’s own hosted
page. Card numbers never pass through WordPress.
Mollie: https://www.mollie.com/en/user-agreement | https://www.mollie.com/en/privacy
Stripe: https://stripe.com/legal | https://stripe.com/privacy
PayPal: https://www.paypal.com/legalhub/home

3. SMS providers: only if you choose one, and only for the messages you send

If you configure an SMS provider, your site sends the reminder text and the
guest’s phone number to it. Two paths exist: reminders are dispatched by the
mee-table backend, while the “Send test SMS” button sends one message
directly from your own WordPress server to the provider, using the
credentials you typed in. Nothing is sent to any of these companies unless you
select them and save credentials. The panel also accepts a custom HTTP
gateway: in that case the same two pieces of data go to the endpoint
address you type in yourself, and to nobody else.

Twilio: https://www.twilio.com/en-us/legal
Skebby (Commify Italia S.r.l.): terms https://www.skebby.it/wp-content/uploads/Contratto-SKEBBY.pdf | privacy https://www.skebby.it/wp-content/uploads/Informativa-Privacy-Estesa-SKEBBY.pdf
Aruba SMS: https://hosting.aruba.it/documents/term_conditions/condizioni_fornitura_servizisms_aruba-it_v-1-2.aspx | https://www.aruba.it/documents/tc-files/it/11_it_privacy_policy_aruba_spa.aspx
Brevo: https://www.brevo.com/legal/
Vonage: https://www.vonage.com/legal/ (its SMS endpoint is still the old brand name, https://rest.nexmo.com)

SMSGate (https://api.sms-gate.app): only if you choose the Android phone gateway

If you pick “Android phone” as the SMS route, your site does not talk to the
phone directly: it sends the reminder text and the guest’s phone number to the
SMSGate cloud at https://api.sms-gate.app/3rdparty/v1, which passes the
message to the free SMSGate app on your own phone, and the message then leaves
from your own SIM. This happens only for the messages you send, and only after
you have installed the app and saved its username and password in the panel.
SMSGate is an open-source project (the app is at
https://github.com/capcom6/android-sms-gateway) and the cloud service is run by
its authors.

SMSGate: https://sms-gate.app/terms-of-service/ | https://sms-gate.app/privacy/

A “generic HTTP” option exists for providers not in the list: there the
endpoint is the one you type in, and you are responsible for it.

4. Meta / WhatsApp Business Cloud API (https://graph.facebook.com): only if you set up WhatsApp messages

If you fill in the WhatsApp fields of a location (phone number ID, WhatsApp
Business Account ID and access token, all obtained from your own Meta Business
account), your WordPress site talks to Meta directly in three cases, and never
otherwise:

• “Create the message templates on Meta”: reads the message templates that
  already exist on your WhatsApp Business Account and submits the missing ones
  for Meta’s approval. Data sent: the wording of the booking messages and your
  access token. No guest data.
• “Send test WhatsApp”: sends one real confirmation message, filled with
  sample values, to the number you type into that field, to check the setup
  works. Data sent: that phone number, the sample values and your access
  token. No guest data.
• The reminder texts themselves are fetched from
  https://mee-table.com/api/whatsapp/modelli, a public page of the mee-table
  site that only returns the wording of those messages. Nothing is sent to it.

The WhatsApp Business Account is yours: you own the number and you pay Meta
directly. mee-table neither resells messages nor owns any number.
Terms: https://www.whatsapp.com/legal/business-terms | Privacy: https://www.whatsapp.com/legal/business-data-processing-terms
Meta Platform Terms: https://developers.facebook.com/terms | Privacy: https://www.facebook.com/privacy/policy

5. Mailchimp: only if you enter an API key

Used to add newsletter subscribers to your audience. Data sent: the email
address and the consent flag of guests who opted in.
https://mailchimp.com/legal/terms/ | https://mailchimp.com/legal/privacy/

6. Groq: only if you enter a Groq API key for the guest assistant

Used by the guest assistant on your booking page. When a visitor types a
question, that question is sent, together with your restaurant’s public
information (name, address, phone, opening times, which time slots are still
free in the next 7 days, discounts and events), to Groq, which produces the
answer. The request is made server-to-server through the mee-table backend
using your own Groq account, so the key never appears in a public page.

Never sent: names, phone numbers or e-mail addresses of your guests, and no
booking of theirs. Free seats are counted; who booked them is not sent.

Nothing at all is sent to Groq unless you have entered a key in
mee-table -> Guest assistant. Leaving that field empty keeps the assistant off
and the script is not even loaded. Groq does not retain these questions for
inference requests and is not permitted to use them to train its models.

Getting a key is free and takes about two minutes at
https://console.groq.com/keys, the plugin explains the steps on that settings
page. The Groq account is yours: the agreement for it is between you and Groq.
Terms: https://console.groq.com/docs/legal/services-agreement
Privacy: https://groq.com/privacy-policy
Acceptable use: https://console.groq.com/docs/legal/ai-policy

Answers are generated by an automated system and can be wrong, and the
assistant tells the visitor that it is automatic. Any answer containing a percentage is
discarded before the visitor sees it. An answer containing an amount is
discarded too, unless you have published prices on the pages you ticked and
that exact figure appears there: the assistant repeats what you wrote, it
never composes a price. On allergens it answers only by repeating what your
own pages say, and any request for a guarantee about a guest’s own health is
sent to your phone instead.

Privacy

This plugin sends reservation data, prepayment details, gift‑card information, and location configuration to the mee‑table backend at https://api.mee-table.com. If you enable the WhatsApp reminders, the guest’s phone number is also sent to Meta’s WhatsApp Business Cloud API so the message can be delivered, using the WhatsApp Business Account that belongs to you. The data is used solely to provide the booking service, payment processing, and no‑show protection. No data is sold, shared with third parties for marketing, or used for advertising. If you enable the guest assistant, visitors’ questions and your restaurant’s public information are sent to Groq through your own Groq account, as described under External services above; no guest personal data is included. For full details, please read the mee‑table Privacy Policy.

Retention: identifying data on a reservation (guest name, email, phone and notes) is irreversibly erased 180 days after the reservation date, by a daily job on the backend. The reservation row itself is kept – date, number of guests, amount, payment gateway – because accounting needs it and none of those fields identifies anyone on their own. That same 180-day window is the furthest back the repeat no-show policy can look.