Skip to content
ring2table
  • Home
  • Features
  • How it works
  • Pricing
  • FAQs
  • Contact
Log in Start free

Privacy Policy

Last updated: November 17, 2026

This page is always the current version. If you saved or printed a copy, check this page or ask us through our contact form before you rely on it.

The short version

  • We collect only what we need to run bookings, waitlists, tickets and phone answering for restaurants.
  • We never sell personal information, and we never share it for advertising.
  • Each restaurant's guests belong to that restaurant. We never show them to other restaurants or use them to promote anyone.
  • We text guests only about their own booking. We never send promotional texts.
  • You can ask to see, correct or delete your information.

This policy explains what personal information ring2order, LLC ("we", "us") collects through ring2table™, what we do with it and who sees it. ring2table is a product of ring2order, LLC. It covers the ring2table service, the dashboard, the booking pages and waitlist kiosks we run for restaurants, and this website (together, the "Service"). Questions? Use our contact form.

1. Who this policy is about

  • Restaurants: businesses that sign up for ring2table, and the people who use their accounts.
  • Guests: people who book a table, join a waitlist, pay a deposit or buy event tickets at a restaurant that uses ring2table. We handle guest information for the restaurant. The restaurant decides how it uses its bookings and guest records, and its own privacy policy applies too.
  • Callers: people who call a restaurant whose phone is answered by ring2table's virtual host (optional phone answering). We handle caller information for the restaurant too.
  • Website visitors: people who visit ring2table.com.

2. What we collect

From restaurants

  • Account details: name, email address and password. We store passwords in a scrambled (hashed) form that we can't read.
  • Restaurant details: name, address, contact details, opening and booking hours, tables, floor plan, booking rules, deposit and event settings, and, if you use phone answering, your menu, call settings and voice choices.
  • Billing details. Our payment processor handles your card. We never see or keep your full card number. The processor tells us your name, email, billing address, subscription status and payment records.

From guests who book or join a waitlist

  • What a guest enters on a booking page or waitlist kiosk, or tells the restaurant's staff: name, mobile number, party size, date and time, notes and answers to the restaurant's questions.
  • The guest's history at that restaurant: bookings, changes, cancellations, visits and no-shows.
  • For deposits and card holds: the amount, and whether it was paid, refunded or charged. Guests type their card details on our payment processor's secure page. We never see or keep full card numbers.

From people who buy event tickets

  • Name, mobile number and email (if given), the event and tickets bought, whether the order was paid or refunded, and when each ticket was checked in at the door. Card details go on our payment processor's secure page. We never see or keep full card numbers.

From callers (optional phone answering)

  • The caller's phone number and the date, time and length of the call.
  • A recording of the call and a written transcript.
  • What the caller says, such as their name, booking details, questions and any message for the restaurant.

From website visitors

  • Basic technical details, such as IP address, browser type and pages visited, which our hosting provider collects to keep the site safe and working.
  • Anything you send us, for example through our contact form.

3. What we use it for

  • To take, change and cancel bookings, run waitlists and floor plans, and show bookings and guest records to the restaurant.
  • To let guests change or cancel a booking, or see their tickets, through a private link.
  • If the restaurant uses phone answering, to answer calls, take, change and cancel bookings, answer questions, pass calls and messages to staff, and show calls, recordings, transcripts and messages to the restaurant.
  • To text guests about their booking or waitlist place (see below).
  • To take deposits, card holds and ticket payments for the restaurant, and to check tickets at the door.
  • To run accounts, billing and support.
  • To keep the Service secure and stop fraud, spam and abuse.
  • To improve the Service, for example by looking at bookings that went wrong.
  • To follow the law.

We never sell personal information, and we never share it for advertising (the law calls this "cross-context behavioral advertising").

Text messages. A guest who gives a mobile number when booking or joining a waitlist gets texts about that booking or waitlist place only: for example a confirmation, a reminder, a change or cancellation, or "your table is ready". We send them for the restaurant. How many you get depends on your bookings. Message and data rates may apply. Reply STOP to stop texts or HELP for help. We never send promotional texts, for ourselves or for anyone else, and booking a table never signs you up for them. If a restaurant wants to send you offers, it must use its own text service and ask for your consent separately. We never share mobile numbers or text consent with anyone for marketing. Mobile numbers go only to the providers that deliver the texts.

