RestoCAP Privacy Policy
Effective Date: October 25, 2026 | Version: 2026-10-v1 | Status: Active Operational Policy
1. Introduction & Scope
RestoCAP (“we”, “us”, or “our”) provides multi-tenant hospitality operations software for restaurant owners, managers, kitchen staff, and cashiers, as well as digital QR ordering interfaces for dining guests.
This Privacy Policy explains how we collect, process, store, and protect information when you access our websites (including www.restocap.tech), use our console applications, or interact with our digital restaurant menus.
2. Restaurant Operator & Staff Account Data
When a restaurant operator registers for RestoCAP, we collect and store:
- Operator Profile: Full name, verified business email address, and contact telephone number.
- Organization & Branch Details: Restaurant business name, branch identifiers, physical dining address, time zone, and operating currency (e.g. INR).
- Staff Team Memberships: Internal role assignments (Owner, Manager, Kitchen, Cashier, Server) and associated station permissions.
- Menu Catalog Records: Dish titles, pricing, descriptions, allergen flags, category hierarchies, and menu photography uploaded by the operator.
3. Customer & Dining Guest Information
RestoCAP is intentionally engineered to minimize guest data collection:
- No Mandatory Account Creation: Diners can view menus and order food without creating a password, without logging in, and without downloading an app.
- Ephemeral Session Tokens: When a diner scans a table QR code, an ephemeral guest session token is generated in client storage to maintain the active cart and associate the diner with Table X for that dining service.
- Order Ticket Records: Selected dish items, quantities, modifiers, special instructions (e.g. “less spicy”), table number, ticket timestamp, and fulfillment status.
- Customer Feedback: Star ratings and written reviews submitted with explicit publication consent. Private session tokens are never disclosed in public review views.
4. Payment References & Settlement Status
Strict Payment Storage Boundary: RestoCAP does not collect, process, or store raw debit/credit card numbers, CVVs, or bank account passwords/UPI PINs.
What We Store:
- For customer food bills: Total bill amount, CGST/SGST tax components, settlement method (Cash, UPI Standee, Card Terminal), cashier actor ID, and the 12-digit bank reference/UTR number entered by the cashier upon verification.
- For RestoCAP SaaS subscriptions: Invoiced subscription tier, billing cycle dates, offline bank reference ID, and administrative approval timestamps.
5. Authentication & Security Logs
Staff access to the manager console is secured through Supabase Auth using JSON Web Tokens (JWTs) and secure session storage. We maintain automated audit logs of:
- Authentication login timestamps and password reset activities.
- Menu price updates and branch configuration modifications.
- Payment settlement recordings and cashier invoice generation.
6. Cookies & Client Local Storage
RestoCAP does not use third-party behavioral advertising cookies or cross-site tracking pixels. We use strictly functional browser storage mechanisms:
| Key / Identifier | Storage Type | Purpose & Scope |
|---|---|---|
| restocap_active_branch | Local Storage | Remembers the active restaurant branch in the staff console. |
| restocap_announcement_config_v1 | Local Storage | Saves manager English/Hindi speech preferences and station profiles. |
| restocap_guest_cart | Local Storage | Retains active dining cart items while diner browses dishes. |
| sb-*-auth-token | Local Storage | Staff session token for authenticated console access. |
7. Third-Party Service Providers
We partner only with reputable infrastructure and hosting providers to deliver the platform:
- Supabase Inc.: Managed PostgreSQL database hosting, encrypted backups, and real-time WebSocket ticket subscriptions.
- Cloudflare / Vercel: Global content delivery network (CDN) and edge web application delivery with DDoS protection.
- Email Delivery: Transactional password resets and account notices are dispatched through Brevo or Listmonk.
- Browser Native Speech: Voice announcements use the browser’s native Web Speech API and Web Audio chime without sending voice recordings to external cloud servers.
8. Retention and Deletion
Operator Business Data: Retained for the duration of the active subscription and up to 90 days following account termination, allowing export of tax invoices.
Customer Dining Sessions: Order tickets are retained by the restaurant for sales history and statutory tax audits (GST compliance). Ephemeral guest session tokens expire automatically upon session completion.
9. Data Access & Multi-Tenant Isolation
Every SQL query executed on the platform is governed by PostgreSQL Row-Level Security (RLS). Policies guarantee that staff from Restaurant A can never query, inspect, or modify records belonging to Restaurant B.
RestoCAP does not sell, rent, or trade customer data to any third party for commercial marketing.
10. Privacy Requests & Grievance Officer
Under applicable Indian laws (including the Information Technology Act, 2000 and Digital Personal Data Protection Act), users and restaurant operators have the right to request access to, correction of, or deletion of their personal data.
To submit a privacy or data deletion inquiry, contact our Grievance Officer: