Privacy
Last updated October 4, 2026
Sofra (sofra-hub.com), by Tap Hub, is run by Echo Group LLC. Sofra lets restaurant guests order from their table by tapping a card with their phone. This page explains what we collect, why, and who can see it.
If you're a guest ordering at a restaurant
You don't create an account, and we don't ask for your email, phone number or payment details. We keep:
- Your order: the items, quantities, any note for the kitchen, which table it came from, and when it was sent, confirmed, cooked and served.
- A first name, only if you type one, so others at your table can see who added what to the shared cart. You can skip it.
- Small cookies on your phone: one that remembers which table you tapped (it expires after 4 hours), one random ID that tells your phone apart from others at the table, and the first name if you gave one.
You pay the restaurant directly, the way you normally would. Sofra never sees or stores your card details.
Who sees it: everyone who tapped the same table's card sees that table's shared cart, including first names. The restaurant's staff see orders and names for their restaurant. Other restaurants never see your orders.
Allergens: menu details, including allergens and calories, are written by the restaurant. If you have an allergy, please check with the staff.
If you work at a restaurant on Sofra
- Your account: your name and email address, through our sign-in provider. If you choose “Continue with Google”, Google shares your name, email address and profile picture with us — nothing else.
- What you do in Sofra: for example which waiter confirmed an order and when. Owners see this to understand how service is going.
- A security log of important actions (such as creating invites, pairing kitchen screens or changing staff), including the internet address they came from.
- Billing (owners): your restaurant's plan status, trial and renewal dates, and a Stripe customer reference. Card details are typed on Stripe's page and stay with Stripe.
Restaurant information
The restaurant's menu, prices, photos, tables and order history are stored so Sofra can show the menu, run orders and give the owner their numbers.
Cookies
Sofra only uses cookies it needs to work: the guest cookies above, sign-in cookies for restaurant staff, and one that keeps a paired kitchen screen connected. We don't use advertising or tracking cookies, and we don't use analytics that follow you across websites.
Services we use
To run Sofra, we use these providers, who store or process data on our behalf:
- Vercel — hosts the website and its firewall.
- Neon — the database, located in the United States (Oregon).
- Cloudflare — stores menu photos.
- Clerk — sign-in for restaurant staff.
- Ably — sends “something changed” signals so screens update instantly. These signals don't contain order details.
- Google — only if a staff member chooses to sign in with Google.
- Stripe — handles restaurant subscriptions: card details, billing email and invoices.
We don't sell personal information, and we don't share it for advertising.
How long we keep it
Orders are kept so the restaurant has its records and statistics. Guest cookies expire on their own (the table cookie after 4 hours; the guest ID after a year). Staff accounts are kept until the restaurant or the person asks us to remove them. Security logs are kept to protect the service.
Your choices
Depending on where you live, you may have the right to ask what we hold about you, to correct it, or to have it deleted. Email us and we'll help. Guests can also clear Sofra's cookies from their phone's browser at any time.
Children
Sofra isn't aimed at children under 13, and guests never create accounts.
Security
Connections are encrypted, staff pages require sign-in, each restaurant's data is kept separate, and the website runs with limited database permissions. No system is perfect, so please tell us if you spot a problem.
Changes
If we change how Sofra handles personal information, we'll update this page and its date.
Questions? Email support@sofra-hub.com.