Privacy Policy
This policy explains how Food Court Operating System handles customer, vendor, and owner data for ordering and food court operations.
Data We Collect
FCOS collects the information needed to operate food court ordering, staff access, support, fraud prevention, and payment reconciliation.
Phone Numbers And Authentication
Customers may sign in with a phone number and OTP. Staff users sign in with email and password credentials. Authentication tokens are stored on the device to keep active sessions available.
Order History
We preserve order numbers, item details, status history, totals, table references, and related customer or tenant identifiers so orders can be fulfilled, supported, and audited.
Vendor And Food Court Data
Vendor names, counter details, menu data, operational status, food court branding, support contact details, and layout data may be stored for customer ordering and owner dashboards.
Payment Processing
Payments are processed through Razorpay. FCOS stores payment status, amounts, gateway order IDs, payment IDs, signatures, and split metadata needed for reconciliation. Card, UPI, and bank details are handled by Razorpay.
Storage Providers
FCOS may use Supabase or compatible PostgreSQL-backed storage for application records, tenant data, and operational assets. Access is limited to service needs and configured tenant isolation.
Account Deletion
Customers can delete their account from customer settings. Phone numbers are anonymized and login access is removed, while required order and payment records are preserved. Vendors can request deletion through their profile. Food court owners can deactivate a food court account from owner settings.
Contact
For privacy or deletion questions, contact the food court support address shown in the customer experience or write to the FCOS operator responsible for your deployment.