What we store
and what we don’t know.

You sign in to the dashboard with an existing Google account. That gives us your email address and a user ID, which is how we know which restaurant is yours. TableFlow never sees your password and doesn’t read your email.

• Diners don’t need an account: the public menu never asks who they are.
• Creating your restaurant and preparing your menu is free. To publish it you need an active subscription (or an invitation to the pilot).
• Google applies its own policy to signing in: Google’s privacy policy(opens in a new tab).

The database and photos are in a free Supabase project created in the Frankfurt (Germany) region. Photos live in a private bucket and are shown through signed links that expire after a few minutes, not permanent public addresses.

• Each restaurant can only read and write its own menu; permissions are enforced in the database, not just on screen.
• The region chosen for this data is in the EU, but we can’t promise that all processing happens in the EU: providers may process technical logs and metadata in other countries under their own terms.
• Provider terms: Supabase privacy(opens in a new tab).

Your restaurant’s subscription is handled by Stripe. Before you pay, your subscription screen shows the price and whether the charge is real or a test. Don’t enter a real card or customer data while that screen says test mode.

When payments are enabled, TableFlow sends Stripe an internal account ID. On its payment page, Stripe asks for your email, your billing name and address and, if you like, your tax ID; Stripe keeps them in your customer record for receipts. TableFlow stores the customer and subscription IDs, their status and dates, not your card number. The authorised administrator can see the email, the restaurant and the status of subscriptions, without amounts. None of this replaces a legal review before selling.

The website is served from Cloudflare Pages and the data service from Supabase. Both log the requests they receive, such as the IP address, the browser and the date, to run and protect their services.

• Those logs belong to each provider: who can access them and how long they’re kept is set by their own terms, not by TableFlow.
• They aren’t used to profile diners and aren’t combined with your menu.
• There’s no advertising, built-in analytics or third-party pixels on these pages.
• Provider terms: Cloudflare privacy(opens in a new tab).

Some of your work is kept on the device itself, in the browser’s local and session storage: it’s technical storage, not advertising, and it doesn’t follow you to another phone.

• Sign-in session: the token that keeps the dashboard open until you sign out. That token is sent to Supabase with every dashboard request: it’s what identifies you as the owner of your menu.
• Unfinished dishes: split by account and restaurant, they stay in the browser so you don’t lose them when you switch screens.
• Menu language: if a diner picks a language on a menu, their browser remembers it for next time. It isn’t sent to any server.
• Dashboard language: if you choose English or Spanish for the dashboard, your browser remembers it. It isn’t sent to any server.
• Local demo: the sample menu you edit, the theme you choose and the “tutorial completed” mark, without leaving the browser.
• Clearing the site’s data in your browser deletes all of this. Signing out doesn’t delete the unfinished dishes in that browser.
• Because there are no built-in analytics and the storage is technical, this website doesn’t show a cookie banner. This describes what we do; it isn’t a legal assessment of your situation.

It’s worth being clear about this before you use TableFlow with real customers.

• A published menu is public. Anyone with the link or the QR code can see it, without a password and without us knowing who opened it.
• Don’t upload your customers’ data or sensitive information to dishes or photos: this pilot isn’t designed for that.
• There’s no end-to-end encryption and no guaranteed backups. It’s a pilot, not a service with an uptime commitment.
• You can download your saved data from Help and data for your menu in the dashboard: it includes text, prices and photo references, not the images or unfinished dishes, and it doesn’t restore anything by itself.
• Deletion is manual: to delete your restaurant or your pilot account, email cristiancaride@gmail.com.
• If the pilot becomes a full service, it will need a formal privacy policy and an identified controller. This page wouldn’t be enough.

Casa Brasa is a fictional restaurant and its dishes, prices and text are made up on purpose. The images are reference photos with their credits, not photos of real dishes. The demo runs entirely in your browser and never sends your test menu to any server.

You can check the credits inside the demo itself, on its credits page.