Privacy Policy

Data collection

We collect account information, contact details, login and device metadata, support messages, billing details, and operational data entered into the platform.

Restaurant business data

Tenant data may include branches, tables, menus, prices, orders, KOT records, receipts, inventory, reports, subscriptions, invoices, and operational settings.

Customer data

Restaurant tenants may store customer names, phone numbers, emails, preferences, feedback, complaints, loyalty points, wallet/credit records, coupons, and order history.

Analytics

We may use aggregated operational and technical analytics to monitor reliability, improve workflows, understand feature usage, and identify performance issues.

Cookies

We use session cookies for login and security, preference cookies for usability, analytics cookies where enabled, and marketing cookies only where permitted.

Retention

Data is retained while accounts are active, as required for billing, security, audit, legal, tax, backup, or legitimate operational purposes, then deleted or anonymized where practical.

Security

RestaurantOS uses role-based access, tenant isolation, audit trails, secure password handling, upload controls, and operational monitoring to protect data.

Third-party services

The platform may depend on hosting, database, Redis, email, object storage, error monitoring, analytics, DNS, SSL, or support providers. These providers process data only as needed for the service.

International usage

RestaurantOS may be used internationally. Customers are responsible for configuring local tax, receipt, privacy, employee, and restaurant compliance requirements.

GDPR/basic privacy compliance

Where applicable, customers may request access, correction, export, restriction, objection, or deletion of personal data. B2B tenants are usually data controllers for their restaurant customer data.