Privacy Policy
Effective Date: September 2026 • Last Updated: September 2026
Welcome to KitchenZap("we", "us", or "our"). KitchenZap is a Restaurant Operating System and digital restaurant operations platform serving restaurants, cafes, cloud kitchens, and food businesses.
Our platform connects ordering, payments, kitchen operations, billing, customer management, and restaurant growth in one unified system. KitchenZap supports multiple customer ordering and communication channels — including table QR ordering, direct online web menus, and optional WhatsApp ordering where enabled by the restaurant.
This Privacy Policy explains how we collect, use, store, and protect information when restaurant partners and end-diners interact with our software, dashboard, website (kitchenzap.in), and associated ordering services.
1. Information We Collect
A. Restaurant Partner Information
- Restaurant business name, owner/manager name, and staff login credentials (email and securely hashed passwords).
- Official contact phone number, city, and optional store address for receipt generation.
- GSTIN and FSSAI license numbers (where configured for tax and compliance invoicing).
- Merchant UPI ID (VPA) and payment gateway API identifiers for customer settlement.
- Where self-managed WhatsApp is enabled: Meta Cloud Phone Number ID and Cloud Access Token provided by the merchant for API connectivity.
B. End-Diner & Customer Information
- Customer phone number and customer display name provided during ordering.
- Dining table number (for dine-in QR orders).
- Delivery address details and contact phone (only where delivery ordering is enabled).
- Order items, selected portions, item modifiers, cooking notes, and order timestamp history.
2. Ordering Channels & Optional WhatsApp Processing
KitchenZap operates independently of any single channel. Restaurants can accept orders via table QR stands and direct web ordering without enabling WhatsApp.
When a restaurant chooses to enable WhatsApp ordering or automated messaging, messages are transmitted through official Meta Cloud APIs (Graph API) and KitchenZap's processing infrastructure to assemble carts, process order status transitions, and deliver automated order notifications.
- No Selling of Data: We do not sell, rent, or trade customer contact numbers or diner lists to third-party marketing networks or brokers.
- Operational Purpose: Order details and conversational data are processed exclusively to fulfill restaurant orders, calculate billing totals, generate KOT tickets, and manage guest history.
- Workspace Tenant Isolation: Operational records (orders, menus, customers, settings) are scoped at the application repository level using strict restaurant tenant identifiers (
restaurant_id).
3. Payment Security & Third-Party Gateways
KitchenZap does not collect, process, or store sensitive card verification codes (CVV), netbanking passwords, or UPI PINs.
Authorized Payment Rails (Razorpay / Cashfree / PhonePe / Direct UPI)
Online customer payments and restaurant wallet recharges are processed through authorized payment aggregators via industry-standard encrypted transport (HTTPS/TLS). Third-party gateway fees apply separately where applicable.
4. User Rights & Contact
In accordance with applicable data protection laws, including the Digital Personal Data Protection (DPDP) Act 2023 and the Information Technology Act 2000, restaurant partners and diners may review, update, or request the deletion of their personal information.
Privacy Support & Inquiries:
Email: privacy@kitchenzap.in / support@kitchenzap.in
Our support team endeavors to acknowledge and review verified data requests promptly.