4. Each restaurant's guests stay with that restaurant

The guest information a restaurant collects through ring2table belongs to that restaurant.

  • Each restaurant sees only its own guests and bookings. If you book at two ring2table restaurants, neither one sees your booking at the other.
  • We never share a restaurant's guest list with another restaurant.
  • A guest's mobile number is used only for texts about that guest's own booking or waitlist place. The restaurant sees it with the booking, so it can call about it, but can't download it or use it for marketing.
  • We never use a restaurant's guests to promote other restaurants, and we never let other restaurants market to them.
  • Guests book on the restaurant's own booking page, which shows the restaurant's name, or through ring4food™, our restaurant directory. Either way, the booking and the guest belong to that restaurant, and we never use them to promote other restaurants.

5. Phone calls answered by a virtual host (optional phone answering)

When a restaurant turns on phone answering, calls are answered by a computer-generated virtual host that uses artificial intelligence from outside providers. Those providers process the call audio and transcript so the virtual host can understand and answer the caller. They have agreed to protect the information and use it only to provide their service to us. The virtual host tells every caller at the start of the call that the call is recorded.

6. Who we share information with

  • The restaurant the guest booked with or the caller called. It sees only its own bookings, guests, tickets, calls, recordings, transcripts and messages.
  • Service providers that help us run the Service: phone, text messaging, call recording and phone number checks; speech and artificial intelligence; database and file storage; website hosting, security and spam protection; web fonts; and payments and sales tax. They may use the information only to provide their service to us.
  • Our payment processor, for guest payments. Deposits, card holds and ticket payments go into the restaurant's own payment account. The processor's own privacy policy covers the card details guests give it.
  • The law and safety: when the law requires it, or to protect the rights, safety and property of our customers, guests, the public or us.
  • A new owner: if our business is merged or sold, this policy keeps applying to the information.

7. How long we keep it

  • Call recordings are deleted automatically after 90 days.
  • Bookings, tickets, transcripts, call records and guest records are kept while the restaurant's account is open, so it can look back at its history, and for a reasonable time after, unless the restaurant asks us to delete them sooner.
  • Account, billing and payment records are kept as long as tax, accounting and legal rules require.

8. Keeping it safe

We use reasonable safeguards: encrypted connections, controls that keep each restaurant to its own data, and limited access to our systems. No system is perfectly secure, so we can't promise that nothing will ever go wrong.

9. Cookies

This website uses no advertising or tracking cookies. We may count page visits with a tool that uses no cookies and doesn't follow you to other websites; it shows us things like which pages are visited, the site you came from and your country, but not who you are. Our hosting provider may set cookies needed for security, and our forms use an automatic check to stop spam. The ring2table dashboard and waitlist kiosks store a small amount of information in your browser to keep you signed in. Our payment processor's checkout page may use its own cookies, explained in its own privacy policy.

10. Your rights

Depending on where you live, you may have the right to see, correct, delete or get a copy of your personal information, and to object to or limit some uses of it. California residents have these rights under the California Consumer Privacy Act.

  • Restaurants can change most information in the dashboard, or contact us.
  • Guests should contact the restaurant they booked with. You can also write to us through our contact form, and we will pass your request to the restaurant or help where we can.

To make a request, use our contact form and choose "Privacy request". We may need to check who you are first. Using your rights will never change how we treat you.

11. Children

The Service is for businesses and is not aimed at children under 13. We don't knowingly collect personal information from children through this website.

12. Where information is kept

We are based in the United States, and we store and process information in the United States. Some of our service providers may also process it in other countries as part of their service to us.

13. Changes to this policy

We may update this policy. When we do, we change the "Last updated" date above. For big changes, we tell restaurants by email or in the dashboard.

14. Contact

ring2order, LLC
Customers: our contact form.
Everyone else: our contact form.

ring2table. Tables booked. No per-guest fees.
  • Home
  • Features
  • Pricing
  • FAQs
  • Contact
  • Terms of Service
  • Refund Policy
  • Privacy Policy
  • Accessibility
© 2026 ring2order, LLC. All rights reserved. ring2table was built by a former restaurant owner who got tired of all the fees. Payments are processed securely.