LetItServe
Back to home
01 · Information we handle02 · Diner and order information03 · How information is used04 · Service providers05 · Browser storage and sessions06 · Security and access07 · Retention and requests08 · Policy changes

LetItServe · letitserve.com

Privacy Policy

Effective: 27 July 2026

This document describes the current service in plain language. Restaurant Owners should obtain local legal advice before relying on it for regulatory compliance.
01

Information we handle

We handle account details such as email address and authentication identity; restaurant information, menus, tables, staff invitations, settings, orders, order items, payment records, and sales data; and technical information needed for security, sessions, rate limits, and troubleshooting.

02

Diner and order information

Diner ordering can create table-session identifiers, orders, selected options, notes, waiter calls, and bill requests. Restaurants control the menu and operational records connected to their workspace. Diners should not place unnecessary sensitive personal information in order notes.

03

How information is used

Information is used to authenticate users, isolate restaurant workspaces, display menus, accept and route orders, operate kitchen and cashier views, maintain subscriptions, produce restaurant sales reports, prevent abuse, and respond to support requests.

04

Service providers

The service currently relies on Supabase for backend, database, authentication, storage, and realtime functions, and Vercel for application hosting and delivery. Google is involved when a user chooses Google sign-in. Those providers process information under their own terms and privacy commitments.

05

Browser storage and sessions

The application uses browser storage and authentication cookies or tokens to keep users signed in, remember interface language, maintain secure table sessions, and support essential application behavior. Clearing browser data can remove those preferences and sessions.

06

Security and access

We use authentication, tenant-scoped database policies, role checks, signed table sessions, protected server functions, rate limiting, and Owner passcodes for sensitive sales access. No internet service can promise absolute security, so Owners must protect credentials and promptly remove staff who should no longer have access.

07

Retention and requests

Operational records are retained while needed to provide the service, protect accounts, maintain billing history, and meet legitimate legal or administrative needs. Owners can contact support to ask about access, correction, or deletion. Some records may need to remain where required for security, disputes, or applicable law.

08

Policy changes

This policy may be updated as the service, providers, or legal requirements change. The effective date on this page will be updated when a revised policy is published.

Questions?Contact LetItServe support
Telegram