Privacy Policy

Last updated: May 26, 2026

At Foodie POS (a product of SB Dev Studio), we are committed to protecting the privacy and security of your restaurant's business data and the personal information of your dining guests. This Privacy Policy outlines exactly how we process information based on our operational parameters to maintain absolute transparency.

1. Information We Collect & Store

Our cloud platform dynamically records and manages data in the following categories:

A. Merchant & Restaurant Information
We store details of your restaurant franchise and specific branches, including owner contact data, physical address coordinates, VAT/GSTIN details, and subscription invoices.

B. Staff & Device Authentication
To provide role-based access controls and prevent security breaches, we store profiles of your restaurant staff including names, emails, roles (Admin, Manager, Cashier, Chef, Waitstaff, Delivery), and precise hardware device identifiers logging device name, ID, and last active timestamp.

C. Diner & Customer Information
When cashier terminals log transactions or guests use tableside QR codes, we store customer profiles containing name, phone number, email address, physical coordinates, and VIP status labels. We also track loyalty analytics including total visit counts, last visit dates, and cumulative spending metrics.

D. Operational & Billing Details
To run POS functions, we record order pipelines (including standard orders, modifiers, and combo deals), payment lists (for cash, cards, and UPI splits), table configurations, guest reservations, and inventory logs (including stock counts and ingredients maps).

E. Delivery Tracking Coordinates
If your outlet utilizes our delivery module, we track delivery order statuses and record real-time GPS locations (logging latitude, longitude, and timestamp) for mapping.

2. How We Use the Data

We process information strictly to guarantee operational uptimes and compile business performance reports:

To route tableside customer orders instantly to cashier terminals and Kitchen Order Ticket (KOT) stations.
To automatically deduct raw stock inventory counts when dishes are completed at a kitchen station.
To calculate precise billing totals, tax splits, rounding adjustments, and automated sales forecasts.
To track cash drawer balances, partial payment status values, and payment split configurations.
To log staff actions for internal merchant auditing purposes.

3. Data Security & Storage Architecture

All transactional records, customer profiles, and logs reside in highly secure database environments powered by **Supabase**. We enforce strict Row Level Security (RLS) policies on every table (such as subscriptions, orders, and staff profiles) to ensure that only authenticated terminals belonging to your specific restaurant account can access or modify your private business information.

4. Share Limits & Integrations

We do not sell restaurant business data or guest ordering profiles. Information is shared only with trusted systems to compile operations:

Supabase & Vercel: Our underlying secure cloud database and hosting backbones.
Delivery Aggregators: Passing order details to external third-party partners if active on your subscription.
WhatsApp API Services: Dispatching e-bills directly to customers using transaction logs when opted-in.

5. Data Retention & Wiping Rights

Upon subscription deactivation or account cancellation, merchants hold the right to request a complete wipe of their private data. Upon written request, all associated profiles, active devices logs, reservations, order sequences, and transactional histories will be permanently deleted from our active database partitions.

6. Contact Our Product Architects

For any questions regarding this privacy mapping, or to request data exports, please contact the principal developer:

Email: banerjeesharnabh@gmail.com
Developer Agency: SB Dev Studio, Ghaziabad, UP, India.