No Errands Tables connector: privacy
Effective 2026-09-21. This page covers the restaurant table connector run by Maren Technologies LLC, a company organised in Missouri, United States. The general policy is at /privacy; where the two differ, this page governs the tables connector.
In one sentence: to ask a restaurant for a table we need the restaurant's number and enough about the booking for a host to answer, we say that much out loud on a phone call or in a text, and we scrub the diner's details 30 days after the request settles.
There are two different people on this page: the diner, who is our customer, and the restaurant, which is a business we contact on the diner's behalf. Their data is handled differently and both halves are below.
What this connector receives about the diner
| What | Example | Why we need it |
|---|---|---|
| The diner's first name | Rob |
It is the name the table goes under, and we read it to the restaurant |
| Party size | 4 | The restaurant cannot answer without it |
| Date and time wanted | 2026-09-25T19:00:00-05:00 |
Same |
| The diner's phone number | +14175550123, optional |
Passed on only if the diner offers it, so the restaurant can call about a change |
| Notes | Up to 200 characters, optional | Read to the restaurant verbatim: "high chair", "one wheelchair user" |
| Your email address | From when you created your API key | Receipts and support |
| Request metadata | Timestamp, IP address, endpoint, status | Security, rate limiting, debugging |
A first name is enough, and the connector brief tells the agent to ask for no more than that. The diner's phone number is optional and is never guessed: either the diner offered it or we do not have it.
What the restaurant is told
Only what a host needs to answer: the party size, the date and time, the first name the table goes under, any note, and the diner's callback number if the diner gave one. Every message says who is asking and how to stop receiving them.
We do not tell the restaurant the diner's email address, their full name, or anything else about them, because none of that helps a host say yes or no.
What this connector holds about the restaurant
| What | Why we need it |
|---|---|
| The restaurant's name and published phone number | To call or text it, and to tell the diner who answered |
| City and state | So we know where it is |
| Whether the line is a mobile, a landline or VoIP | A text to a landline reaches nobody |
| Whether it has agreed to receive texts, and when | It is the consent record US carrier rules require |
| Whether it has asked never to be contacted again | So we never do |
| A contact name and email, only if a restaurant gave them on our sign-up form | So a person, and not just a number, can be reached about the sign-up |
| Every message and keypress, in both directions | So a dispute about what a restaurant was told, or answered, has an answer |
A restaurant's phone number is the business's own published number. We do not buy restaurant lists that carry personal data, and we do not enrich what we hold with anything from a data broker.
Why we have it
Only to ask for the table you asked for, tell you what the restaurant said, and keep an accurate record of both. We do not use any of it to train models and we do not use it for marketing. Nothing we send a restaurant advertises anything.
Who we share it with
- Sinch, our voice and messaging provider, which places the automated calls and carries the texts. It receives the restaurant's number and the wording of the request, which includes the party size, the time and the first name. It processes this for us under contract and may not use it for its own purposes.
- The telephone network, which carries the call or the message.
- The restaurant itself, which hears or reads the request. That is the point of the product.
- Stripe, if you buy credits, or if a restaurant pays for its plan. Stripe receives the email address, the amount, and for a restaurant plan the business name and phone number given at checkout. Card details go to Stripe directly, never to us.
- Our hosting provider, which runs our servers.
- Law enforcement or a court, if legally required.
We do not sell your data or share it for advertising.
Text messages and mobile numbers
Mobile numbers will not be shared or sold with affiliates or third parties for marketing or promotional purposes. Text messaging opt-in data and consent are never shared with any third party. The only outside company that sees a mobile number is the carrier partner that delivers our messages, and only to deliver them.
Agents only act with your approval
If you reach this connector through an AI agent such as Meta's Muse, the agent uses an API key you created and stored in the agent's secure credential store. The connector brief the agent reads requires it to:
- confirm the restaurant, the party size, the date and time and the name with you, and get your explicit approval before every request, because a real business is about to be telephoned;
- use the number it actually found for that restaurant and never invent one;
- use one idempotency key per request, so a retry cannot contact the restaurant twice;
- never tell you the table is booked before the restaurant has said so.
Nothing is sent without that approval. Our responses to the agent contain data only, never instructions.
How a restaurant controls this
- Reply STOP to any text, or press 9 on any call. We stop immediately, clear any agreement to receive texts, close whatever request was open, and never contact that number again through this connector.
- A restaurant that has not asked for texts is only ever called, never texted.
- A restaurant that signed up at for restaurants can email support@noerrands.com to have the contact name and email address it gave us deleted. We keep the phone number and the opt-out flag, because deleting an opt-out record is not the same thing as honouring it.
- A restaurant that gave an email address on the sign-up form gets each reservation request by email as a backup for a missed call, with Confirm and Decline links that work for that one request only. Every such email carries a link that stops the emails; calls are not affected. The address is used for nothing else and shared with nobody but the email provider that delivers the message.
- A restaurant can be sent a private inbox link, a page that lists its open requests with a Confirm and a Decline button. The link is the only key to that page, it is tied to the restaurant's number, it is replaced whenever a new one is sent, and an opt-out cancels it. We store only a one-way hash of it. An answer given on that page is logged exactly as a keypress or a text reply is.
How long we keep it
| Data | Retention |
|---|---|
| The diner's name, phone and note on a request | 30 days after the request settles: the name is cut to an initial and the phone and note are deleted |
| Request record: party size, time, status, restaurant, amount charged | Kept with your billing history; after the scrub it holds only the diner's initial |
| Messages and keypresses in both directions | Their text, which repeats the diner's name, callback number and note, is deleted on the same schedule as the diner's details. The channel, direction and time are kept as the record that the restaurant was contacted |
| A saved copy of a request's result, kept so a retried request is answered without being repeated | Deleted once it is 24 hours old, by the next daily sweep |
| The restaurant's number and its opt-out flag | Kept, so an opt-out outlives every request that set it |
| Billing ledger and receipts: amounts, dates and references, no addresses or content | At least 7 years, because tax rules require it |
| Technical logs | Up to 90 days. Rate-limit counters, which hold IP addresses, are deleted within 3 days |
Deleting your data
Ask your agent to delete your data and it calls delete_my_data, which scrubs
the diner details from every request on your account, and the text of every
message and keypress logged for them, straight away, whatever their age.
It also deletes the saved copies of your recent results, erases the email address on your account and revokes your keys. You can also email support@noerrands.com from the address on your
account; we will revoke your keys and delete your request records within 30
days, keeping only what tax and legal rules require in the billing ledger.
You can also ask for a copy of what we hold, or ask us to correct it.
A request a restaurant has already answered cannot be recalled, and anything in the billing ledger stays there as tax rules require.
Other people's details
If you give us a diner's phone number or a note about them, you are giving us information about someone else. Only ask for tables for people who know you are asking, and keep notes to what the restaurant needs.
Where this applies
United States restaurants only. Requests are handled at the Cloudflare data centre nearest whoever sent them, which can be outside the United States, and our database is placed in North America. Sinch, which places the calls and texts, is based in Sweden; texts go through its US region, and calls and number lookups go through its global endpoints. See where your data is processed.
Contact
Maren Technologies LLC, support@noerrands.com. General policy: /privacy. Connector terms: /connectors/tables/terms.